Operating System in use:
Debian GNU/Linux 9.4 (stretch)
Linux 4.9.0-6-amd64
Telephone model to be used: ZTE Z5s mini NX406E
Processor: Qualcomm Snapdragon 400/410 1,21 GHz
Android 4.4.4 KitKat
I try to make a backup using the adb, using the command:
adb backup all or adb backup -all
example:
[email protected]:/home/life/adb# adb backup -all
Now unlock your device and confirm the backup operation...
I go to the phone screen, I enter the password and the copy continues, Hard pains about 3 seconds this, I only create a file of barely weighs about 549 bytes, when I review the adb versions, performing the following steps:
[email protected]:/home/life/adb# adb version
Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-1
[email protected]:/home/life/adb# adb shell
[email protected]:/ $ adb version
Android Debug Bridge version 1.0.31
[email protected]:/ $ exit
Question # 1: They are different versions, for that reason I can not make the backup?
Question # 2: I need to have in Debian the same version that has the phone to make the backup, is it the only way if I want to use the adb?
Question # 3: How can I locate and install version 1.0.31 of the adb in my debian?
Question # 4: Can I have different installed versions of the adb at the same time in my debian without having any kind of problems?
Note: I am learning to disarm ROM, to study them and start creating new ones.
Thanks in advance for any assistance.
sorry my bad english, I use google translate
Question.
I forced myself to use Windows 7 to be able to have part of the answers I'm looking for, even though using Windows 7 I was able to make the copies, having the same version of the mobile in Windows 7, I am interested in knowing in what way using Debian I can do it. I know at least that if the versions are different there are limitations. But Windows is easy to have a folder with each version of adb, however in Linux is not so easy, at least for those who do not have much experience in this field.
Thanks in advance for any assistance.
sorry my bad english, I use google translate
Related
If you want to install Debian, just follow this step:
1. Download this : megaupload.com/?d=EV1SOKWJ
In the debian folder you should change the installer.sh and bootdeb files by this one
Download them:
installer.sh : mediafire.com/file/6j99zi0g1lu4oxq/ashu11x_installer.rar
Bootdeb : mediafire.com/file/osshm94mo1qhd65/ashu11x_bootdeb.rar
2. After that, copy the debian folder unzipped to the root of your sd-card
3. Than open Terminal and type:
Code:
su
cd /sdcard/debian
sh installer.sh
bootdeb
cd /scripts/onetime.sh
sh onetime.sh
That's it!
Credits:
ashu11x
An other way to install it
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
Download Linux Installer here:
uk.androlib.com/android.application.com-galoula-linuxinstall-tFjz.aspx
Install it
Press "Menu" button and choose "Setup".
The configuration apper, the defaults settings work without touch anithing : Debian Leny into a 500M loop file named "Linux.loop" in th sdcard. for lunch this Linux, the script name is "linuxboot".
Detailled functions :
- Install into LOOP file
Check to box if you want use an loop file, a loop file, is a virtual disk, same as image of hard drive. The loop file can be in any directory. I recomand to put this loop file into sdcard with an extension ".loop".
- Server
Name or IP of download server. If this option is empty, the default server is used. To install ubuntu, leave emtpy.
- Distribution type
Type of distibutions, actualy, Debian or Ubuntu.
- Distribution version
Version in type distribution. Warning ! Please check your version with a real type ! Debian can be Lenny or Squeeze, but no Dapper or Jaunty ! This two end, is Ubuntu version !
- Script to lunch Linux
The command to lunch Linux. you can choose own command to lunch. It permit to install Lenny into file Lenny.loop with script name bootLenny and install. after that install debian squeez or Ubuntu Jaunty into a partition of your SD card, and use an JauntyBoot to lunch jaunty. You have two Linux distributions on the same phone !
- Install into (loop)
Enter full path for the filename used as loop. I recommend to /sdcard/myfile.loop
- File size
The size of file allowed for loop. The size is alocated directly, no possible to change or have an dynamic size !
Click to expand...
Click to collapse
The full site with pictures
android.galoula.com/en/LinuxInstall/
where is the /scripts/onetime.sh
http://forum.xda-developers.com/showthread.php?t=1129803
http://forum.xda-developers.com/showthread.php?t=996746
http://forum.xda-developers.com/showthread.php?t=954807
ccownu said:
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
The full site with pictures
android.galoula.com/en/LinuxInstall/
Click to expand...
Click to collapse
on My P500 that one sucks, it worked on 2 gb not on 8 gb, but as told its an rc
Or just do this: ← How to Build CHROOT ARM Ubuntu Images for Android! (UBUNTU ONLY) SHALL WORK ON DEBIAN I THINK!
How to Install Busybox on your Android! →
How to Install Ubuntu on Android!
Posted on February 1, 2011 by admin
For those of you who want to install Ubuntu on your Android smartphone or tablet device, here’s our universal guide on how to do it. (This guide is based off my original guide at NexusOneHacks.net)
*Note – This guide should work on most “rooted” Android smartphones/tablets with no further modification.
We will be running Ubuntu “chrooted” under Android OS, which just means that we will be running a “virtual” Ubuntu OS that runs on top of the Android OS. Your Android OS will work fully (e.g. your phone will keep working normally) while the Ubuntu runs on top of it.
First of all, you should have your Android device “rooted” because you need root access to run Ubuntu off your Android.
Second, your Android OS must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it.
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
How do you know this? Just try installing Ubuntu and if it doesn’t boot, your Android device needs a kernel with loop device support. Otherwise you are fine.
How to Install Ubuntu on Android! (Windows)
First, download the following Ubuntu.zip file (from a preferred mirror), unzip and copy over the whole ubuntu directory to the SD card of your Android smartphone/tablet device:
Download ubuntu.zip http://downloadandroidroms.com/files/get/Nhi9EJWSw7/ubuntu.zip
(Turn USB storage ON then copy over the Ubuntu folder to the root directory of your SD card.)
(What it looks like after copied over to the SD Card)
1) Again, make sure you have your Android smartphone/tablet “rooted”!
2) You must have Android SDK installed or have access to adb.exe.
3) Make sure your Android phone/tablet is in debugging mode. Go to Settings->Applications->Development and make sure USB Debugging is checked ON.
4) Connect your Android device to your computer via USB cable and set the USB mode to “Just Charge”.
5) Your Android device should be recognized as “ADB Device” under Device Manager. If not, install appropriate drivers.
For all HTC Android smartphones/tablets (such as G2 Phone, Nexus One), you can download Windows drivers here:
HTC Windows 64-bit driver download – Click Here to Download Driver
HTC Windows 32-bit driver download – Click Here to Download Driver
6) Open up a command prompt by typing “cmd” under Start->Search programs and files.
7) Browse to your SDK directory where you installed the Android SDK:
8) Then go into platform-tools directory:
9) Type “adb devices” to double-check your Android device is recognized.
In this example, I used an HTC G2 Phone, which shows up at “HT09SR204261″. This is fine. However, if you get an empty device, that means you didn’t install the drivers for your phone/tablet correctly. (Go back to #5)
10) Type “adb shell” to enter the Android shell.
Then type “su” to enter super user mode, then type “cd /sdcard” and “cd ubuntu” to enter the ubuntu directory in your SD card of your Android device.
11) Next, type “sh ubuntu.sh” to run the script which will basically get your Ubuntu image ready to run on your Android smartphone/tablet.
If you get error messages, don’t worry and keep going.
12) Type “bootubuntu” to enter Ubuntu. (Next time you enter Ubuntu, you just need to type “bootubuntu” from your /sdcard/ubuntu directory, no need to run ubuntu.sh again.
If you got “[email protected]” at this point, congratulations! This means your Android OS comes with loop device support and Ubuntu is now running “chrooted” on top of your Android OS!!!
However, if you failed at this point, your Android OS probably doesn’t support loop devices, try installing another ROM or compiling your own kernel with loop device support.
How to Install Programs on your Ubuntu!
Once you’ve got Ubuntu running on your Android device, it’s time to install some Ubuntu packages(or programs).
Type “apt-get update” to update, this is the first thing you will need to do before installing any new programs.
How to Install OpenSSH-server on your Android Ubuntu!
Type “apt-get install openssh-server” to install OpenSSH-server. What is OpenSSH-server? If you want to connect to your Android Ubuntu via an IP address (and SSH into it), you will want to do this.
How to Install TightVNCServer on your Android Ubuntu!
If you want to access the GUI of your Android Ubuntu, you can install TightVNCServer, which allows you to access the Android Ubuntu via Android VNC app on your Android smartphone/tablet or even access it remotely from your desktop computer.
Type “apt-get install tightvncserver” to install.
How to Fix Language Issues
Above is after I connected to my Android Ubuntu via SSH2. Well, for some reason my default language switched to German. To fix that, just type “export LANG=en_US.UTF-8″:
How to Install LXDE!(optional)
Next, we will install LXDE (Lightweight X11 Desktop Environment). Although we can use Ubuntu’s default GNOME (and trust me I love that), LXDE takes up less memory so our GUI access will be faster.
If you like GNOME, you can skip this step though.
Type “apt-get install lxde”
Next, let’s setup xstartup file so that when TightVNCServer is started, the LXDE runs instead of GNOME:
Type “cat > /root/.vnc/xstartup”
Then type:
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then hit Ctrl+D twice and enter to save the file.
How to Start TightVNCServer!
Next, let’s start the TightVNCServer and connect to it from our Android phone and my Windows 7 desktop:
Type “export USER=root” and “vncserver -geometry 1024×800″.
Here, you can change the resolution settings 1024×800 to the resolution of your liking.
Now your TightVNCServer is ready to accept any incoming connections from your phone or computer. Just point to the correct IP address and use port number 5901 to connect.
On your Android smartphone, just download the free app “Android-VNC-Viewer” and set the IP address to “127.0.0.1″ and port number 5901 to connect.
And you should be able to get into your Ubuntu like this:
You can also use desktop software like TightVNC Viewer and connect to your phone.
Do “ifconfig” to find out what your IP address is in your Android Ubuntu.
In this example, mine was connected to “192.168.1.131″.
Then connect to “192.168.1.131:5901″ on your TightVNC Viewer:
Here’s LXDE running on my desktop off my G2 Phone’s Ubuntu:
Troubleshooting
Ubuntu not running?
Try typing “cp” under Android shell and if you get an error message, it means you need to install Busybox. Install Busybox and try again.
Final Thoughts
As said in the video, there will be a lot of improvements in the speed of Android devices in the near future. This year, there will be a slew of dual-core 1Ghz processor-equipped Android devices being introduced. Which just means our Android Ubuntu will run faster and faster.
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this:
Code:
:~$ adb devices
List of devices attached
S58300c017faf device
:~$ adb shell
sh: applet not found
Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking.
If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal.
I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try
I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM).
Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut
Thanx for all your help guys.
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needing a PC).
So..... Would it be possible?
This would fare better in the Android Q&A forum. I'll flag it to the forum mod and ask them to move it
Done, and Thank You Sir.
adb
pokepal101 said:
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needinig a PC).
So..... Would it be possible?
Click to expand...
Click to collapse
I want to start by saying I'm no expert, but to the best of my knowledge, this is how it works.
adb runs native on android, the android property is ro.secure=1 this is found in the default.prop file. ADB is run in user privilege mode with this property setting. Not all of the adb shell commands will work with the device in this mode. With ro.secure=0 property setting, adb will run with root user privileges and all adb shell commands will function. There is an adb comand that when issued will return the value of the setting, but off the top of my head I could not tell you it. The file default.prop is part of the boot.img and will load every time the device is booted, so to edit the file the boot.img would have to be unpacked, edited, repacked, and pushed to the device boot partition.
I don't know why you would want to connect two smartphones using adb and don't know if it is even possible. It is probably best to run the binary with a script on the device where you want it installed. Good Luck with your project.
Sorry, I don't think I quite understand....
fdaconta said:
Not all of the adb shell commands will work with the device in this mode
Click to expand...
Click to collapse
I'm sorry if I'm not making myself clear, but I'm talking about running the ADB client/server on an android phone (normally done on a development computer), not the ADB daemon.
fdaconta said:
It is probably best to run the binary with a script on the device where you want it installed
Click to expand...
Click to collapse
That's also not possible, as the script involves running some complicated ADB-ish things like "adb restore" and running while device #2 is turned off - hence the need for device #1.
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.
Hi,
Hope this is the right forum.
I just upgraded from Windows 7 to 10. Now Helium for Windows can't activate the backup on my android phones any more (Moto X and Samsung Galaxy).
Any settings that I need to change?
Thanks
--- update
I installed the driver from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and now it's working.
Use the chrome version
I have tested on windows 10 build 11082 and worked.
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
xplorr said:
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
Easy enough fix. Wonder if the Helium creators will update.
This worked perfectly! Thanks so much!
this worked perfect for me!
The coder really should make his windows application just point to the default ADB installation folder. Or better yet, he should have a prompt/wizard which will lead the user to the default directory but also give them the opportunity to point to a non-default location. Since ADB is a pre-requisit for this program, users just need to be told "go to the android website and download platform-tools or the android studio." I prefer the studio because it comes with the GUI sdkmanager and that's nice because I dont have to go anywhere to find out if there has been an update to platform-tools, it tells me right away and will download/install it for me. And that's good for me cause I can be pretty lazy sometimes.
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
i Don't believe such a simple trick works ..... thank you very much ...