Related
Hi all,
I am noticing something with nexus s.
When in recovery or in normal homescreen, my nexus s communicates properly with adb commands
But there seems to be no communication from the nexus s when in fastboot mode.
Everytime I enter a fastboot command, I always get a "waiting for device" and nothing happens.
Am I missing something?
Thanks.
Heeter
If your PC is running Linux then you will need to be root.
No I am running windows 7
I got the Android 1.0 driver. Windows Device manager recognizes that my phone is hooked up,
But when I type in "fastboot devices" it is not listed there.
Thanks
Heeter
When I hook up my Nexus S in fastboot mode, I see this at the bottom:
Code:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Everytime I unplug/replug USB wire, another "STANDARD_SET_CONFIGURATION" line gets added
I type "fastboot devices" into fastboot, and my Nexus S does not show up.
The phone is currently unlocked, but I would like to lock to reset it and start from factory rogers setup again.
Any help would be greatly appreciated.
Thanks
Heeter
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
rubbamade said:
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
Click to expand...
Click to collapse
I do have that already, rubbamade.
My Device Mangler is recognizing Android 1.0, and has the drivers for that I took from PDAnet.
The PDAnet itself couldn't install properly, so I extracted the drivers from the package and manually installed them through the Device Mangler.
I still cannot connect to fastboot.
Heeter
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
I guess you made your decision already in getting rid of windows lol. Anyway goodluck with the fastboot issue. And I hope the 3G issue is looooooog gone from your life. Take it easy
Arnel
Sent from my Nexus S using Tapatalk
LOLOL,
A whole bunch of thanks for that radio to you again
Heeter
Good choice ditching windows. Lol
Offtopic: how is debian compared to Ubuntu concerning repo n 3rd party drivers? Seriously considering switching to debian since Ubuntu adopted the crapy Unity
Sent from my Nexus S using Tapatalk
The driver isnt right if your phone wont show. You have to let windows find the correct driver out of the drivers you point it to. Either point it to x64 or x86 directory only. No further. Windows will find it.
Go to the fastboot thread in development and get the drivers.
Uncle Jimmy says hello
Heeter, it's maybe a bit late but unless you're really strapped for disk space you can keep Windows and create a separate partition for Linux, using the grub bootloader to choose between the two. I'm a Linux user myself (mostly Arch but I love to test most new distros) but I have lots of disk space and I keep an up-to-date Windows 7 installed for testing purposes and gaming.
Since - I have to admit it - I suck at most games, my Windows doesn't get used much but I don't begrudge the space it takes up. On Debian you should have less trouble with the adk and drivers - here's a good post at Howtoforge about using the adk http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-debian-squeeze
Heeter said:
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
Click to expand...
Click to collapse
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
bender_123 said:
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
Click to expand...
Click to collapse
I tried that like 50 flippin times! everytime, PDAnet stays locked up during the pulling driver area. I have come back half hour later, still not complete. Then, when I unplug the cable, it spits out an error, and uninstalls itself.
What I ended up doing was, during the PDAnet install, it creats a root folder in C:/Program Files/PDAnet (or whatever it is). Now when it got stuck there, I went into that root folder, copied the "usb-win" driver package from there and set it aside. Then I went into the Device Mangler, and right clicked and manually installed the PDAnet driver.
Hiya Gun26, Thanks for that link. I am actually a site supporter on that site, if you search up "Heeter" over there. Been for a couple of years now.
I guess I could go back to dual booting, haven't done that in a long while either.
Heeter
That was just a suggestion about the dual booting - if you enjoy gaming, why give it up? Linux and Mac may be great (and BSD let's not forget) but for gaming it's either Windows or a console. I don't think you'll have any trouble with the adk and drivers on Debian. Good to hear about your connection to Howto Forge - it's a really useful site.
Thanks for that Gun,
I haven't had time to move back to Debian, and I really do like gaming once in a while.
I should be up and running dual boot this weekend.
Thanks again, guys.
Heeter
i'm having this same problem, it's rather annoying
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Firmware/Rockchip_CPU_based/Rockchip_Batch_Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Hi, the multiupload link seems down, would it be possible to re-up? thanks!
And how exactly are you supposed to install the drivers from the driver folder? Because those are not Runable files, theyre drivers, with no install command. So, my daughters nextbook is bricked, wont install drivers(says not successfully installed after i plug it in) and there is no way to install the drivers from the batch file. Anything you left out??? Id like to unbrick this thing. Thanks..
SOLVED
I found out how to install the drivers on windows 7!
Follow this:
click the start button > type in the search box right above the start button "device manager"
(make sure the tablet is plugged in and in USB MODE)
right click the tablet or unknown device
select install/update driver manually
browse for the driver in the download folder then it should be updated
worked for me.
Nextbook 8 stuck in bootloop
I am a noob. My Nextbook 8 is stuck in bootloop, the last app i downloaded was firefox. Ive read that this can be fixed by starting safe mode and doing a factory reset, how do i do this?!? Im desperate, and would greatly appreciate any help that works, thanks.
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.
Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
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.