Related
Hello,
Firstly, this is a long explanation, so, for the lazy, I have put a TL;DR version at the bottom of the post. Scroll there to get the general idea.
I have attempted to root my Transformer numerous times now. It is a serial number B60.
I am running Windows XP, so I am trying to use Brk's script.
I am using v6.3.1 of the script, because I have the latest OTA update.
This is my 'Build number' in 'About tablet': HTJ85B.US_epad-8.6.5.9-20110816
I have been trying this method since 8.6.5.6 and at the time I used v6.1 of the script (other methods including a VirtualBox run of rebound's One-Click Universal root linux live-CD).
When I run the script, I follow the instructions exactly.
I backup (option 1), then reboot into APK mode again.
Then, I flash unsecure boot.img (option 4) and CWM. I have tried only installing unsecure boot.img and it has made no difference.
Flashing the unsecure boot.img reports success and flashing CWM reports success.
Next, I reboot into regular Android OS.
Development mode is on for the USB. I check to see if ADB is working (option 7).
ADB is not working. The reason? I do not have root. I have installed the Terminal Emulator application. When I run the command 'su', it says 'Permission denied'.
I have also tried the Transformer pure root tw/us/ww/de/jp (8.4.4.5/11/12/8.6.5.6/7/9) and it has the same results. That is, flashing unsecure boot reports success, as does flashing CWM, but I have no root.
Additionally, I tried a VirtualBox run of rebound's One-Click Universal root linux live-CD. That failed, because I couldn't capture the Transformer as a USB device).
TL;DR version
I have tried several different methods of rooting my Transformer. It is serial #: B60 series running HTJ85B.US_epad-8.6.5.9-20110816.
All drivers are set up completely.
All steps are followed
All steps report success
Root is not granted
ADB will not work
???
More details at the top
One last thing
The only thing that I can think may possibly explain this problem is that I do not have an SD card in the tablet. I know some guides specify that you need one and other ones do not say anything.
I do not think that this is the cause, chiefly because everything reports 'success'.
Are these results typical of what happens when someone tries to flash a B70 or B80 model? If so, is it possible that, although I have a B60 series model, the innards are that of the B70/80 series and thus, incompatible?
I hope that posting my results and problems will help solve someone else's problem at the very least.
At this point, even someone just replying and letting me know that I have done everything correctly would be nice.
Have you got the ASUS drivers installed in your pc? i.e. can you connect and sync your device normally?
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Success!
AustinMartin said:
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Click to expand...
Click to collapse
Wow! I feel like a complete idiot...
I downloaded and installed the "Asus Eee PAD Transformer TF101 USB Driver" which I thought was what the PC Suite was. I was wrong.
Everything is working after installing the PC Suite and then trying ADB.
I definitely wrote way too much...
telekenetix said:
I definitely wrote way too much...
Click to expand...
Click to collapse
But that is how we learn, from seeing what others have done...
did you enable development ? it is for adb
I found that out early on that the PC Sync app is essentially just a front-end for ADB, since the app wouldn't work when I had debugging enabled on the TF.
mashi said:
did you enable development ? it is for adb
Click to expand...
Click to collapse
Yes. The trouble was that the PC Suite wasn't installed. I thought I had it installed, but it turned out that I only installed the drivers. Everything is running smoothly now.
The thing that still seems odd to me is that I tested to see if I had root, using the terminal application. It said "Permission denied". But, after installing the PC suite, adb was able to function and apparently did something magical.
So, I have to ask. What is this black magic?!
Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Since ICS is on the way you will get you bootloader upgraded most likely. Then the unlock APK should follow if Asus holds up there end.
This will allows for comminucation with your tablet and phones (execpt moto for now)
Hope Asus hits you up soon with the unlock.
Cheers!
DDMS ok on my evo 3D with your driver, will test my transformer later
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
keyra74 said:
DDMS ok on my evo 3D with your driver, will test my transformer later
Click to expand...
Click to collapse
Thanks for the feedback
fonix232 said:
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
Click to expand...
Click to collapse
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
1wayjonny said:
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
Click to expand...
Click to collapse
Hmm, then please remove the Fastboot options from the original Transformer's log, as we have no access to it yet ;D Maybe with a modified u-boot, but that needs some time.
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
gnufabio said:
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
Click to expand...
Click to collapse
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
keyra74 said:
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
Click to expand...
Click to collapse
Thanks for the feedback!
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
shady503403 said:
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
Click to expand...
Click to collapse
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
mrevankyle said:
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
Click to expand...
Click to collapse
You also get that message if you have the SDK installed but not in your path and you are trying to run the command outside of the Android\android-sdk\platform-tools\ directory where the adb command resides. I have posted a guide for installing the SDK and then installing these drivers in the Roach's Clockwork Mod Recovery thread. I was trying to help solitude65 who installed a Recovery that only reads internal apparently after he wiped the internal sdcard or didn't realize he needed a ROM on the internal sdcard. Not sure how much of it will apply to the Prime as I have a TF101 and used it to confirm the steps I posted over there.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
1wayjonny said:
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
Thanks for the feedback!
Click to expand...
Click to collapse
Can you tell me specifically what USB config you are referring to and where to find it?
Thank you SO much! I was pulling my hair out, trying to find drivers for my TF101 in recovery mode, and I couldn't.. But these helped me immediately, and did the job!
Thank you!
I am on Windows 8 and couldn't get this installed with an error about missing the hash for the file. It of course is missing, since this isn't a signed driver.
I followed the instructions at http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/ and was able to install the driver. If you're using Windows 8, you can do the same to install these unsigned drivers (or any other unsigned drivers for that matter).
Updated version, feedback helpful
1wayjonny said:
Updated version, feedback helpful
Click to expand...
Click to collapse
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Hammerfest said:
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Click to expand...
Click to collapse
No worries thanks for any help.
I having an issue trying to remove the previous version to the latest one I just sold my tf201 and today i got the nexus7 can someone help on a step by step on what to do in device manager. Now my galaxy nexus isn't recognized when i write adb devices in cmd after trying to push the latest one
perfecto
i tried rooting and playing with my TF101 when i first got it ages ago, but it was all such a pain in the ass. thank you for making this part a bit simpler.
Tried pointing Device Manager to the folder I unzipped Universal drivers to and got this.
Anyone else?
Hi,
As a brand new owner of TF700T (9.4.5.22), I'd like to root it. I've thus read many posts on this site (and elsewhere, which most often direct to this forum..), in particular one describing the use of debugfs.
One pint that I've still not understood is how to install debugfs: post states to unzip the debugfs files and then to install its drivers. But when I connect my TF700T to PC (with debug tckied and asus sync unchecked), my Win7 64 deos not recongizes the device (unknown device). If I go to device manager, I see a "unknown device" and if I "update its driver", I select the directory of drivers/android from debugfs 1.9, but then I get a message that there's no need to update driver, but still I see "no driver" has been installed for the device, and it remains "unknown".
What do I do wrong ? Or do I need to install Asus Sync on PC, and then simply "exit" it to run adb/debugfs ? ("exit" and not "uninstall") ?
I also tried to check various websites, such as the transformerprimeroot site and its tutorials, but it doesn't help me. I also found another website suggesting to install java sdk+Google SDK, etc., but I've the feeling it's not required for rooting... or is it ?
Thanks in advance for your help,
Ricorico94
Try using the USB driver from the Android SDK. Although that might be the same one that's included in the debugfs root tool.
If the tablet shows up as a ADB composite device or something (don't have the tablet nearby to check, sorry) in the device manager you should be good to go.
If you can run "adb shell" and get anything but an error message, you're good to go. Type "exit" to get out of the shell.
Do not install the Asus Sync software, it can only end in tears
Einride said:
Try using the USB driver from the Android SDK. Although that might be the same one that's included in the debugfs root tool.
Click to expand...
Click to collapse
I'm not sure where to look: on Android SDK pages, it states that to connect devices, you need to go to OEM pages, and when I go follow their link to Asus I get the support page which lists firwraes and Asus Sync, but not drivers separately. Does it mean I need to install first Asus Sync, then remove it ?
I could progress :
- first, it coud interest others to see that despite Asus does not propose USB drivers for TF700T, it still does for TF201. I could download such USB drivers, thoug I did not use them..
- as I had to put my laptop on hibernation, when I switched it on again, I unzipped the USB drivers (nothing more, so probably no effect), I plugged in my TF700T and then it was recognised. I assume the download of the USB drivers did not have any effect, but it's probably linked to laptop exiting hibernation (update of some Win7 processes, I guess?)
- in device Manager, under Portable Devices, it states "ASUS Transformer Pad TF700T" and not "composite ADB" as I could read sometimes..
I'm now starting the debugfs.bat, and it's looking ok so far...so I cross my fingers !
It worked ! My device is now rooted. Thanks a lot to all of you !
I'm having the same problem, but unfortunately without Windows suddenly finding drivers.
In Device Manager, the tablet shows up as ASUS Android Composite ADB Interface, but with no driver installed (and the familiar little yellow warning triangle). Windows can't find drivers automatically, and telling it to find them in DebugfsRoot_v1.8/Drivers/Android doesn't work.
As far as I can tell, the ASUS TF700T page currently has no drivers. (I'm not allowed to link 'cause I'm a new user.) The TF201 page does have drivers, listed under 'USB', but diff tells me they're the same as the ones packaged with the debugfs root tool.
I just wanted to check: am I doing something wrong? It seems like rico also saw no drivers at the ASUS page, but then Windows suddenly recognized his tablet anyway.
I haven't installed the Android SDK because I'd rather not install Java, and from what I can tell it won't make a difference here (and rico didn't need it). But I'm a noob, so please let me know if that's what I have to do!
pyrthas said:
I'm having the same problem, but unfortunately without Windows suddenly finding drivers.
In Device Manager, the tablet shows up as ASUS Android Composite ADB Interface, but with no driver installed (and the familiar little yellow warning triangle). Windows can't find drivers automatically, and telling it to find them in DebugfsRoot_v1.8/Drivers/Android doesn't work.
As far as I can tell, the ASUS TF700T page currently has no drivers. (I'm not allowed to link 'cause I'm a new user.) The TF201 page does have drivers, listed under 'USB', but diff tells me they're the same as the ones packaged with the debugfs root tool.
I just wanted to check: am I doing something wrong? It seems like rico also saw no drivers at the ASUS page, but then Windows suddenly recognized his tablet anyway.
I haven't installed the Android SDK because I'd rather not install Java, and from what I can tell it won't make a difference here (and rico didn't need it). But I'm a noob, so please let me know if that's what I have to do!
Click to expand...
Click to collapse
Here is what I did
get ASUS Sync from the Asus Website
install it
Then uninstall asus sync (it screws things up) but keep the drivers or whatever the other thing it installs is
run debugfs.
GrimSage said:
get ASUS Sync from the Asus Website
Click to expand...
Click to collapse
Aw, I was hoping to avoid that. I'll give it a shot, though. Thanks!
Edit: Looks like it worked fine. For anyone else coming to this, just in case it's not clear, installing ASUS Sync installs three additional things: Adobe Air, MSXML, and USB drivers. Obviously the drivers are the important part. I never plugged the TF700T in while Sync was installed; I immediately uninstalled it (and Air and MSXML, but those shouldn't matter). Then I plugged my tablet in and it was detected just fine (as ASUS Transformer Pad TF700T, rather than ASUS Android Composite ADB Interface, so that matches rico's report).
Thanks again, GrimSage!
Edit again: I was worried that I'd screwed something up, but apparently I just had to actually run the Superuser app before su would work. Yay, I'm rooted and can install Arch Linux.
I can not figure out what the hell I am doing wrong here.
I downloaded the naked driver pack on the guide page labeled 'Drivers TF700: Windows (Patched Universal Naked Driver)'. I unzipped the folder and plugged my TF700 into my computer. I then opened up the Device Manager and clicked on 'Asus Android Devices', then right clicked on 'Asus Android Composite ADB Interface' and pressed uninstall. I checked the 'delete the driver software for this device' and pressed OK.
The drivers uninstalled successfully and I turned off my WiFi card. I then unplugged and re-plugged my TF700 and navigated to 'Other Devices' in the Device Manager. I right clicked on 'Asus Android Composite ADB Interface' and clicked 'update driver software...' and then on 'browse my computer for driver software'.
I then navigated to the folder that I unzipped the driver pack to and tried to install them (clicking the 'include sub-folders' option). No go, I got the error message 'Windows was unable to find the driver software for your device' or something very similar. I then tried specifically pointing to both the i386 and amd64 sub-folders just to see if that wouldn't work somehow but I got the same error message.
What am I doing wrong? I am using a Lenovo G550 (I think) 32-bit laptop running Windows 7. My TF700 is rooted and unlocked but not much else has been done to it.
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
diablodow said:
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
Click to expand...
Click to collapse
That step isn't till later
@OP - let it update the drivers form Windows. That should be fine. As long as you can see the device and it has no errors or warnings around it. you only need the specific drivers when you get to the APX mode, then it will find them.
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
MartyHulskemper said:
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
Click to expand...
Click to collapse
This.
I had big time problems as well with installing these correctly. You need to reboot after uninstalling all old drivers. 1) Hook up Infinity in Android Debug mode 2) uninstall/delete old drivers like you did 3) reboot PC 4) Plug in Infinity again in Android Debug mode 5) install drivers manually through hardware wizard (use have disk option)
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
SOTK said:
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify this? What do you mean by 'repeat this for fastboot mode'?
Sent from my unlocked Transformer Infinity
Still no luck. I uninstalled 'ASUS ABD Interface', unplugged the TF700, restarted the computer, plugged the tablet back in, and tried to uninstall. Told me the same thing, that Windows could not find the driver software.
Any other ideas? I have no clue what to do now...
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Click to expand...
Click to collapse
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Eddie Hicks said:
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Click to expand...
Click to collapse
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Pretoriano80 said:
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
Click to expand...
Click to collapse
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Eddie Hicks said:
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Click to expand...
Click to collapse
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
buhohitr said:
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
Click to expand...
Click to collapse
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Pretoriano80 said:
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Click to expand...
Click to collapse
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Pretoriano80 said:
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Click to expand...
Click to collapse
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
buhohitr said:
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
Click to expand...
Click to collapse
So I see you are trolling this thread too... 98%??? Really??? Can you give a source for that or is that a number you just made up?
NVFlash is useless if you have not already made the backups. But you are completely incorrect if you are suggesting that it is useless even if you have made the backups.
Best not to troll when you clearly do not understand what you are talking about
I_EAT_BABIES said:
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Damn,i can't believe this....When you get to this step " 4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK ... " look on the right bottom of that menu,do you see a "Have Disk" button?.
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Here is a screen capture from my system. Look in the lower right for the HAVE DISK button. Following the directions giving earlier should get you to this point. Just click HAVE DISK and guide to where you have the drivers on your system. You may not see the list of drivers as on the screen capture the first time you do it. Since I have already installed the drivers the system remembered where to look so the drivers are visible. Also make sure to connect your tablet to your computer in order for the device to be visible in device manager. The device in device manager should say android ABD Interface or something of that sort. It took me awhile to get it too
****edit***
Apparently the link opens another page.Once on that page click the little box for the image.
https://www.dropbox.com/s/ykuv2ac6zxdln7i/driver_update.JPG
As of the time of this reply I have got the Fasboot drivers installed, but I still saw now "have disk" option. After turning UAC off (don't know how that got back on) I was still just selecting a folder as shown in my previous screenshot.
About to try APX, will post results.
Got it! Thank you guys so much, I really appreciate it. This was seriously driving me crazy, but I still don't understand how we are looking at different menus.
Hi
So I've just download a rom and superscript on my eee pad and went into cwm and run the superscript. Unfortunately, that wiped everything from my tablet so, I tried to install the rom but the files deleted and I put the rom on an external sd but cwm won't read that. The only thing I can do is access recovery and that's it :/
Can anyone help please!? Thankyou!
I've just got this problem fixed with help from user gee one. Check my recent posts.
rohaan06 said:
Hi
So I've just download a rom and superscript on my eee pad and went into cwm and run the superscript. Unfortunately, that wiped everything from my tablet so, I tried to install the rom but the files deleted and I put the rom on an external sd but cwm won't read that. The only thing I can do is access recovery and that's it :/
Can anyone help please!? Thankyou!
Click to expand...
Click to collapse
You have to change recovery so Look at easy flasher thread, it helps you to push better recovery/return to stock etc..
Download easy flasher and universal naked drivers and install them, before you install anything read the instructions patiently and then go about working on your tablet.
Remember remove all existing Asus drivers before you install universal naked driver, Also use patience while installing drivers, if windows doesn't install then " unzip the driver files into a folder and go to device manager and select Asus tablet/unknown device and update driver/install driver" .
Once you have installed driver its just the matter of plugging your tablet in APX mode(press volume up and power buttons together for few secs) and clicking on your laptop... remember in APX mode tablet won't show anything than few letters on top in very small font... once you are in APX mode use the easy flasher to go back to stock then you can root and install "twrp" recovery as its the best.
Sent from my Transformer using xda app-developers app