Instructions for setting up Adb/Fastboot (windows)
1. On your phone go to Settings/Development and make sure USB debugging is ON and plug it in via the usb.. New phones go the settings about phone then click on the build number 10 times then back out to settings again and you will see developer options right above about phone. click on developer options then select usb debugging from there. also known as adb debugging.
2. Install drivers on your PC. Try pda.net for the drivers. Install the program by hitting “Run” and follow the instructions. You can remove it at a later time.
3. Download the file at the bottom of these instructions to your desktop and extract the contents. There is 1 folder and a install note (these instructions) that should extract. You can use a program called 7-ZIP to extract if needed (google it, its free and a great tool).
4. Open your “Start” menu and click on “My Computer”. Then choose “Local Disk C:”.(You can now click and drag the adb folder you extracted to the C: drive.
5.Open a command prompt and type cd\adb and hit enter. You should now see something that looks like this C:\adb>
6.Type adb devices then hit enter in the command prompt and it should list your device.
7. You can also type adb reboot bootloader which will put the device into bootloader mode. Now type fastboot devices then hit enter in the command prompt an it should list your device. (you must be in the bootloader for fastboot to recognize your device)
You should now be ready to send commands to your phone via ADB or Fastboot. You will need to repeat steps 5-6 anytime you want to use ADB/Fastboot. To send a file using Adb or fastboot make sure to put the file in your “adb” folder before giving the command to send it to your device.
ADB FASTBOOT WINDOWS ZIP
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you’ll find out what apps are doing in the background without you noticing.
TAKING AN LOGCAT
adb logcat > logcat.txt:
Here are some commands for Adb/Fastboot.
DO NOT USE ANY COMMANDS THAT YOU ARENT SURE OF OR DONT KNOW WHAT THEY DO. I AM NOT RESPONSABLE FOR ANYTHING THAT YOU DO TO YOUR PHONE.
ADB Commands Quote:
adb devices – list all connected devices adb push <local> <remote> – copy file/dir to device adb pull <remote> [<local>] – copy file/dir from device adb sync [ <directory> ] – copy host->device only if changed (-l means list but don’t copy) (see ‘adb help all’) adb shell – run remote shell interactively adb shell <command> – run remote shell command adb emu <command> – run emulator console command adb logcat [ <filter-spec> ] – View device log adb forward <local> <remote> – forward socket connections forward specs are one of: tcp:<port> localabstract:<unix domain socket name> localreserved:<unix domain socket name> localfilesystem:<unix domain socket name> dev:<character device name> jdwp:<process pid> (remote only) adb jdwp – list PIDs of processes hosting a JDWP transport adb install [-l] [-r] [-s] <file> – push this package file to the device and install it (‘-l’ means forward-lock the app) (‘-r’ means reinstall the app, keeping its data) (‘-s’ means install on SD card instead of internal storage) adb uninstall [-k] <package> – remove this app package from the device (‘-k’ means keep the data and cache directories) adb bugreport – return all information from the device that should be included in a bug report. adb help – show this help message adb version – show version num DATAOPTS: (no option) – don’t touch the data partition -w – wipe the data partition -d – flash the data partition scripting: adb wait-for-device – block until device is online adb start-server – ensure that there is a server running adb kill-server – kill the server if it is running adb get-state – prints: offline | bootloader | device adb get-serialno – prints: <serial-number> adb status-window – continuously print device status for a specified device adb remount – remounts the /system partition on the device read-write adb reboot [bootloader|recovery] – reboots the device, optionally into the bootloader or recovery program adb reboot-bootloader – reboots the device into the bootloader adb root – restarts the adbd daemon with root permissions adb usb – restarts the adbd daemon listening on USB adb tcpip <port> – restarts the adbd daemon listening on TCP on the specified port networking: adb ppp <tty> [parameters] – Run PPP over USB. Note: you should not automatically start a PPP connection. < tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] – Eg. defaultroute debug dump local notty usepeerdns adb sync notes: adb sync [ <directory> ] < localdir> can be interpreted in several ways: – If <directory> is not specified, both /system and /data partitions will be updated. – If it is “system” or “data”, only the corresponding partition is updated.environmental variables: ADB_TRACE – Print debug information. A comma separated list of the following values 1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp ANDROID_SERIAL – The serial number to connect to. -s takes priority over this if given. ANDROID_LOG_TAGS – When used with the logcat option, only these debug tags are printed |
Fastboot Commands Quote: Example (fastboot flash recovery TWRP-recovery.img) then hit enter this will flash a recovery image to the device.
usage: fastboot [ <option> ] <command> commands: update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition erase <partition> erase a flash partition getvar <variable> display a bootloader variable boot <kernel> [ <ramdisk> ] download and boot kernel flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it devices list all connected devices reboot reboot device normally reboot-bootloader reboot device into bootloader options: -w erase userdata and cache -s <serial number> specify device serial number -p <product> specify product name -c <cmdline> override kernel commandline -i <vendor id> specify a custom USB vendor id -b <base_addr> specify a custom kernel base address -n <page size> specify the nand page size. default: 2048 |
.
Not one bit of this seemed to work for me. I appreciate the effort, but I’ve been working on getting something working for 3-days now. I found your article and was impressed that I actually found downloadable software instead of someone’s advertisement and that is seems so clear. I have a Doogee S90C. I was able to get through adb commands prior to changing to the software you provided. Now I get nothing.
Hey RJ… Good stuff. are you still around?
Need help on Samsung Galaxy S9
frp.
bro how to install custom rom without twrp in micromax q306..mine is mt6580 chip..i have rooted it successfully.. but my device has no twrp
I’ve been trying to unlock bootloader on a Motorola Droid Z zxt1650 no luck any help would be appreciated.
dear rootjunky
i have lenovo vibe p1ma40 mmodel of 2015 running on android 5.1.
ita base band is P1ma40-A-V046-170106 and kernel version 3.10.65+
its build number is P1ma40-s040-170106-16G-ROW
i tried all method to unlock oem/bootloader to install twrp and miui 10 on it but unable to do so.
i read and followed methods on net available to root permanently but not succeed.
help me to upgrade android 5.1 to android pi wether using custom rom or method to install as ota unofficially.
Rootjunky……I need to bypass the frp lock on my samsung j3 luna pro! Help!
DITTO!
I also have a samsung j3 luna pro, which as of right now is nothing but a expensive battery holder!
Please RJ, find us a FRP bypass, so it can be a phone once again!…please?
I am sure i have a method that will work please check out phonlabteachable.com or rescuemyphone.net
you should update your article. The ‘pda.net’ plug is close to nonexistent, so invalid at this point. You also shouldn’t just leave readers with one site to use.. it would be nice if you actually took time to do more researching.
I am grateful you are here to help, however, I was trying to continue the article on adb and fastboot commands but it ended with the note, want to read the rest click a button below and share, upon doing that and sharing on google+ the article remained at the same location with nothing more.
thank you
I want to root my GT-N8000 Cynogen mode bought in China, which went off since and could not opened after watching your video on how:boot, recovery and system
now I need to
1. On my phone go to Settings/Development and make sure USB debugging is ON and plug it in via the usb.. New phones go the settings about phone then click on the build number 10 times then back out to settings again and you will see developer options right above about phone. click on developer options then select usb debugging from there.
the phone Samsung Tablet 10.1interface is on when you plug to the charger and you could use odin mode to access but cannot debug etc neither turn it on till it goes off by itself. what can I do in this instance?