Related
hey just wondering about adb i need to download and adb and i am assuming some sort of device drivers i was wondering if anyone has a link for this or what versions i need and how i get adb to work before when i rooted phone i just imputed everything in the terminal emulator?
Check out guide, getting adb setup in Asus dev section. It's pretty good.
http://forum.xda-developers.com/showthread.php?t=1124217
Closing as a simple search would give you answers to these questions.
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?!
Just wanted to let everyone know who was trying to follow root guides that have you adb su and busybox. I tried for hours and couldn't get mine listed under devices with the driver being correct, reinstalled android sdk, deleted drivers then forced win7x64 to use the ones i found in forums. Still nothing. Then I installed Asus Sync and it said it still needed to install drivers as part of the install even though I had them all installed in control panel. Instantly it was listed under devices and I had no trouble using adb to push su and busybox. I have a b60 transformer though.
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?
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?