Database Develop

Help with Set Up?

Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.

G1BRICKED said:
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
Click to expand...
Click to collapse
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
nephron said:
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
Click to expand...
Click to collapse

Also at what point are you having issues with setting this up?

nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
Ok so I have it setup as C:\android-sdk-windows and then all of the files. When I type in the first command it says
Code:
The system cannot find the path specified.
And I have the Droid Explorer Installed and everything but it doesn't have the Emulator and that's all I really want. That and FastBoot.

nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd [B]C:\sdk\tools[/B]
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
If you noticed it extracted it to C:\sdk\tools, you did yours to C:\android-sdk-windows. So you'll need to adapt to the changes..
Code:
cd C:\android-sdk-windows\tools
adb shell

Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.

G1BRICKED said:
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
Click to expand...
Click to collapse
A friend of mine had the same problem. Make sure the device is plugged into the back of your computer, reboot the PC and the Phone. See if that helps. And which ROM are you running?

Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging

G1BRICKED said:
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
Click to expand...
Click to collapse
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.

nolimit78 said:
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
Click to expand...
Click to collapse
Well man, I tried it on FastTest and now I have a Custom Splash1 Image and now I'm not afraid of holding the Back button with the Red one. I think I'm going to throw Sense UI off to the side for now until it supports ADB and all. So thanks man, after all these monthes I finally have ADB Access. One more thing though, how can I get Emulator to work?

Now, when I try to go into Emulator through CMD, I se this;
Code:
C:\android-sdk-windows\tools>emulator
emulator: ERROR: You did not specify a virtual device name, and the system
directory could not be found.
If you are an Android SDK user, please use '@<name>' or '-avd <name>'
to start a given virtual device (see -help-avd for details).
Otherwise, follow the instructions in -help-disk-images to start the emulator
Then, I navigate to C:/Windows-SDK-Windows/SDK Setup and I allow it to run. I get two windows, one that says
Code:
Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: HTTPS SSL error. You might want to force download through HTTP in the settings.
I close that window and go to the one that says Choose Package To Install, but the white box on the side is blank. I close that and go to Android SDK And AVD Manager. From there I go to Virtual Devices and it's blank and grey-ed out. I click new and see
Code:
Name - [I]Here I can write[/I]
Target - [I]Here I can't write[/I]
SD Card: Size [I]Here I can write[/I] MiB or KiB
File: [I]Here I can't write[/I] Browse [COLOR="DarkRed"]Dulled out[/COLOR]
Screw skins and Hardware I can do that on my own, but how can I set a Target if it is grey-ed out?

G1BRICKED said:
how can I get Emulator to work?
Click to expand...
Click to collapse
that is something I can't help you with. I am at work and it won't allow me to download what I need for that. But I am glad you got ADB workin!

Lol thanks =D

[HOW-TO] Setting up ADB - The Tutorial For WINDOWS USERS...

SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps

adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..

Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?

cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.

how do i install an apk file right to my phone using the "cmd"

jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk

n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything

Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.

[Q] Help about sideloading apk files

Hi,
Nook Color CM7 RC1.
I am trying to sideload Google+ apk using adbwireless.
ADB seems to work OK in the PC, adbwireless is active, but I get device not found.
Is there a a tutorial or step-by-step explanation somewhere that explains how to use adb commands?
I come from DOS days, and know how to use command line, but I have very limited experience with Linux.
Thanks for answers

velizet said:
Hi,
Nook Color CM7 RC1.
I am trying to sideload Google+ apk using adbwireless.
ADB seems to work OK in the PC, adbwireless is active, but I get device not found.
Is there a a tutorial or step-by-step explanation somewhere that explains how to use adb commands?
I come from DOS days, and know how to use command line, but I have very limited experience with Linux.
Thanks for answers
Click to expand...
Click to collapse
Hi,
Solved the problem myself..

There is no man page, but running 'adb' by itself will print a description of the syntax.

By far the easiest way to do it is to download the apk to your Nook using your Nook's web browser, then navigate to the apk with Astro File Manager, select it and choose "install."

dsf3g said:
By far the easiest way to do it is to download the apk to your Nook using your Nook's web browser, then navigate to the apk with Astro File Manager, select it and choose "install."
Click to expand...
Click to collapse
To each his own. And you are titled to your opinion just as i am mine.
downloading an App on a computer storing it to your c:/<android_tools> folder then typing
Code:
adb install -s app_name.apk
is super easy.
most people are scared of ADB because it requires using the dreaded command prompt on your computer. And people are afraid of that.

neidlinger said:
To each his own. And you are titled to your opinion just as i am mine.
downloading an App on a computer storing it to your c:/<android_tools> folder then typing
Code:
adb install -s app_name.apk
is super easy.
most people are scared of ADB because it requires using the dreaded command prompt on your computer. And people are afraid of that.
Click to expand...
Click to collapse
why the -s switch?

velizet said:
why the -s switch?
Click to expand...
Click to collapse
adb install -s app_name.apk
Click to expand...
Click to collapse
will install the app onto the sdcard.
-l means forward-lock the app
-r means reinstall the app, keeping its data
-s means install on SD card instead of internal storage

neidlinger said:
To each his own. And you are titled to your opinion just as i am mine.
downloading an App on a computer storing it to your c:/<android_tools> folder then typing
Code:
adb install -s app_name.apk
is super easy.
most people are scared of ADB because it requires using the dreaded command prompt on your computer. And people are afraid of that.
Click to expand...
Click to collapse
No need to store the app in that folder. I keep my apks in a random one under my documents. When you want to install, just
Code:
adb install "drag the apk into command prompt"
and it will install just fine.

Nburnes said:
No need to store the app in that folder. I keep my apks in a random one under my documents. When you want to install, just
Code:
adb install "drag the apk into command prompt"
and it will install just fine.
Click to expand...
Click to collapse
Is it not possible to specify the folder of the apk file in the command line?
Something like:
adb install C:\<app_folder_path>\app_name.apk

[GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies

ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
[COLOR=Black]SETX PATH "%PATH%;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\platform-tools;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\android-sdk-windows\tools" -m[/COLOR]
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. However, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped​
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge

Reserved

Reserved Once More

Last One

Reserve the guide

install full rom
how to install a full rom from adb?

Pretty sure it's impossible. Sorry.
Sent from my E15i using XDA Premium App

Perfect Guide to use ADB Commands..
It is very clear and perfect guide to use ADB commands.. I tested this all and works fine..

You can use apks to do logcats from the phone too, I use catlog.

About Broadcom being open sourced made me laugh hahaha.

open source broadcomm, i see what you did there .

Updated OP

Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)

Android-fany said:
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Click to expand...
Click to collapse
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.

iamareebjamal said:
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
Click to expand...
Click to collapse
I already reinstalled it like 5 times. Still doesn't work.

Android-fany said:
I already reinstalled it like 5 times. Still doesn't work.
Click to expand...
Click to collapse
Which Windows?
Which ROM?

iamareebjamal said:
Which Windows?
Which ROM?
Click to expand...
Click to collapse
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)

Android-fany said:
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Click to expand...
Click to collapse
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8

AW: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
iamareebjamal said:
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
Click to expand...
Click to collapse
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i

Android-fany said:
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Click to expand...
Click to collapse
Very strange
Download My Phone Explorer and check if its working!!
Its just 2mb-6mb

Root with twrp - can't see my device in windows explorer

Hello guys,
im rooting my 3T with TWRP and following the steps described here:
http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
In step 8 i swiped right and wanted to copy the SU zip on my device (step 9). But i can't see it in windows explorer!
I installed drivers before and could see my device in windows explorer than it was on. But now im in the the TWRP menu and cannot copy the SU zip to device What can i do? Will i get bootloop, if i disconnect the device from pc?
Windows sees the adb usb device but it is not visible in explorer...
Please give me any help. Thanks

onionead said:
Hello guys,
im rooting my 3T with TWRP and following the steps described here:
http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
In step 8 i swiped right and wanted to copy the SU zip on my device (step 9). But i can't see it in windows explorer!
I installed drivers before and could see my device in windows explorer than it was on. But now im in the the TWRP menu and cannot copy the SU zip to device What can i do? Will i get bootloop, if i disconnect the device from pc?
Windows sees the adb usb device but it is not visible in explorer...
Please give me any help. Thanks
Click to expand...
Click to collapse
if you can see using this command "adb devices"
you can use adb push command to copy the zip

kenzolo said:
if you can see using this command "adb devices"
you can use adb push command to copy the zip
Click to expand...
Click to collapse
ok thank you for fast reply. but how i can identify my device? the command "push" requieres <local> and <remote> parameters.
Sry my bad... unfortunately i can't see my device with adb devices command

onionead said:
ok thank you for fast reply. but how i can identify my device? the command "push" requieres <local> and <remote> parameters.
Sry my bad... unfortunately i can't see my device with adb devices command
Click to expand...
Click to collapse
Ok can be closed. I had just to reinstall adb drivers.