I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.
Hi! Search in transformer's support page, you can find the drivers there
Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?
Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.
I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.
ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable
That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.
is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.
You sir are the man! Thanks for your time.
To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck
This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193
I set Windows to look for driver in c:. After a while one was installed and worked.
What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W
Related
how do u root with z4root with out being able in install any 3rd party apps
!!
please help!!!!
Do alittle more research on the whole root process. 2.2 is a little weird but instructions are out there. I would not use any app to root Basically you need to find the right zip and install that with the button recovery.
Also don't expect an immediate response. Just because no one respond in 5 minutes does not mean they won't
Sent from my SAMSUNG-SGH-I897 using XDA App
I had to use a side loading app to get z4root installed on my phone and then rooted it from there.
Google "captivate side loading" and you should be able to find the app you need the name escapes me at the moment.
Sent from my SAMSUNG-SGH-I897
Sideload Wonder Machine from Android Central worked great for me.
http://forum.androidcentral.com/and...40770-ac-sideload-wonder-machine-windows.html
Watch this... http://www.youtube.com/watch?v=LFHLVF1aA0Q
If you can get an app to load and work on your machine to side load the apps you are ready to go. If not, i.e. Vista 64bit is an issue for DroidExplorer, you can use simple adb commands.
Like the video says... assuming you have the SDK and drivers installed. This is also assuming a computer running windows, if you are running Linux well... if you are running Linux you should be able to translate
1. Open a command prompt
2. change directories to the platform-tools directory where ever you installed the 3. SDK. i.e. C:\android-sdk\platform-tools
4. Turn usb debuging On via the phone Settings->Applications->Development and check Usb debuging
5. connect your phone to the PC with the usb cable
6. type adb devices
If you then see something like this you are ok to continue, if not you need to figure out what is wrong with either your SDK install or your driver install
List of devices attached
100049b90495 device
7. type adb install <location of your z4root.apk file> i.e. adb install c:\apks\z4root.apk
8. You will see adb copy the file and install to the phone. (If it fails start reading more in the dev section here. All the answers are there)
9. Disconnect your phone and open up z4Root on the phone and root it.
That should help. All of the steps above and A LOT more are in the dev section here, as posted above search and read and ye shall have all the fun you want.
+1 Sideload wonder machine
Follow the rooting guide on youtube from mobiletechvideo(?), he has a bunch of videos, one is how to flash cognition based rom onto your phone (but the first step is rooting, so you could skip the rest if you didn't want to flash a rom).
Hope it helps
http://capfaq.com/w/Root
My Transformer informed me of an OTA update, which I tried to perform. It stuck on the boot screen and wouldn't go any further. I managed to wipe it and get it going again by switching off and pressing power and volume down, so I rebuilt it and it again wanted to do the update - with the same result.
I tried side-loading the update and again, it froze, so I downloaded and ran NVFLASHTF and now I can't get anything on the display whatsoever. All I can do is connect it to my PC and it makes the familiar connection sound and I can get to the SD card, but nothing else.
I need someone to show me what to do step-by-step as if I was completely stupid (which I obviously am!).
Please help if you can.
TIA
the nvflash sticky in the dev section includes a youtube video.
although the most likely reason your nvflash didn't work, is you extracted the files in the wrong place. make sure they are in the same place as the download.bat file.
Sent from my Transformer TF101 using Tapatalk
I have all the nvflash files in the same folder as extracted from the .zip file. I even have Prime 1.6 in the folder.
All I seem to be able to do is press the power button and either Up-vol or down-vol (or both) and the computer disconnects and immediately reconnects. When I run the download.bat file, it seems to run and complete the formatting and then download something and the dos box disappears at that stage. The tablet is showing the following...
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 027c100040a0b2d7
Click to expand...
Click to collapse
That is the only thing I can get to display - and, of course, it stays like this until I try to reboot again.
copy and paste what you get when you run the batch file into here...once it finishes
Pretty sure the tf should reboot on its own if done right.
Did you also check the md5sum of the downloaded files?
I followed these instructions..worked perfectly
http://tabletroms.com/forums/transf...ock-3-1-stock-3-2-recovery-roms.html#post9968
The Dos box disappears when it finishes so I can't paste it here and yes, I checked the files. In fact, I tried it on three different PCs (W7 64-bit, W7 32-bit and XP Pro 32-bit), all without success.
Have you plugged it straight to power and switch it on?
Yes - no difference.
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
maybe try a different usb port, I have 4 ports on the front of my pc but for some reason only ONE port works when i try to nvflash,also have problems if I use a hub or extend the cable in any way
Malandro2011 said:
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
Click to expand...
Click to collapse
Ok, the second option got me a little bit of info. Bootloader.bin is installing but it is telling me that the file 'recovery.img' is not found.
you can prevent the dos window from closing by starting the command via command line.
start > run > cmd (enter)
dir c:\where\nvflash\is\located (enter)
download.bat (enter)
OK, it's official - I'm an idiot!
I had downloaded the nvflash version of Prime 1.6 but hadn't extracted the files! I now have a working version of Prime 1.6 and am restoring the data as I type.
Thanks for all your help, especially the suggestion of running download from a dos prompt, which let me see where I was going wrong.
Excellent!
Glad it's all sorted
Hello, i just got my new samsung 7 plus with honeycome 3.2 and im loving it
I want to know what is the step by step instruction to rooting my device using adb?
the root.zip i found on here dont work for me. when i save the file to /sdcard and n reboot n go into wher i applie the zip from sdcard it shows no files at all on my card. i bought the 16gb version of this tab so i dont have the externel sdcard. i thought that i read one the forum you can only use the externel card not the interel. i believe they added the folder /sdcard to the internel drive and thats why it not viewing.
The rooting instructions say to put it on an "external" sdcard for a reason as recovery will not recognize the internal storage. Do you have adb installed on your computer and at least know how to use it? If not it is going to be way easier for you to just go and spend the $10 for an 8 GB sdcard and install it that way.
I can at least get you part way, installing the sdk and jdk. Here are the instructions for installing the android sdk (adb) direct from google. You also need the java jdk installed on your commputer and google has a link in their instructions.
http://developer.android.com/sdk/installing.html
You first need the proper usb drivers installed and not exactly sure on how to do that. I already had the android usb drivers installed on my computer for my phone and I just let the compter install whatever else it needed the first time I connected my tab to it.
You will need usb debugging turned in your settings and then power the tab off. You would then plug the usb cable into the tab and computer then boot it into recovery. Once into recovery Mount/System. You then run adb in a command window and change the drive to the platform-tools directory where adb resides. It would look something like this in a command window (c:\android-sdk-windows\ is how I set my computer up yours may be different):
cd c:\android-sdk-windows\platform-tools
To check and see if your device is recognized by adb run the command:
adb devices
If nothing is listed then adb isn't recognizing the device and you would need to troubleshoot your installation or boot method.
As far as installing the root.zip file I'm not sure as I've never had to do that before as I've always had an external sdcard on my devices. Maybe someone else can take you thru the last step. I believe all you would do is push the file inside the zip folder over to the tab. The su file inside the root.zip folder needs to be in the same directory as adb, platform-tools directory.
adb push su /system/bin
I'm not sure if you need to change permissions on this file or not and that is done thru a chmod command in adb shell but not sure of the proper code to use for the GTab to do this. For my phone setting permissions looks like this:
adb shell
cd /system/bin
chmod 0644 Su
exit
Do not use this chmod as I'm not sure it will work on the GTab or what it will do to it, it just an example.
In summary these are the basic steps you are trying to accomplish:
1. Install Java JDK
2. Install Android SDK
3. Install USB drivers
4. Turn USB debugging on in Tabs settings
5. Boot Tab into recovery while connected to PC
6. Mount/System in recovery
7. ADB push su file to system/bin
8. Set permissions of su???
9. Exit adb
10. Reboot phone and install superuser and busy box from market
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
ronlsjr said:
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
Click to expand...
Click to collapse
Yes any sdcard will do and that is the easiest way. Though I think everyone should learn how to use adb anyways as it is useful especially if you get into modding.
Yes i do want to learn how to use adb. My desire is to become a developer.
Sent from my GT-P6210 using Tapatalk
Just follow the link I provided previously to the android developers site and follow the instructions. You will first have to have Java JDK installed and a link to that is provided on the android developers website in the link. Once JDK is installed download and install the SDK. It will only put the basic functions onto your computer and you will have to install the rest through SDK Manager, this can take a while, up to an hour or so depending on what packages you want to install. At the minimum you would want the Android 3.2 API (GTab 7+ uses this) and the Google USB drivers and then any other API's for phones you may have. I myself installed all the API's as my first phone had Donut (Android 1.6).
I know this may be a stupid question but why root? what special features does it give you? I am not sure If I want to or not.
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
don't get confused by the lingo...
Noah321 said:
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
Click to expand...
Click to collapse
There's a difference between "flashing a ROM" and "adding root access".
A custom ROM implies someone has taken the stock software infrastructure, altered/tailored/customized it, and packaged it for others to easily use.
"Rooting" a device just simply gives you access to certain folders, permissions, files, etc.
It's like giving yourself Admin Rights to your work computer (assuming you're over 18 and/or working).
It allows you to do things that the manufacture probably didn't want you to do - like delete "bloatware" (unwanted apps).
If helpful, click "Thanks"
hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "
im on recovery and when i run adb devices it just blank. any walk through is much appreciated!
Do yo have USB debugging on?
I dont know because i was about to flash a new rom so i did a full wipe already
Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.
i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe
i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.
I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!
Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!
If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.
thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...
still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.
Hi! I'm running CM 10.2 Android 4.3+.. My firmware is over 10.6.. i installed flatline NVflash for tf300t and after installing Android Root bootloader I chose from the flatline recovery the generate bloobs( I followed the tutorial)The blobs generating was Done and the recovery sad something like bloobs ware uploaded to server. On that menu I tried to run the adb pull comment...that don't work..adb says no device.I booted in Android and I tried again the adb pull.This time adb sad remote object doesn't exist.I checked with Rooted Explorer if the Android Root folder exist in /dara/media/AndrooidRoot. IT DOES! After that I tried to copy that folder on my SD card. On PC shows it a 1 KB file. How I can extract that folder with adb? Adb says something like remote object doesn't exist! Please Help..Sorry for my bad English!
TheKid1997x said:
Hi! I'm running CM 10.2 Android 4.3+.. My firmware is over 10.6.. i installed flatline NVflash for tf300t and after installing Android Root bootloader I chose from the flatline recovery the generate bloobs( I followed the tutorial)The blobs generating was Done and the recovery sad something like bloobs ware uploaded to server. On that menu I tried to run the adb pull comment...that don't work..adb says no device.I booted in Android and I tried again the adb pull.This time adb sad remote object doesn't exist.I checked with Rooted Explorer if the Android Root folder exist in /dara/media/AndrooidRoot. IT DOES! After that I tried to copy that folder on my SD card. On PC shows it a 1 KB file. How I can extract that folder with adb? Adb says something like remote object doesn't exist! Please Help..Sorry for my bad English!
Click to expand...
Click to collapse
More details needed to figure out what your problem is. What OS are you using on your PC? Right now, it sounds like your ADB drivers aren't working correctly. Can you post a screenshot of your cmd commands? At the upload server screen, you should try the command "adb devices" on your pc. If that does not return a serial number, your PC is not communicating with your tab. Likely cause: bad ADB drivers. You can certainly copy the folder to your SD card, but make sure you have permission to do so with your explorer.
graphdarnell said:
More details needed to figure out what your problem is. What OS are you using on your PC? Right now, it sounds like your ADB drivers aren't working correctly. Can you post a screenshot of your cmd commands? At the upload server screen, you should try the command "adb devices" on your pc. If that does not return a serial number, your PC is not communicating with your tab. Likely cause: bad ADB drivers. You can certainly copy the folder to your SD card, but make sure you have permission to do so with your explorer.
Click to expand...
Click to collapse
I'm running windows 8. When the tablet is in Android the pc reconize adb device. I tried this command adb pull/data/media/AndroidRoot ( the comand that is on the tutorial. Can you mace a screenshot of that read and write permisions? I don't understand that r/w....I will try this on Ubuntu 13.xx ( 04 or 10) It's ok in linux to try this...In linux the adb commands are different?
TheKid1997x said:
I'm running windows 8. When the tablet is in Android the pc reconize adb device. I tried this command adb pull/data/media/AndroidRoot ( the comand that is on the tutorial. Can you mace a screenshot of that read and write permisions? I don't understand that r/w....I will try this on Ubuntu 13.xx ( 04 or 10) It's ok in linux to try this...In linux the adb commands are different?
Click to expand...
Click to collapse
They're the same in Linux, but you've gotta to have those ADB drivers in there too. Are you using the 64-bit version? When you say the pc recognized the device, does it return a serial number when you query "adb devices"? If it does, you don't need Ubuntu. If the problem persists, then issue of compatibility with Win 8.
Hi,
I am using this thread since my question is about NVflash
I am new to custom roms/fw on TF300T. I have latest Android 4.2.1 and bootloader (10.6.1.27.5) and it's still locked.
Do I have to do anything else than unlock my bootloader with app provided by ASUS before starting this NVflash procedure? Is root access required?
Do I need specific drivers for Win7 32-bit? I am familiar with ADB/Fastboot..
Thanks for advance!