Database Info

[Program]Bash simpleroot OTA 1.47.651.1 for Linux users - update01 rlsed

This is an adaption of Simpleroot for rooting OTA 1.47.651.1 in bash-script for linux users
In order to use this root you will need to have installed the android SDK on your linux machine, either via your distributions package management system or manually.
The user you are logged in with will need to have access to the adb tool that comes with the android sdk. Usually this means adding the user to the android group after installing the sdk, but specific methods of attaining access may differ by distribution.
- One method of setting up the sdk can be found Here
To begin using the bash simpleroot after installing the sdk and verifying access to adb, navigate to the directory where you extracted the simpleroot files in a terminal (read: console or command prompt if you prefer that terminology) and do an
"sh p1.sh"
to begin step 1 of the process,
then follow the instructions that you will be given as the script runs (it will tell you when to run the next script in the chain, etc).
SPECIAL THANKS to ItsMeCD for being a guinea pig on irc and successfully rooting his evo using bash simpleroot.
UPDATE 24-July-2010, 14:45 (2:30pm): Download replaced due to nasty evil bugs that crept into the original scripts and prevented them from running. if you downloaded before this time/date, please re-download
Simpleroot Bash Edition, by netarchy
Bugfix update: Update 01
- Fix some confusion in script execution feedback during p2.sh that may lead the user to believe the process has failed when it has not
- Clarified output during p4.sh to better reflect how long the user should wait before confirming the attempt to root has failed
Extract the update to the same place you extracted the original download, and overwrite files if prompted.
Simpleroot Bash edition Update-01

Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets

jmlott said:
Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets
Click to expand...
Click to collapse
Windows has no place on any computer of mine ;D
Be sure to lemme know if you run into any issues. Eventually I'll streamline it to need less interaction, maybe even make a gui for the cli-fearful.

Running it now...re-downloaded and extracting.

Posted a bugfix update to clean up script errors and clarify output.

Worked First Time
Didn't see any success stories yet, so I thought I'd post mine. Downloaded and ran the scripts and got root first time.
Now rockin Froyo courtesy of CyanoGenMod6. (Tried to leave a url to the ROM, but I'm too much of a noob on the forum

damnit ! - linux n00b - i gotta be close - errors on scripts... help ?
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.

xda98052 said:
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.
Click to expand...
Click to collapse
Putting the sdk tools binaries in the same dir with the scripts isn't going to make them magically find them (you're thinking windows style here), you need to put the android sdk tools in your PATH variable. The wiki referenced in the first post has an example of how to do this.
An example for you:
let's say you extracted the android sdk to /home/foo/androidsdk
and the tools are in /home/foo/androidsdk/tools (this is just for the sake of example mind you)
you would want to edit your .bashrc and add in
export PATH=$PATH:/home/foo/androidsdk/tools
You can then make that kick in by logging out and logging back in.

Just to Clarify...
Can I get root access without having to wipe my phone?

Having a problem
UPDATE: booted into clockwork and flashed Fresh ROM, ROM Manager works fine now. Thanks again for the awesome root method Netarchy, you are my hero!
Hey Netarchy, first want to say thank you for giving us Linux users some simpleroot love. Good job.
I ran all the scripts and everything seemed to go as you said it would. No error messages, all was well, I ran clockwork.sh and my phone booted in to clockwork just fine!
Code:
Pushing ClockWork Recovery
1534 KB/s (2752512 bytes in 1.751s)
Clockwork image pushed!
pushing flash_image
610 KB/s (26172 bytes in 0.041s)
flash_image pushed!
Changing permissions...
Permissions changed...
Moving recovery image...
Recovery moved...
Rebooting...
===============================================================
===============================================================
Recovery Flashed! please run sh cleanup.sh
===============================================================
===============================================================
Yay! So I installed ROM Manager on my phone and then my hopes are dashed. When I try to download roms it says I have to have ClockworkMod Recovery installed, so I tell it to install from ROM Manager, and I get this...
An error occurred while attempting to run privileged commands!
Click to expand...
Click to collapse
Any idea what I might have done wrong? Or should I just start the whole process over again? I noticed in my settings my software number was showing 1.17.651.1 now instead of 1.47.651.1 before I rooted.

netarchy said:
- One method of setting up the sdk can be found ...
Click to expand...
Click to collapse
Not allowed to post links (yet?)
Thanks for this but there's no info at that link just this...
AndroidSDKLinux
From Villain ROM
Jump to:navigation, search
There is currently no text in this page. You can search for this page title in other pages, or search the related logs.
Click to expand...
Click to collapse

Installing apk from sdcard in recovery console

I have no market on my phone and have been trying to install some apk's through amon ra console in recovery. Everything I try, which is practically everything i've read from searching, comes back with errors.
Either file/directory not found or can't open "install"
I am also having problems installing the drivers to get adb working from dangerspl. When I try to update drivers it says "This file does not contain information about your device"
Any help is much appreciated. I've been up all night trying to figure it out and feel like I'm going in circles.

Have you try installing from a file manager instead? (astro, estrongs, linda, etc..)

No I don't currently have a file browser installed, and have no market to look up/install one. I have another android phone with astro, could I pull it off of that phone and install on this with recovery console?

Why not just install it via adb or push it to /system/app

I can't connect via adb becuase I couldn't update the windows driver for dangerspl. I downloaded the drivers for dangerspl but when I tried to update, it said it didn't have information about my device. Something like that. So I can mount the sdcard in windows and put any files needed and boot into recovery and use that right? I tried making a zip with the qpks in it and use flash from zip, kinda like installing gapps, but that didnt work either. Any ideas?

Zip files will need the update scripts and signed for it to be able to be "flashed" from recovery.

Just use droidexplorer or android commander.

Code:
mount -a
or type less and read more

You can use busybox if you have the latest CM ROM installed
just type this ~~~> (busybox install /sdcard/yourapp.apk /sd-ext/app)
make sure the app is in the root of your sdcard

brios86 said:
You can use busybox if you have the latest CM ROM installed
just type this ~~~> (busybox install /sdcard/yourapp.apk /sd-ext/app)
make sure the app is in the root of your sdcard
Click to expand...
Click to collapse
Code:
su
cp /sdcard/yourapp.apk /sd-ext/app
is less typing
and
Code:
su
cp /sdcard/yourapp.apk /data/app
is a 'safer' bet as they didn't mention which rom

what about this one? update.zip creator
http://forum.xda-developers.com/showthread.php?t=717437

sleepyfu said:
Zip files will need the update scripts and signed for it to be able to be "flashed" from recovery.
Click to expand...
Click to collapse
which is not a big problem to create.
There is a TUT for it

sleepyfu said:
Have you try installing from a file manager instead? (astro, estrongs, linda, etc..)
Click to expand...
Click to collapse
you need a filemanager with root-rights. Depending on the ROM you use it might be available.
Try the app "IRSSI - connect bot". It gives you a console on the device.
login "local" and type "su".
Than you have superuser rights .... anything on commands you find in linux/android TUTs

Lol! 6 month old post?

[Linux/Mac] ADB & Fastboot (Un)Install Script [Team BlueRidge]

[Linux/Mac] ADB & Fastboot Install Script
I have created a script to be used to install ADB and Fastboot on a Mac or a Linux computer. Simply run the script in Terminal or a similar application and it will copy ADB and Fastboot to /usr/local/bin/
Also, as of Version 3.1 this also installs the JDK for Linux-based systems.
While advanced users probably won't need this, it would be good for new users who need help using the ADB and Fastboot commands.
You can see the source at GitHub.
Download
If you have any problems or errors, let me know.

Changelog:
20171202
Moved entirely to GitHub
On Debian-based Linux, installs the adb and fastboot packages
Other systems, the binaries are pulled from Google's website
Executables are given +x permissions
Version 5.0
Hosted on GitHub and Google Code
Uses latest adb and fastboot (as of April 3, 2014)
Install to /usr/local/bin/
Version 4.1
Uses cp rather than mv
Hosted on GitHub again
Team BlueRidge project
Version 4.0
Now installs adb and fastboot to /usr/bin/ which is a more appropriate directory for the files.
Includes Readme now!
Version 3.1
Added JDK Install for Linux
Version 3
Created separate scripts for Linux & Mac
Updated uninstall script
Version 2.1.1
Fixed errors in installer
Version 2.1
More code efficient.
Better comments in script.
Version 2
Combined installer scripts into one Universal
Updated Uninstall.sh to remove udev rules
Version 1.1
Added udev rules for Linux
Version 1
Initial release

Linux
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.

shootind5nukes said:
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.
Click to expand...
Click to collapse
Thanks! I'll fix that and post an update soon!

JDK is now installed on Linux systems!

Now hosted on Google Code rather than GitHub.

Now installs to /usr/bin/, which is a more appropriate directory as these files are not required for normal system booting or are required for the general functions of your operating system.

i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices

boneskid1 said:
i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices
Click to expand...
Click to collapse
Does it say that ADB is not found or your devices?
Try enabling ADB (USB Debugging) on your device if it says no devices were found.
Gingerbread: Settings>Applications>Development>USB Debugging
Ice Cream Sandwich: Settings>Developer options>Android debugging

Thanks!!!! This worked perfectly. Using Ubuntu 11.10.

romuloxiii said:
Thanks!!!! This worked perfectly. Using Ubuntu 11.10.
Click to expand...
Click to collapse
I'm happy I could help! Don't forget to click "Thanks" if you liked it!
If you have any issues in the future with it, please feel free to let me know!

Good news!!! This is now a Team BlueRidge project and is on Team BlueRidge's GitHub

since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious

prflash3 said:
since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious
Click to expand...
Click to collapse
Download whichever for whichever platform. It's the script inside that you use that matters.

Trying to run the script on OSX, but when I am prompted to enter my password I can't type anything. Please help.

Ditto ul49, being prompted for a password, please advise

Simply type your account password. It won't look like anything is being typed but it is. This is how the "sudo" command works. It is for security.

really glad i found this.
i run "sh "sh script name" and i get this error
ADB-Install-Linux.sh: 5: ADB-Install-Linux.sh: Syntax error: newline unexpected
not sure if it's installed or what
thanks for making this set of scripts and if u could advise me on that error id be grateful.
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
crazy
apt-get install android-tools-fastboot
and
apt-get install android-tools-adb
worked

Just released the first update in two years. Sorry to leave this project unmaintained. The files are now hosted by Team BlueRidge as Google Code no longer supports downloads.

First, thank you very much for putting this together for fellow users. While I'm not the most savy of guys I thought I might just share my experience while installing this ADB + Fastboot package on my MacBook Pro (mid 2012) running OS X Mavericks 10.9.3 in the hopes that somebody might benefit from it as well.
So here it goes:
I tried running the installation script found in "Androidv5.zip" which up until now is the latest version (I think). The script failed to install:
"This will install ADB and Fastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/User/Downloads/Androidv5
Moving ADB
cp: /usr/local/bin/adb: No such file or directory
ADB Moved to /usr/local/bin/adb
moving Fastboot
cp: /usr/local/bin/fastboot: No such file or directory
Fastboot moved to /usr/local/bin/fastboot
You may now run Android Debug Bridge and Fastboot commands
Have a nice day."
So I figured I'd open the script file and run each command manually but they would still not work. I then decided to open the target directory
from terminal and it couldn't find it either, so I openned the /usr/ directory to find where the /bin/ directory was... and I found it at | /usr/bin | instead of | /usr/local/bin |.
I ran the commands in the script again manually one by one with the target directory set to | /usr/bin | and then closed terminal and reopened. After that I tried running "adb devices" and the output was "permission denied".
I then applied a "chmod 775 /usr/bin/adb" "chmod 775 /usr/bin/fastboot", closed & reopened terminal and voilà it worked!
Again I'm not a savy guy... there might probably be a better way to do this or perhaps I didn't run the install script as it was supposed to but anyway I decided to let you guys know how it went just in case it proves useful to somebody else....
Then again thanks a lot for sharing this! I finally have ADB + Fastboot on my Mac without having to nag about downloading the Android SDK. :laugh: :good:

[LINUX]adbkp-gui ~ Control your phone with your PC!

adbkp-gui​
It is for linux, can be made for windows too, as it is open source :angel:​
Ever wondered, controlling your phone with your PC? Even possible? Yes!
but, "adb input x y" everytime???
Click to expand...
Click to collapse
No.
but, adb input x y doesn't work on ICS!
Click to expand...
Click to collapse
Yes, I know. That's when I got @Twin0ne's guide, TUTORIAL: Remote Control Touch Screen, but it was half-done So, I figured out the other half of the guide myself (which was easy to do, given the first half is pretty-self explanatory), and was able to get touch events on the phone, and soon, keypress events.
So, made a GUI with Qt, to make things easier
Changelog:
v2.2.5:
Reimplemented recalibrate() function to run automatically at startup
Easier to port, as platform-specific code is lessened
Needs single standalone executable, with adb in environment path
v2.0:
Diagonal touch added
re-worked touch functions
added re-calibrate function for multiple ROM support
v1.0:
Initial Release
Credits:
Twin0ne's guide (TUTORIAL: Remote Control Touch Screen)
https://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt
App preview:
How to use:
You need Qt 5.
Installation instructions for Qt:
Code:
sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
sudo apt-get update
sudo apt-get install qt-sdk
Then, install adb using "sudo apt-get install android-tools-adb" or similar
*or*
Reference adb path in your ~/.bashrc file!
Then, chmod ./adbkp-gui (if necessary) and execute normally.
Source: https://github.com/vineethraj49/adbkp-gui
XDA:DevDB Information
adbkp-gui, a Tool/Utility for the HTC Pico (Explorer)
Contributors
thewisenerd
Version Information
Status: Stable
Current Stable Version: v2.2.5
Stable Release Date: 2013-10-22
Created 2013-11-16
Last Updated 2013-11-16

Downloads
Downloads:
v2.2.5: https://github.com/vineethraj49/adbkp-gui/releases/download/v2.2.5/adbkp-gui
v2.0: View attachment adbkp-gui_v2.0.zip
Where's version 1.0?
Well, though sources were on GitHub, it was never intended to be released. v2.0, I thought it was good enough for public release
TODO:
Directly obtain event codes from phone (with help from: http://ktnr74.blogspot.in/2013/06/emulating-touchscreen-interaction-with.html)
You suggest!
There's BBQScreen! A much better alternative! More info: http://screen.bbqdroid.org/

reserved...
Reserved... just in case

@vineethraj49
how to run in ubuntu 12 cant understand how to do it
tried serching but got some error then

sakshamx said:
@vineethraj49
how to run in ubuntu 12 cant understand how to do it
tried serching but got some error then
Click to expand...
Click to collapse
You'd need to install the Qt5 and Qt4 from this PPA: https://launchpad.net/~ubuntu-sdk-team/+archive/ppa
Then, you'd be able to run it!
If you are looking for a faster method of controlling your phone, (and don't mind shelling out a few bucks), here's something useful: http://screen.bbqdroid.org/
Click to expand...
Click to collapse

vineethraj49 said:
You'd need to install the Qt5 and Qt4 from this PPA: https://launchpad.net/~ubuntu-sdk-team/+archive/ppa
Then, you'd be able to run it!
Click to expand...
Click to collapse
the app is running now some part in sdk was missing:silly:
but its not showing the screen and cant use any buttons on it

sakshamx said:
the app is running now some part in sdk was missing:silly:
but its not showing the screen and cant use any buttons on it
Click to expand...
Click to collapse
You need to connect your phone, and press the "re-calibrate" button

vineethraj49 said:
You need to connect your phone, and press the "re-calibrate" button
Click to expand...
Click to collapse
re caliberate not working just showing a blank screen
what extra data to be download for adb to work ?
sdk is required to download externally (full package) and add code in bashrc for adb to work?
i have already donloaded the stuff from the that code

sakshamx said:
re caliberate not working just showing a blank screen
what extra data to be download for adb to work ?
sdk is required to download externally (full package) and add code in bashrc for adb to work?
i have already donloaded the stuff from the that code
Click to expand...
Click to collapse
hmm...
you need to connect your phone, and your phone should be recognized with "adb devices"...then, open gui, and press recalibrate first... and you need to be able to see qt in your menu...
p.s. made a silly mistake of not including logging... will try to add logging support to the app as soon as possible

seems the 32-bit adb in the bin folder was causing the problem... next release with logging, and you'd have to install adb yourself using "apt-get install android-tools-adb", or set it in your path... no etas
p.s. recalibration done at app-execution time

ADB 1.0.32 for OTA update!!!

Hey folks!
I'm following this guide. From the command lines on Updating the platform-tools, I get an error "please consider trying to update again without a package filter"
Code:
android.bat update sdk -u -t platform-tools,tools
Downloaded the latest SDK and drivers. after writing down recovery.img, system.img and boot.img, I'm unable to update via sideloading.
Code:
adb sideload update.zip
The recovery screen turns out "You need adb 1.0.32 or newer to sideload to this device." I've checked out the SDK and confirmed the "Android SDK Tools (24.0.2)" and "Android SDK Platform-tools (21)" have been updated, which is possibly the ADB and fastboot etc.Now what more does it require to get ADB updated.
I've already updated the platform tools, sdk tools from the package manager. Regarding the PATH variable, Please shed some light though. I'm no experianced under LINUX or it's distro's nor have much knowledge in CMD terminal either. I've located the (cd) path to where the android.bat is installed for the 1st command line operation below.
Code:
android.bat update sdk -u -t platform-tools,tools
How come the 1st update platform-tools command went out wrong? All command line operations/downloading and writing down under the fastboot menu went out smoothly, except this sideloading.
Thanks.
:angel:

cloutz90 said:
to show the adb version use
Code:
adb version
it should be 1.0.32 or newer (see image attached)
Click to expand...
Click to collapse
I checked with the exact command line also, it's the same 1.0.31! Also the package manager shows out I'm at the latest platform and SDK tools.

Sigh of relief!
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:

CODENEX said:
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:
Click to expand...
Click to collapse
Having the same issue. How exactly did you "update the ADB version to the directory"

ADB issue
SantinoInc said:
Having the same issue. How exactly did you "update the ADB version to the directory"
Click to expand...
Click to collapse
about this ADB version issue, i have a different phone, but was facing almost same sort of problem.
I think he might have referred to this thread: http://forum.xda-developers.com/showthread.php?t=2317790;)