Related
I tried to install Zenonia 2 from mediafire but it blocks the installation and don't have the setting to allows it to install since ATT took it off. Is there a way to get this app into my phone?
-----------------
Check the sticky thread, "Installing 3rd party apps."
Sent from my HTC Liberty using XDA App
I tried doing that but I got stuck stuck doing on step 7 Becuz there was no adb command
I had the same problem and unfortunately I didn't document what steps I took to resolve it. I think you need to run the Android SDK and look for either the SDK manager or some sort of module add-on option. Then you need to add the SDK tools that include ADB. For some reason it's no longer included in the general SDK download.
How to Sideload 3rd Party Apps:
(Rooting NOT required for this)
Download SDK Tool HERE
1: Un-RAR Android folder to root directory on PC (ie: C:\ )
2: Open CMD Prompt and type CD\ and hit Enter
3: Now type cd\android\tools Enter
4: Plug in Data cable and choose "Charge Only" on phone (always choose this)
5: Now in CMD prompt enter this command: adb install barcodescanner3.4.apk and press Enter
The SDK tool should install the Barcode Scanner app on the phone. Yay!! Success!!
**You can use this method to install .apk downloads onto the phone. For this demo i had already inserted
the Barcode Scanner app into SDK tools folder. the actual command should read as follows:
adb install c:\path to .apk file (ie: adb install c:\apps\filename.apk)
**I chose this app because you can use it to install other apps by scanning the barcode
found on many HTC App sites.
No need to go through all this trouble anymore. All you need to do is download "sideload wonder machine" from android central and whatever app you want to install. Its quick and painless and it allows you to sideload apps to your unrooted aria (or any android)
The only thing you must do to the phone is make sure you have usb debugging enabled under the development settings.
Sent from my cm6.1 Aria using XDA App
unteagle said:
How to Sideload 3rd Party Apps:
(Rooting NOT required for this)
Download SDK Tool HERE
1: Un-RAR Android folder to root directory on PC (ie: C:\ )
2: Open CMD Prompt and type CD\ and hit Enter
3: Now type cd\android\tools Enter
4: Plug in Data cable and choose "Charge Only" on phone (always choose this)
5: Now in CMD prompt enter this command: adb install barcodescanner3.4.apk and press Enter
The SDK tool should install the Barcode Scanner app on the phone. Yay!! Success!!
**You can use this method to install .apk downloads onto the phone. For this demo i had already inserted
the Barcode Scanner app into SDK tools folder. the actual command should read as follows:
adb install c:\path to .apk file (ie: adb install c:\apps\filename.apk)
**I chose this app because you can use it to install other apps by scanning the barcode
found on many HTC App sites.
Click to expand...
Click to collapse
If you see my post right above yours, you will see that this method doesn't work anymore since adb is not included in the SDK by default. You (or whoever wrote the original instructions) need to add the steps necessary to install adb in the SDK.
How u install the adb command?
Thank you CallMeAria. It works now!
GuardianC6 said:
How u install the adb command?
Click to expand...
Click to collapse
Guessing you don't need the instructions anymore since you got it working with the wonder machine, but just in case, you need to run the Android SDK Manager, choose whichever available package comes with ADB, I think it is Android SDK Tools Revision 8, then download and install that.
awesome
thanks it worked great
Download Android Central Sideload Wonder Machine.
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
The last SDK Platform-Tools for Win, Linux and Mac you can always find here - https://developer.android.com/studio/releases/platform-tools
Arhive:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
sorry for being a noob and asking for another device in a different forum,
but will these adb drivers also work with nexus 4???
need them to sideload 5.0.1
IS this for android 5.0 GPE?
http://forum.xda-developers.com/htc-one/general/guide-windows-8-1-fastboot-adb-t2970692
i have anaged to get it working after expereincing the problems stated here by others ... follow my steps here for those who still have trouble
lewonsky said:
IS this for android 5.0 GPE?
Click to expand...
Click to collapse
Yes, this for all version. It' latest update from official Android SDK Platforms.
See link in OP.
Golv said:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
Click to expand...
Click to collapse
I think you forgot to mention that this is only for Windows. So it does not work for Linux or Mac.
Quick, fast, no frills, just the necessary files itself. Hopefully this thread gets updated whenever a new release comes up
thanks, nice share bro :good:
how to use those files
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
open a command window and change directory to the folder where adb.exe is installed. Then you can use adb commands. Commands syntax is as follow:
Code:
adb [target] <command>
You only need to specify the [target] if you have more than 1 android device or emulator connected simultaneously, otherwise the command will be directed to the only connected device, so the syntax will be:
Code:
adb <command>
So if you want to sideload a rom to your device, boot in your custom recovery and start the "sideload" mode.
In the command window:
Code:
adb sideload my_rom.zip
Don't forget that the rom.zip must be in the same folder where adb.exe is
If you want to use "adb push" instead of "adb sideload" then boot in custom recovery (not in sideload mode) and use the following command:
Code:
adb push my_rom.zip /sdcard
You can read more about adb commands here: http://developer.android.com/tools/help/adb.html#issuingcommands
adb sideload explained here: http://android-revolution-hd.blogspot.in/2013/12/ow-to-use-adb-sideload.html
If you have more question about what file to sideload or push a rom to your device, you should ask in the correct forum, Amazon Fire HD 6 forum is here: http://forum.xda-developers.com/fire-hd
thank u
save my day
How do you install the new adb 1.0.32 over the old version and will it work with the moto X 2014?
its dosnt work for me
and i need it ((
every phone i want use sideload , its say me , use adb 1.0.32 or newer
and when i want use adb 1.0.32 , show me this error in all adb commands :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
what should i do ?
update adb
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
go to this website: https://fl1.androidfilehost.com/dl/...803384/minimal_adb_fastboot_v1.3.1_setup.exe?
download and install it to your computer, then try to sideload it through there.
if that doesn't work just download the stand alone SDK from the android studio website and after its downloaded, open the .rar file and extract it to a new folder to your desktop. after that open it and search for a folder that says platform tools and look for the ADB .exe file and copy it, then go to your C drive and go to programs and try to find the android studio folder, when you have located it open it and look for a folder named platform tools, then delete the adb.exe in that folder and paste the new one in there or you can probably just copy the whole platform tools folder and replace the other one in the C drive.
I hope this helps, if it doesnt just message me and im sorry for the late reply.
alishadlou said:
* failed to start daemon *
error: unknown host service
what should i do ?
Click to expand...
Click to collapse
this usually means the phone is not communicating with your PC.
- either your phone is corrupt
- the connection is corrupt
- or the cable is bad
Tip: add the path of ADB.exe to your system Environment Variables, so you can call it w/out first navigating to it.
- Right click Computer > Properties > Advanced system settings
- Environment Variables ... > edit "Path" by adding the path to ADB.exe.
ie.
Windows 10 x64, i simply add: D:\PortableApps\ADB
for other Windows, you may have to add to the end of "Path", click edit > scroll to the end > add ;D:\PortableApps\ADB;
(don't forget to add the semicolon at the end)
Now you can simply launch Command Prompt and enter: ADB sideload *file*
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
Not working on Android 6.0
This and older versions will not work on Samsung S7E for system backup and restore.
It accepts the commands, but the confirmation popup supposed to open on the device never does. For a few 6.0 users on other devices, it opened up but the backups were not really completed.
thanks bro. nice share :good:
Thanks, you save me too much time!!
my adb was working fine for my Note 4. I followed the instructions to upgrade bootloader
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Now, I keep getting device offline when used adb devices command. Do you think, upgrading ADB will solve this? thank you
Please note, I can only speak with any degree of certainty about devices bought from Play / Moto. I cannot attest to the accuracy of this information for US carrier versions etc. Anything you do is at your own risk
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Download links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide .. This is asking to install for all windows users. < 15 second installer needs updating to SDK 23, which is required for latest Android versions.
Download the latest SDK (adb and fastboot) versions here: https://developer.android.com/sdk/index.html (Scroll down to SDK tools only) then download the Windows *Installer*.
Open the installer and select "Platform-tools" and install the packages. This should create "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Now we want to set this path as a Windows Environment variable PATH to make the executables work system wide:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Please note, the semi-colon ; is VERY important.
You may also need to install drivers.
Here is a link to the Google USB Driver: DOWNLOAD THIS
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 6 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb, find teh folder you extracted then follow the wizard to the end - using amd6 64 if you're on a 64 bit system and i386 if you're on a 32 bit system.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you may need to additionally disable driver enforcement
- 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.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working.
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. Rooting the N6 is essentially unlocking the bootloader, flashing a recovery and then putting the SuperSU zip on your sdcard and flashing it via the recovery. This thread covers rooting: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide by @xBeerdroiDx
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and boot image (kernel) as you would if you were returning to stock.
A full guide to returning to stock can be found here: [TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader by @Mr hOaX
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer
thanks(im out of thanks). but ill be back to leave one here!!!!!
simms22 said:
thanks(im out of thanks). but ill be back to leave one here!!!!!
Click to expand...
Click to collapse
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
rootSU said:
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
Click to expand...
Click to collapse
it was up in the n5 threads before, and was needed here. but its here now as well, so thank you
Good guide. Needs to be a sticky. In fact, I think every device general forum should have a sticky like this. Would have saved me a lot of grief back when....
Excellent update.
Very good to see. I'm sure lots of people will be sending noobs here for the basics.
Up to your usual helpful, good work I see.
rootSU said:
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
Click to expand...
Click to collapse
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
rootSU said:
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the google USB drivers
Here is a link to the Google USB Driver: DOWNLOAD THIS
Click to expand...
Click to collapse
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Snoop05 said:
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Click to expand...
Click to collapse
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
rootSU said:
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
Click to expand...
Click to collapse
Path is added in both cases.
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Can you be very specific with your issue please?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Android M no like root, you'll either have to live with stock or wait for chainfire to do his thing.
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
ScottyChaos said:
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
Click to expand...
Click to collapse
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
cam30era said:
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
ScottyChaos said:
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
Click to expand...
Click to collapse
Error 28 means drivers not installed. Try the driver help thread that I linked above.
---------- Post added at 12:33 PM ---------- Previous post was at 12:04 PM ----------
cam30era said:
Error 28 means drivers not installed. Try the driver help thread that I linked above.
Click to expand...
Click to collapse
@ScottyChaos,
Just a fundamental question: I assume you have enabled "Developer Options" in Settings, and then checked "enable USB debugging"?
---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------
[/COLOR @ScottyChaos,
Here is a thread that you might find interesting > http://forum.xda-developers.com/android/help/metro-pcs-kyocera-hydro-life-rooted-t2870678
Windows 10 device driver management is even more locked down then windows 8. I got two of the three drivers loaded but when going into adb mode on the phone through recovery it just disappeared out of the device manager. I had to unplug and plug in while in that mode to trigger a unloaded driver in the device manager. Once there I had to force the adb driver manually with the nasty windows driver warning and all. Once I did that I could see the device in adb mode and sideload my marshmallow OTA. woot!
I decided to drop a thanks bomb...
ADB is good.
But that fastboot.
Seriously, its ONE command. OK, a few different arguments to use.... But it is so easy, and so powerful. People are afraid to mess up on command line, but its actually way harder to type the wrong thing out then to click the wrong thing.
LEARN IT. Forget your toolkit.
You can fix almost anything, Its not too hard for you. It may be new... YOU CAN DO IT.
Also, I have to say it... Its not going to help anyone, but it will keep me from punching something. ADB and Fastboot... Not the same. You don't ADB a new system image....
Hi,
I have been able to 'master' HTC Desire, Xperia T, Xperia Z3C and even LG Optimus Black.
Except from HTC Desire (if you ever want to learn about ADB and Fastboot, use HTC Desire, the best) it is always a bit tricky to get into Fastboot mode.
I have found the easyest way to access Fastboot mode in this howto: https://goo.gl/hzyB2H
Simply stated:
- Enable USB debugging in Developer Options
- Install Minimal ADB and Fastboot from here: https://goo.gl/d5BSc7 or use the solid option using FWUL (see below)
- Open command window in Minimal ADB and Fastboot directory (Window Flag + right-click on the folder)
- Plugin your device (which is on)
- Type: adb devices and your device answers with its serial number.
- First answer is serial number and 'unauthorized'
- On your device you will see a popup like shown below
- Type: adb devices and your device answers with its serial number and device
- You're there
If you just need adb you can stop here, if you want to go on to fastboot, continue.
- Type: adb reboot-bootloader
- Type: fastboot devices
And you're there.
No more hassling around with Vol-Down and plugging in.
- Type: fastboot reboot to end the session nicely
Uninstall (system) apps using adb
Uninstall Sony Xperia 'What's New'
adb uninstall --user 0 com.sonymobile.entrance
Let's uninstall Facebook
- type: adb shell pm list packages | grep 'acebo' (I don't know if it spells with F or f) (see REMARK)
- You will receive an answer like:
com.facebook.katana
com.facebook.system
com.facebook.appmanager
- type: adb uninstall --user 0 com.facebook.katana etc.
- do the same for the other lines
- Done for the moment
- Check on your device. Goto settings->apps->Facebook and you will see 'uninstalled' behind it
- Reboot your device ( do it the adb way and issue the command <adb shell reboot>
- After the reboot you won't find Facebook anymore in the apps list
REMARK sometimes it is hard to find the name of the app you want to uninstall.
F.i. the app Playstation bears the name com.scee.psxandroid.
You can retrieve the name using the Play Store app Application Inspector
I had quite a lot of trouble with adb and Windows 10, the solution lies in using Linux.
Recently XDA senior member steadfasterX released “Forget Windows Use Linux” (FWUL) – a bootable GNU/Linux ISO geared specifically towards Windows users who need to communicate more reliably with Android. https://goo.gl/PxvS9p
If you want to play with adb then this is your chance.
Create a live CD or a bootable USB stick with FWUL and everything works like a charm. Forget Windows!
Remember:
Don't blame me if anything goes wrong.
Following these instructions is at your own risk.
And if.... then normally Xperia Companion is your friend.
Enjoy!
Picture shows an example
- how to find the location of an apk
- how to pull the apk to your computer
- how to uninstall the apk
- and the failure that shows that the apk is gone
You can use adb to record your phone screen
- adb shell screenrecord /sdcard/screenrecord.mp4
Stop with Ctrl-C
You can use adb to make a screenshot
- adb shell screencap -p /sdcard/screendump.png (-p stands for: create png file)
- adb pull /sdcard/screendump
alternative
- adb shell screencap -p > screendump.png (which sends the file to your computer)
ADB can be used to backup yout device (apk's and data)
- adb backup -f c:/backups/phonebackup.ab -all
- on the device you have to give permission
Of course you can restore the backup
- adb restore <filename>, but for restoring you need to have root access.
There are a lot of options, all explained elsewhere on XDA: https://goo.gl/KtVd1n
W10 is a bit tricky when it comes to running adb on your Xperia device.
To install the necessary drivers, follow this instruction:
To install the official Sony Xperia drivers you need to download them from here.
- Unpack the Zip file
- goto the directory
- right click on sarndis.if and click on install
To install the Flashtool drivers for Windows 8/8.1/10, please follow the steps below.
A) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine.
This text is copied from Xperia blog
PS
Just adding another uninstall.
Using PiHole to block ads, people have noticed that on Android adds are not blocked.
More specific: Ads in Chrome on Android are not blocked.
Reason: Chrome denies your DNS settings
Solution:
adb uninstall --user 0 com.android.partnerbrowsercustomizations.chromeHomepage
From now on ads in Chrome on Android will be blocked as well.
Hi,
I am a real noob here, I have adb and fastboot. I would like to unlock my Z3 tablet compact bootloader. I have the code, it shows when I use the command adb devices but when I try fastboot devices I get not response. I'm not really sure what the issue is, can you help?
Did you try using Flashtool to unlock it? Never done it myself, but it seems pretty simple, and no command line required.
https://xperiafirmware.com/unlock-bootloader-sony-xperia/
sony xperia z3 no os installed android 6 bootloader cant be unlocked
hey guys my z3 has been soft bricked coz i flashed a system img that i extracted from its firmware i have tried to flash it using flashtool but it gives me this device connected with usb debbuging off 2011 make sure mtp is disabled
Use Flashtool to flash a stock .ftf file.
Note: I'm new to XDA, so I've basically made no posts so far. I tried posting this under HTC Bolt/Evo 10, but since I have not made the 10 post threshold yet, I cannot post there, so I just made the post here. If this post needs to be relocated please let me know.
After rooting my phone (HTC Bolt), I foolishly deleted some bloatware applications without backing them up. One of them was TouchPal, a preinstalled keyboard app. I didn't think this would be much of a problem because I already had it disabled in settings and was using a separate keyboard app for other purposes.
However, when I restart my phone, it always asks me to type my pin and "decrypt" the phone. I'm not sure why it does this (previous cell phone didn't), but apparently (this is only a theory) it uses this keyboard application, so I can't actually type my PIN in to decrypt my phone.
I could be completely wrong, and I might have accidentally deleted some other important file from my phone, but either way, I don't know how to fix my phone right now.
I did a bit of research and found out I was supposed to flash a ROM onto my device. However, I don't think I can even connect my device to my computer because normally I would have to enable USB debugging and file transfers.
So basically: is there a way to connect my phone to my computer that would allow me to do whatever is necessary to let me access my phone again? (also should I be flashing a completely new ROM? I should still have everything on my phone except a couple bloatware applications, so is there an easier workaround?)
Update: I got my phone to connect to my PC by booting it in recovery mode. I'll delete this thread if I can successfully flash a ROM.
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Ksawerion said:
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Click to expand...
Click to collapse
Thanks for the reply. How would I install the apk onto my device?
ztcfrank123 said:
Thanks for the reply. How would I install the apk onto my device?
Click to expand...
Click to collapse
I remember an easier way.
Maybe you can install app via ADB in recovery mode.
Therefore you need:
custom recovery
ADB tools installed on your PC
USB Driver installed
The APK downloaded from here: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=TouchPal
If you have done this - reboot to recovery.
Navigate on your PC to the adb tools folder where adb.exe is in it. Open CMD with right click on address line.
Then write in CMD:
adb devices
If your phone is found, adb commands are working.
Then copy the APK in the folder where adb.exe is in it.
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
So maybe this works
So first check:
- custom recovery flashed?
- adb tools installed?
- USB driver installed?
If you have further questions, let me know.
KSA
Ksawerion said:
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
Click to expand...
Click to collapse
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
ztcfrank123 said:
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
Click to expand...
Click to collapse
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Ksawerion said:
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Click to expand...
Click to collapse
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
ztcfrank123 said:
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
Click to expand...
Click to collapse
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Ksawerion said:
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Click to expand...
Click to collapse
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
ztcfrank123 said:
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
Click to expand...
Click to collapse
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Ksawerion said:
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Click to expand...
Click to collapse
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
ztcfrank123 said:
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
Click to expand...
Click to collapse
Was pushing successful? What says CMD after 'adb push'?