Related
Hey there,
My Asus Transformer TF101 was working fine yesterday... I recently updated to ICS without any problem. I then rooted my device using viperMOD PrimeTime v4.5. Once again, everything worked without any problem.
After rooting, I ran the V6 SuperCharger script. The device rebooted and everything was fine... Then according to the instructions, I downloaded a modified version of the services.odex file and I replaced the original system file (I did kept the original file by changing the extention to .tmp). This is the last time I've seen my Transformer booting. I did this because of the reply from bsoplinger on this post:
http://forum.xda-developers.com/showthread.php?t=991276&page=906
The thing is that I forgot to change the owner:group to root:root and to chmod 644. I believe this is where I failed.
Asus Transformer TF101 B80
Rooted ICS with viperMOD PrimeTime v4.5
V6 SuperCharger Script activated (Choose Option #8)
Replaced original services.odex with a new "empty" one
Now, when booting it gets stuck on the Asus Logo with the rotating loading circles... they keep rotating forever until the battery is drained out.
This is what I tried:
Booting with Power button & Volume down then Volume down again (tried Cold boot and Wipe)
Booting with Power button & Volume down then Volume up (Recovery)
Booting with Power button & Volume up + NVFlash (won't work because it is not a B50-B60-B70)
Drained the battery to 0%
Put an official firmware update zip file on a microSD and booted with it
So.... this is pretty much it... As of now, I'm out of ressources and I don't know what else I can do... 40$ via Paypal to the first persone who gives me a working solution.
Thank you for your time!
If you have the original saved on your PC, try pushing it to your TF with ADB
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
baseballfanz said:
If you have the original saved on your PC, try pushing it to your TF with ADB
Click to expand...
Click to collapse
Actually, the renamed original file is only on the internal SD card of the Transformer. I don't have a copy.
I am currently trying to ADB work... I installed the proper APX drivers but I get a message from Windows saying that the ASUS Android MTP Drivers failed to install and all I get from ADB/Fastboot is a "- waiting for device -" message...
I'm using Windows 7 Pro 64bit
Jfuginay said:
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
Click to expand...
Click to collapse
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
bArDBQ said:
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
Click to expand...
Click to collapse
Try what I mentioned about shutting down processes and hold down Volume up plus power when booting. You'll see a black screen but that's ok, you can verify that there is actually something going on because your computer should make the sound stating a new device has been connected to your pc.
From that black screen, you should be able to get nvflash to work, assuming you've shut down other programs that could be using adb, and have installed the correct driver for nvflash, and have also unpacked the prime rom into the nvflashf folder.
Jfuginay said:
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Click to expand...
Click to collapse
I will try to close all process that might use ADB but I already know that NVFlash will not help me since my device is a B80 and that NVFlash won't work with anything over B70
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I will make ADB working and see what I can do from that... Should not be that difficult.
I am installing Asus PC Suite since it seems to be the best way to get the missing drivers...
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I just can't get ADB to see my device...
I installed Asus PC Suite, it does detect the device and show it as "Nvidia USB Boot-recovery driver for Mobile device" in Window's device list when I boot using Power Button + Volume UP... When I launch adb from command prompt deamon starts but when I type "adb devices" it shows: "List of devices attached" but that's it... no devices in the list.
I deleted the "Nvidia USB Boot-recovery driver for Mobile device" and installed the default ASUSTeK Computer Inc. drivers I already had in Windows drivers list "ASUS Android ADB Device" but I get the exact same result.
I also tried to install the USB Drivers from ASUS website "ASUS_Android_USB_drivers_for_Windows.zip" but it seems like they are not made for Windows 7 64bits... The OS doesn't see them or won't install them...
AAAAAAAAAAAAHHHHHHH
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
bArDBQ said:
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
So, cold-booting did not help, when I do this, the device manager shows that the "ASUS Android MTP device" drivers failed to install. I get the Code 10 (This device cannot start)
jazzruby said:
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
Click to expand...
Click to collapse
Hello JR,
Thanks for the reply.
I manage to show the ghost devices and hidden device in the device manager. I deleted everything, and rebooted the computer. I connected the Transformer and cold-booted. Windows detected the device and I choose the MTP drivers from ASUS_Android_USB_drivers_for_Windows.zip but I got the same result. When I was booting using the Power Button + Volume Up Windows was detecting the device in ADB mode and I was able to install the proper drivers and make it work.
This said, it was impossible for me to get the Transformer in the device list in ADB. My computer simply can't connect to the tablet.
I can't make sure USB debugging is enabled in Settings on the device since the device do not boot but it was before it was bricked.
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
BiohazardPL said:
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
Click to expand...
Click to collapse
Hey,
No, I was unable to fix the problem. I returned the device to ASUS and my replacement unit is on its way. I guess I was lucky they were not able to fix it.
Since you are on a B70 you might be able to use NVFlash. You should try it if not already done.
Good Luck!
SON OF A BBBBBBbbbbb
Son of a bbbb... Son of a BBBB.... Son of a BBBB... hot damn. Ok Rooted, stock TF101. I was beta testing an app, and got the andy on his back with red triangle for my TF101 (us variant). I can see the Eee pad logo start, then nothing, only the back light stays on. Recovery leads to andy on his back. I tried Vol down + Power until reboot, then let it settle and come up with either choose to enter android or wipe data. Either one does nothing. Only the back light stays lit.
Recovery option is a no go.
Normal cold boot is a no go,
Hot boot is a no go.
PERI is a no go.
NVFlash is not tried yet.
ODIN is a no go.
12 pack of beer is a GO. Need more though I think.
Any assistance would be helpful.
UPDATE : Easyflash with the latest OFFICIAL Asus 4.0.3 update worked perfectly. NOTE : there was a simple partial file error that caused the problem.
adb shell adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"
hello people but once I need your help
someone deleted all folders from my TF101
'm trying flashing mode with adb but is giving this error
adb shell "exec '/ system / bin / sh' failed: No such file or directory (2)"
what can I do? regarding this error.
try fastboot mode but this does not recognize the device
help me please
even more
Fastboot isn't available on the TF, have you tried APX mode?
Hold volume-up while the TF is off, then press power and wait a second, the screen will stay blank but you'll enter apx mode. If you then plug in the TF it should be recognized by your computer.
Then you can use the NvFlash tool to completely restore your tf to stock, and if you want root you can then manually or use one of the many tools (Mine/1-click/easyflasher) to do this...
Links --
NvFlash files to get back to stock ASUS version .27 -- Also includes driver folder called 'usbpcdriver' which you install to get your computer to see the TF in APX mode. Pick WW for a tablet outside of the United States and US for a US tablet.
You should then download wheelie.zip from here - Wheelie - NvFlash for TF101.
Extract all files from the wheelie.zip and place them in the .zip of the NvFlash version you downloaded, overwrite any files that already exist.
Make sure the driver properly installs, you can run in command prompt:
Code:
pnputil -a C:\Users\[username]\Downloads\TheNvFlashzip\Usbpcdriver\Nvidiausb.inf
Be sure to do this with the TF unplugged, the drivers will install on next plugin.
-Or use the manually search for a driver option when windows fails to find the proper drivers and manually navigate to the usbpcdriver folder.
Only do this if apx mode isn't detected.
--
From here you have everything you need, and you will need to find out your TF's Serial Number to find the SBK (Secure Boot Key) version. It can be found on a sticker on the bottom of your tablet by the charge port, or on the box that the device came in.
The serial will be rather long, you're only interested in the first 3 entries:
-If it reads B60 or a lower number than 60, run the 'reflash sbkv1.bat' in the folder, which will reflash your tf completely to stock assuming it's plugged in during APX mode and the drivers were properly installed.
-If it reads B70 or a higher number than 70, run the reflashsbkv2.bat to NvFlash the device.
--
This process should take a little while, then the device should boot up like new, assuming everything was done properly..
If you wish to root afterwards, use either my PERI tool (link below) or another tool, one can be found in General and a few can be found in the Development threads.. Or manually root with Wolf's method 3. Currently all methods require a pc with usb connection and proper adb drivers installed, my tool and others assist you through this process.. it's very similar to above Nvflashing driver process.
Thing O Doom said:
Fastboot isn't available on the TF, have you tried APX mode?
Hold volume-up while the TF is off, then press power and wait a second, the screen will stay blank but you'll enter apx mode. If you then plug in the TF it should be recognized by your computer.
Then you can use the NvFlash tool to completely restore your tf to stock, and if you want root you can then manually or use one of the many tools (Mine/1-click/easyflasher) to do this...
Links --
NvFlash files to get back to stock ASUS version .27 -- Also includes driver folder called 'usbpcdriver' which you install to get your computer to see the TF in APX mode. Pick WW for a tablet outside of the United States and US for a US tablet.
You should then download wheelie.zip from here - Wheelie - NvFlash for TF101.
Extract all files from the wheelie.zip and place them in the .zip of the NvFlash version you downloaded, overwrite any files that already exist.
Make sure the driver properly installs, you can run in command prompt:
Code:
pnputil -a C:\Users\[username]\Downloads\TheNvFlashzip\Usbpcdriver\Nvidiausb.inf
Be sure to do this with the TF unplugged, the drivers will install on next plugin.
-Or use the manually search for a driver option when windows fails to find the proper drivers and manually navigate to the usbpcdriver folder.
Only do this if apx mode isn't detected.
--
From here you have everything you need, and you will need to find out your TF's Serial Number to find the SBK (Secure Boot Key) version. It can be found on a sticker on the bottom of your tablet by the charge port, or on the box that the device came in.
The serial will be rather long, you're only interested in the first 3 entries:
-If it reads B60 or a lower number than 60, run the 'reflash sbkv1.bat' in the folder, which will reflash your tf completely to stock assuming it's plugged in during APX mode and the drivers were properly installed.
-If it reads B70 or a higher number than 70, run the reflashsbkv2.bat to NvFlash the device.
--
This process should take a little while, then the device should boot up like new, assuming everything was done properly..
If you wish to root afterwards, use either my PERI tool (link below) or another tool, one can be found in General and a few can be found in the Development threads.. Or manually root with Wolf's method 3. Currently all methods require a pc with usb connection and proper adb drivers installed, my tool and others assist you through this process.. it's very similar to above Nvflashing driver process.
Click to expand...
Click to collapse
I tried this several times but giving error
Using SBK type 2.
Using bootloader: ´bootloader.bin´.
Using BCT: ´transformer.bct´.
_________________________________
= Chip UID: 0x299648565018420119
- Incorrect SBK or SBK type selected. nverror: 0x4
connetion failed Nverror 0x30011
acacioxda said:
I tried this several times but giving error
Using SBK type 2.
Using bootloader: ´bootloader.bin´.
Using BCT: ´transformer.bct´.
_________________________________
= Chip UID: 0x299648565018420119
- Incorrect SBK or SBK type selected. nverror: 0x4
connetion failed Nverror 0x30011
Click to expand...
Click to collapse
You used the wrong sbkvX.bat file, as stated in the error message.
use sbkv1. If that doesn't work then you have the 3g version or the slider, and are probably SOL.
I found a way to install APX drivers in PC for TF700. As everbody, or almost everbody knows, these drivers are absolutely vital for the ones that want to run NVFlash to secure their TF700 in the best way against an eventual brick. As I experienced—and I know I am not the only—this adventure of APX drivers install causes a lot of trouble to people trying to figure out where are the drivers and how the install should be done.
Days ago, I posted these step-by-step instructions as a reply of a message about APX drivers. I am now posting it again at a separate topic, as this can be easier to find. The thing is that there's some "tricks" and "pitfalls" to the newbies like me when they try to install that Asus USB drivers. At first I couldn't install, I even thougt that they were not compatible with my Windows (I use Vista 32, that is famous as being really a ***** when comes up to install things). So, for ADB, in that moment I just gave up from Asus Android USB Drivers and installed Asus Pad PC Suite, that included ADB drivers, but apparently no APX. At that moment, when I was only looking for ADB, worked. But later, trying APX, I got really stucked. Just found the solution many sleepless nights later.
Please just notice that I am not an expert in anything: just a cat-crazy lady that works as text revisor and does patchwork quilts and amigurumi dolls at the free time. So, I'm afraid I can't help much on the technical side if any doubt appear (unless your doubt is about feeding an elder toothless cat with a bird syringe, syntax of verbs in Portuguese or about brands of wool and thimbles). Also can't assure this method will work for everyone.
Anyway, I'll be glad to help with the few I know. I hope these instructions can be of any use and save people from stress. Best wishes and happy APX'ing.
********************HOW TO INSTALL APX FOR TF700 IN WINDOWS************************
***One important warning I give to the stucked TF700 owners that are searching for APX drivers: DO NOT TRY TO USE UNIVERSAL NAKED DRIVERS! They will not work! Universal Naked Drivers are great, but made for TF101, Prime, Nexus, etc, etc, NOT for TF700 Infinity! So, any attempt to use that drivers, at the moment (March 2014) will give you nothing more than a last-longing splitting headache.
Use the pack from Asus: "Asus Android USB Drivers", download the pack from Asus website (go there, is one of the few downloads for Windows available for TF700)***
I'll just enumerate what I did and what I paid attention as necessary steps to install APX drivers for TF700 in Windows. If someone wants to give a try and follow them, there's the description.
1) Your device must be with the USB Debugging Mode enabled. This is found under Developer Options (enable it if Developer Options doesn't show by tapping 7 times the build number, under Settings/About).
2) Asus drivers dislike Windows auto-install. When we plug our device in USB (just normally, Android running), he is recognized and Windows auto-install prompts a message offering to locate and install drivers. IGNORE IT, SKIP IT. Just tell windows that will install later (there's an option for that, at least in Vista 32).
3) Then go to Control Panel, and choose "System". There, choose "Device Manager". There, look for something Asus, if you don't have previously installed any (if you have, uninstall it first, reboot the PC, then plug the tablet via USB). If you haven't installed anything and your tablet is connected, will appear something like "Asus ADB Interface", marked as not working by Windows.
4) Then, right-click over it and ask for "Update Driver". It will open a new prompt asking if you want Windows to search it automatically or if you want to search driver files manually from other sources. Say you want to search it manually. After, say you want to choose from drivers list (bottom option) and then say "Have Disk". And then direct Windows to search the driver in the directory where "Asus Android USB Drivers for Windows" are (uncompressed directory, please). The drivers file is the "android_winsub.inf", under the sub-directory "Android". Choose the file and proceed the installing.
5) This should install ADB. But, wait: the problem is the APX, not the ADB, right??? So, what does all this is for?
6) Now the magic (or, what so magically happened to me): reboot the tablet into APX Mode (power+volume up). And then another window of APX auto-install will pop. IGNORE IT.
7) Again, go to System/Device Manager. APX should appear there as "Asus Transformer Infinity APX Interface" or something fancy alike (if appear only "APX", something gone wrong and the installation already failed, at least here was this way). Is also marked as not working by Windows. You should again right-click and choose "Update Driver"
8) Repeat the process, if necessary direct Windows to the directory where the android_winsub.inf is (the one that was into the Asus Android USB Drivers pack). From this point my Windows installed automatically some parts, but, as I could notice, installed the driver from that same file of before.
This installed APX for me, and I could run wheelie and NVFlash!
So, I honestly hope this helps. I know it arrives too late for many, but still if can help somebody at least a little bit, I'll be happy.
Hello drhode, are you sure Universal Naked Drivers do not work? I remember very clearly that I used Universal Naked Drivers to run NVFlash and wheelie worked fine a few months ago. In fact, the guide for Flatline actually includes a link to a set of Universal Naked Driver 0.72, and I am very sure that I used that to get APX Driver.
huy_lonewolf said:
Hello drhode, are you sure Universal Naked Drivers do not work? I remember very clearly that I used Universal Naked Drivers to run NVFlash and wheelie worked fine a few months ago. In fact, the guide for Flatline actually includes a link to a set of Universal Naked Driver 0.72, and I am very sure that I used that to get APX Driver.
Click to expand...
Click to collapse
There seem to be different versions of this driver pack in circulation. To see whether it works with the TF700, look into the .inf files for USB vendor and product IDs and compare with my udev rules for Linux. The vendor and product IDs are the same for Windows, and they should appear somewhere in the .inf file (for wheelie, at least the one for APX):
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c90", GROUP="plugdev", MODE="0660" # MTP (normal)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", GROUP="plugdev", MODE="0660" # MTP + USB Debugging (adb)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c92", GROUP="plugdev", MODE="0660" # RNDIS
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c93", GROUP="plugdev", MODE="0660" # RNDIS + USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c94", GROUP="plugdev", MODE="0660" # PTP
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c95", GROUP="plugdev", MODE="0660" # PTP + USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", GROUP="plugdev", MODE="0660" # Fastboot
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX
@drhode Can you please post the link where you found the drivers? Have been searching the Asus download site high and low and don't see them. Only found a zip on XDA and that only seems to have the ADB dirver.
Sent from my K00C using Tapatalk
drhode said:
I found a way to install APX drivers in PC for TF700. As everbody, or almost everbody knows, these drivers are absolutely vital for the ones that want to run NVFlash to secure their TF700 in the best way against an eventual brick. As I experienced—and I know I am not the only—this adventure of APX drivers install causes a lot of trouble to people trying to figure out where are the drivers and how the install should be done.
Days ago, I posted these step-by-step instructions as a reply of a message about APX drivers. I am now posting it again at a separate topic, as this can be easier to find. The thing is that there's some "tricks" and "pitfalls" to the newbies like me when they try to install that Asus USB drivers. At first I couldn't install, I even thougt that they were not compatible with my Windows (I use Vista 32, that is famous as being really a ***** when comes up to install things). So, for ADB, in that moment I just gave up from Asus Android USB Drivers and installed Asus Pad PC Suite, that included ADB drivers, but apparently no APX. At that moment, when I was only looking for ADB, worked. But later, trying APX, I got really stucked. Just found the solution many sleepless nights later.
Please just notice that I am not an expert in anything: just a cat-crazy lady that works as text revisor and does patchwork quilts and amigurumi dolls at the free time. So, I'm afraid I can't help much on the technical side if any doubt appear (unless your doubt is about feeding an elder toothless cat with a bird syringe, syntax of verbs in Portuguese or about brands of wool and thimbles). Also can't assure this method will work for everyone.
Anyway, I'll be glad to help with the few I know. I hope these instructions can be of any use and save people from stress. Best wishes and happy APX'ing.
********************HOW TO INSTALL APX FOR TF700 IN WINDOWS************************
***One important warning I give to the stucked TF700 owners that are searching for APX drivers: DO NOT TRY TO USE UNIVERSAL NAKED DRIVERS! They will not work! Universal Naked Drivers are great, but made for TF101, Prime, Nexus, etc, etc, NOT for TF700 Infinity! So, any attempt to use that drivers, at the moment (March 2014) will give you nothing more than a last-longing splitting headache.
Use the pack from Asus: "Asus Android USB Drivers", download the pack from Asus website (go there, is one of the few downloads for Windows available for TF700)***
I'll just enumerate what I did and what I paid attention as necessary steps to install APX drivers for TF700 in Windows. If someone wants to give a try and follow them, there's the description.
1) Your device must be with the USB Debugging Mode enabled. This is found under Developer Options (enable it if Developer Options doesn't show by tapping 7 times the build number, under Settings/About).
2) Asus drivers dislike Windows auto-install. When we plug our device in USB (just normally, Android running), he is recognized and Windows auto-install prompts a message offering to locate and install drivers. IGNORE IT, SKIP IT. Just tell windows that will install later (there's an option for that, at least in Vista 32).
3) Then go to Control Panel, and choose "System". There, choose "Device Manager". There, look for something Asus, if you don't have previously installed any (if you have, uninstall it first, reboot the PC, then plug the tablet via USB). If you haven't installed anything and your tablet is connected, will appear something like "Asus ADB Interface", marked as not working by Windows.
4) Then, right-click over it and ask for "Update Driver". It will open a new prompt asking if you want Windows to search it automatically or if you want to search driver files manually from other sources. Say you want to search it manually. After, say you want to choose from drivers list (bottom option) and then say "Have Disk". And then direct Windows to search the driver in the directory where "Asus Android USB Drivers for Windows" are (uncompressed directory, please). The drivers file is the "android_winsub.inf", under the sub-directory "Android". Choose the file and proceed the installing.
5) This should install ADB. But, wait: the problem is the APX, not the ADB, right??? So, what does all this is for?
6) Now the magic (or, what so magically happened to me): reboot the tablet into APX Mode (power+volume up). And then another window of APX auto-install will pop. IGNORE IT.
7) Again, go to System/Device Manager. APX should appear there as "Asus Transformer Infinity APX Interface" or something fancy alike (if appear only "APX", something gone wrong and the installation already failed, at least here was this way). Is also marked as not working by Windows. You should again right-click and choose "Update Driver"
8) Repeat the process, if necessary direct Windows to the directory where the android_winsub.inf is (the one that was into the Asus Android USB Drivers pack). From this point my Windows installed automatically some parts, but, as I could notice, installed the driver from that same file of before.
This installed APX for me, and I could run wheelie and NVFlash!
So, I honestly hope this helps. I know it arrives too late for many, but still if can help somebody at least a little bit, I'll be happy.
Click to expand...
Click to collapse
So when I did the original unlock, root and flash of the CROMBi kit Kit ROM a short while ago, I followed all the instructions for it in the forum. Does this mean that I still need to install the APX drivers? IF I don't what am I missing?
Cary
Sorry by the delay, I'm back (got sick these days)
Hi, people: sorry for the delay. I got really sick these days (I am under treatment right now, getting better, enjoying the lovely painkillers to get a fine time to answer here. Perhaps the last exhibition of patchwork and quilting has been much of excitement to me ***the troubles of being an old lady, that's it...XDDD ***)
About Universal Naked Drivers: by some time it WERE some versions available, and one of them patched for TF700T. Thing is, that patched version is not available anymore: at NVFlash page of Android. Mobi team, the link leads nowhere. I don't know if there was some sort of unstability of sorts, but the truth is that version is not available anymore, at least I could not find it.
About Asus Android USB Drivers: besides I remember have taken the pack from Asus site, just checked it and there's nothing there now. I don't know if Asus pulled it to force us to use the Asus PC Suite instead or if I was just mistaken, but I found nothing this time.
BUT, THERE'S HOPE! And coming right here from XDA. I found a working link at this site to Asus Anroid USB Drivers zip pack. I downloaded now with XDA link and the file is of the same size of that I have, so I figure out that is the same.
Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=1245225&d=1344272324
I am at the tablet, comparing the file of the link with one in my tools memory card, but I'll check tomorrow/today if the files are really the same in my PC (need enjoy the painkillers to sleep too, so now I'll take a nap). If they are the same, I'll update my message with XDA link. If perhaps they are not the same, I'll upload the pack I have (and that's work) somewhere and post the link here.
And about APX...It's necessary to run NVFlash and wheelie, that grant a more trustworthy security to TF700T tablets ( these are for recovering the tablet after a softbrick). Install ROM, unlock, root, etc, is not done using APX, but the best recovery afer some tragedy, surely it is.
Again, friends, sorry about the delay in replying, I was needing some meds and rest. Best wishes to everbody.
drhode said:
Hi, people: sorry for the delay. I got really sick these days (I am under treatment right now, getting better, enjoying the lovely painkillers to get a fine time to answer here. Perhaps the last exhibition of patchwork and quilting has been much of excitement to me ***the troubles of being an old lady, that's it...XDDD ***)
About Universal Naked Drivers: by some time it WERE some versions available, and one of them patched for TF700T. Thing is, that patched version is not available anymore: at NVFlash page of Android. Mobi team, the link leads nowhere. I don't know if there was some sort of unstability of sorts, but the truth is that version is not available anymore, at least I could not find it.
About Asus Android USB Drivers: besides I remember have taken the pack from Asus site, just checked it and there's nothing there now. I don't know if Asus pulled it to force us to use the Asus PC Suite instead or if I was just mistaken, but I found nothing this time.
BUT, THERE'S HOPE! And coming right here from XDA. I found a working link at this site to Asus Anroid USB Drivers zip pack. I downloaded now with XDA link and the file is of the same size of that I have, so I figure out that is the same.
Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=1245225&d=1344272324
I am at the tablet, comparing the file of the link with one in my tools memory card, but I'll check tomorrow/today if the files are really the same in my PC (need enjoy the painkillers to sleep too, so now I'll take a nap). If they are the same, I'll update my message with XDA link. If perhaps they are not the same, I'll upload the pack I have (and that's work) somewhere and post the link here.
And about APX...It's necessary to run NVFlash and wheelie, that grant a more trustworthy security to TF700T tablets ( these are for recovering the tablet after a softbrick). Install ROM, unlock, root, etc, is not done using APX, but the best recovery afer some tragedy, surely it is.
Again, friends, sorry about the delay in replying, I was needing some meds and rest. Best wishes to everbody.
Click to expand...
Click to collapse
Thank you drhode! I found the same link.
I wish you all the best for your health!
berndblb said:
Thank you drhode! I found the same link.
I wish you all the best for your health!
Click to expand...
Click to collapse
There are two drivers for the tf700. The portable driver is for fastboot and adb. The second driver is for andriod usb which is for apx.. You can find the apx driver on the sdk website...
@drhode
I hope that you are getting better soon and wish everything going well for you...
LetMeKnow said:
There are two drivers for the tf700. The portable driver is for fastboot and adb. The second driver is for andriod usb which is for apx.. You can find the apx driver on the sdk website...
@drhode
I hope that you are getting better soon and wish everything going well for you...
Click to expand...
Click to collapse
What is a portable driver????
And where have you been the last week or so? We're still testing f2fs and you're on to the next trick already? Bionic???
Good to see you
berndblb said:
What is a portable driver????
And where have you been the last week or so? We're still testing f2fs and you're on to the next trick already? Bionic???
Good to see you
Click to expand...
Click to collapse
When you plug in your tf700, win recognizes it as a portable device so you can communicate with it. As the same time, there is an android driver that you can can configure for apx mode. Otherwise, you have to manually cofigure to apx when you want to use it... I believed that @drhode is trying to explain in her post...
My f2fs is still running great and looking for new stuff to play around with but it is not as convience as before because I can not test them without the tf700 next to me...
I think I'm more confused now than I was before I read this thread. I've checked every version of UND drivers I could find and none had the ids _that posted. None of the patched drivers seem to exist anymore. I'm hoping someone could be more specific about manually configuring the above linked drivers for apx mode in Windows. Failing that would it be possible/advisable to generate the NVFlash files using a Linux live usb key? I've been reading up on Linux for the past year but have yet to actually do anything with it. Many thanks to anybody taking the time.
a-t0m said:
I think I'm more confused now than I was before I read this thread. I've checked every version of UND drivers I could find and none had the ids _that posted. None of the patched drivers seem to exist anymore. I'm hoping someone could be more specific about manually configuring the above linked drivers for apx mode in Windows. Failing that would it be possible/advisable to generate the NVFlash files using a Linux live usb key? I've been reading up on Linux for the past year but have yet to actually do anything with it. Many thanks to anybody taking the time.
Click to expand...
Click to collapse
I just want to share my experience with apx driver.
I was able to install apx driver when I boot into flatline's recovery first, and then install UDN 0.72 driver in windows.
I had trouble when I was following flatline's method for pulling blobs files with adb commands (no devices found).
My Asus Android USB Drivers didn't install apx driver for windows, so I used UDN 0.72 driver from http://forum.xda-developers.com/showthread.php?t=1426502
The zip file should contains "android_apxusb.inf". Open that file, the you should see similar text of what _that posted
" SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX "
From the file ->
" Asus Transformer Prime TF201 APX & ADB Interface
%AsusTransformerPrimeAPXInterface% = USB_Install, USB\VID_0955&PID_7330 "
Follow OP drhode's unistall driver instruction for a clean start over (usb debug mode on).
"control panel -> device manager->asus android devices->right click on asus android....->uninstall->
a window prompt of unistall confimation, check the box of delete this device's driver->ok->
after unistalled, unplug tf700 usb connection to pc, restart windows.
after windows restart, Plug in normal booted tf700 and update the driver(either *.inf from UDN 0.72 or Asus Android USB Drivers)
Guide for win7 driver update
You can turn off driver signature check during the installation just incase some weird driver situation
Open cmd.exe type " bcdedit /set TESTSIGNING ON " and restart windows.
Reboot tf700 into flatline's recovery. If yellow ! appears in control panel, then update the driver again( w/*.inf from UDN 0.72 choose Prime).
Just restart windows after every driver install/uninstall.
It is just a regular driver update/install, nothing more special about it.
Btw, I'm using Win 7 64bit, so I'm not sure if that's the same instruction for windows 8.
I hope you can get it to work soon.
Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part
You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine
Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.
Hi all, title says it all really, I can't connect my tf101 to Windows 7, the PC beeps when I plug it in and that's it, no dialog saying usb device found or anything, I've Googled for hours and tried installing Asus official drivers as well as the recommended Naked ones but zilch works, adb doesn't list any devices and I'm at a loss as to what to try next - any help much appreciated
Would love a response on this as well...
Received the TF-101 as a gift yesterday and wanted to root it using OneClickRecoverV0.4.2 (run as admin) on my 64-bit Windows 7 machine. Device isn't showing up in "adb devices"
After researching extensively, I have tried:
- Naked drivers
- ASUS sync
- Latest SDK
I can confirm that the device is successfully entering APX mode by looking at the Safely Eject/Remove hardware taskbar, although I only see it in Device Manager when the TF-101 is fully booted up (non-APX mode). USB Debugging is checked off as well. I'm full charged and I've tried multiple USB ports.
What am I missing here? This is frustrating!