{
"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"
}
Nexus Tools is an installer for the Android debug/development command-line tools ADB (Android Device Bridge) and Fastboot for Mac OS X and Linux. The script does not need to be downloaded, simply copy and paste this command into the terminal and run it to install ADB/Fastboot:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
and this command to un-install Nexus Tools:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/uninstall.sh)
Nexus Tools requires sudo privileges to install/uninstall the adb and fastboot tools to /usr/local/bin, so they can be run without typing the full directory. Nexus Tools is licensed under the GPLv3 license, and the source code is at the GitHub project below.
If you have a problem with Nexus Tools, leave a reply below or as an issue on the GitHub project!
GitHub Project
XDA News Article
Someone tested already??
im afraid..
zevim2005 said:
Someone tested already??
im afraid..
Click to expand...
Click to collapse
I've tested it on my Mac Mini (OS X 10.9), a Live CD of Ubuntu 13.04, and a custom Chrome OS x86 build and it worked on all of them.
zevim2005 said:
Someone tested already??
im afraid..
Click to expand...
Click to collapse
i just installed it. no problems. osx mavericks
just tried on my ARM Chromebook and its installing the Intel version... doesn't work 'cause their're binary files... any ideas?
edit: spotted the problem. the install script has the string for architecture (arch) set to "arm" whereas my chromebook returns "armv71" when the command is typed, so it defaults to intel
I tried editing the script and running it locally, but I get a "missing file operand" error when I do it... any help would be appreciated
edwinr29 said:
just tried on my ARM Chromebook and its installing the Intel version... doesn't work 'cause their're binary files... any ideas?
edit: spotted the problem. the install script has the string for architecture (arch) set to "arm" whereas my chromebook returns "armv71" when the command is typed, so it defaults to intel
I tried editing the script and running it locally, but I get a "missing file operand" error when I do it... any help would be appreciated
Click to expand...
Click to collapse
This is what i get on my Samsung Chromebook:
Code:
localhost / # bash <(curl https://raw.github.com/corbindavenport/nexus-tools/master/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4156 100 4156 0 0 17159 0 --:--:-- --:--:-- --:--:-- 20472
[INFO] Nexus Tools 1.2.1
[INFO] Please enter sudo password for adb/fastboot install
[ OK ] Sudo access granted.
mount: cannot remount /dev/ROOT read-write, is write-protected
[INFO] It appears your Chrome OS device is not rooted. Having root privliges is needed to install ADB and Fastboot.
[INFO] Type this into the command line and reboot to root your device:
[INFO] sudo /usr/share/vboot/bin/make_dev_ssd.sh --force --remove_rootfs_verification
I tried that last command with no further success.
---------- Post added at 11:57 PM ---------- Previous post was at 11:32 PM ----------
or.saeros said:
This is what i get on my Samsung Chromebook:
Code:
localhost / # bash <(curl https://raw.github.com/corbindavenport/nexus-tools/master/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4156 100 4156 0 0 17159 0 --:--:-- --:--:-- --:--:-- 20472
[INFO] Nexus Tools 1.2.1
[INFO] Please enter sudo password for adb/fastboot install
[ OK ] Sudo access granted.
mount: cannot remount /dev/ROOT read-write, is write-protected
[INFO] It appears your Chrome OS device is not rooted. Having root privliges is needed to install ADB and Fastboot.
[INFO] Type this into the command line and reboot to root your device:
[INFO] sudo /usr/share/vboot/bin/make_dev_ssd.sh --force --remove_rootfs_verification
I tried that last command with no further success.
Click to expand...
Click to collapse
Umm and then had to recover my device lol
thanks a lot bro
very helpful for beginners like me
or.saeros said:
This is what i get on my Samsung Chromebook:
Code:
localhost / # bash <(curl https://raw.github.com/corbindavenport/nexus-tools/master/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4156 100 4156 0 0 17159 0 --:--:-- --:--:-- --:--:-- 20472
[INFO] Nexus Tools 1.2.1
[INFO] Please enter sudo password for adb/fastboot install
[ OK ] Sudo access granted.
mount: cannot remount /dev/ROOT read-write, is write-protected
[INFO] It appears your Chrome OS device is not rooted. Having root privliges is needed to install ADB and Fastboot.
[INFO] Type this into the command line and reboot to root your device:
[INFO] sudo /usr/share/vboot/bin/make_dev_ssd.sh --force --remove_rootfs_verification
I tried that last command with no further success.
---------- Post added at 11:57 PM ---------- Previous post was at 11:32 PM ----------
Umm and then had to recover my device lol
Click to expand...
Click to collapse
your Chromebook has to be in developer mode for this to work
---------- Post added at 09:02 AM ---------- Previous post was at 08:46 AM ----------
Does anyone have a compiled version 1.0.31 of ADB for ARM
ADB and Fastboot will not work on 4.4 and above unless they are version 1.0.31. I have version 1.0.29 compiled for ARM and if I run the script and just replace the two files on /usr/bin/ they will work but I get "no permissions" when listing the devices because of the old version and the new RSA verification on android 4.4.
So if we can get a newer version of ADB compiled for ARM and then just run the following lines after the script runs:
" sudo cp /Downloads/ADB /usr/bin/adb" where "Downloads" is the folder where you downloaded the version of ADB, and do the same for fastboot, it should work
here are the links for the versions of ADB and Fastboot that I have:
ADB
https://drive.google.com/file/d/0B0boaxQIFMqAN0R5bnVYMGZLV3M/edit?usp=sharing
Fastboot
https://drive.google.com/file/d/0B0boaxQIFMqAVGI5Z09xZ3dpSkk/edit?usp=sharing
If you are running a device with 4.3 or older, these should work after you replace them in /usr/bin/
For the record, my chrome book is in developer mode
Sent from my Nexus 5 using XDA Premium 4 mobile app
or.saeros said:
For the record, my chrome book is in developer mode
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird... It worked in mine... Did u restart after running the command... I didn't the first time and it didn't work
Sent from my Nexus 7 using xda app-developers app
@corbin052198 what version of ADB is on your script? If it is 1.0.30 or higher, could you post the files for ADB and Fastboot?
here are the links for the versions of ADB and Fastboot that I have:
ADB
https://drive.google.com/file/d/0B0boaxQIFMqAN0R5bnVYMGZLV3M/edit?usp=sharing
Fastboot
https://drive.google.com/file/d/0B0boaxQIFMqAVGI5Z09xZ3dpSkk/edit?usp=sharing
If you are running a device with 4.3 or older, these should work after you replace them in /usr/bin/
Click to expand...
Click to collapse
Are these for x86 or ARM?
edwinr29 said:
@corbin052198 what version of ADB is on your script? If it is 1.0.30 or higher, could you post the files for ADB and Fastboot?
Click to expand...
Click to collapse
Nexus Tools installs ADB 1.0.31 on Mac and Linux, but right now Chrome OS uses an older version that doesn't support Android 4.2+ devices. I'm working on updating it.
corbin052198 said:
Are these for x86 or ARM?
Click to expand...
Click to collapse
They are for ARM... BTW thanks for the update... Will you b able to take a look at the arch string identifier for ARM on the install script???
Sent from my Galaxy Nexus using xda app-developers app
edwinr29 said:
They are for ARM... BTW thanks for the update... Will you b able to take a look at the arch string identifier for ARM on the install script???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The development branch of Nexus Tools already detects ARM on a Linux host, I just need to switch out the current (outdated) binaries for yours. Thanks!
EDIT: Forgot to ask, is this for armel or armhl ARM?
corbin052198 said:
The development branch of Nexus Tools already detects ARM on a Linux host, I just need to switch out the current (outdated) binaries for yours. Thanks!
EDIT: Forgot to ask, is this for armel or armhl ARM?
Click to expand...
Click to collapse
It's for a Samsung chromebook... So I'm not sure
Sent from my Nexus 7 using xda app-developers app
edwinr29 said:
It's for a Samsung chromebook... So I'm not sure
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Then I think it's armhf.
Nexus Tools 2.0
New in Nexus Tools 2.0:
Chrome OS and generic Linux both use same binaries
Detects processor platform for Linux (ARM or x86)
Downloads udev list for ADB
Script improvements/fixes
Thanks to XDA user edwinr29 for compiling updated ADB and Fastboot binaries for Chrome OS
corbin052198 said:
New in Nexus Tools 2.0:
Chrome OS and generic Linux both use same binaries
Detects processor platform for Linux (ARM or x86)
Downloads udev list for ADB
Script improvements/fixes
Thanks to XDA user edwinr29 for compiling updated ADB and Fastboot binaries for Chrome OS
Click to expand...
Click to collapse
Thanks for the credit Corbin, but I actually found those binaries in another thread here on XDA... When I find it I'll let you know so you can credit the creator...
Sent from my Galaxy Nexus using xda app-developers app
corbin052198 said:
New in Nexus Tools 2.0:
Chrome OS and generic Linux both use same binaries
Detects processor platform for Linux (ARM or x86)
Downloads udev list for ADB
Script improvements/fixes
Thanks to XDA user edwinr29 for compiling updated ADB and Fastboot binaries for Chrome OS
Click to expand...
Click to collapse
Just tried it and its still recognizing my ARM Chromebook as having and Intel processor and downloading the binaries for Intel...
Related
Hi
ADBBrowser is a GUI based file browser for Android devices. It will run on most Linux and Windows systems. Originally written for my Sony X10i, But should work on ALL android phones. Adbbrowser requires Android STK to be installed.
Get latest Adbbrowser
Regards
Balsat
works on ubuntu 10.10 x64, cheers
Hi,
Is there any way to get adb working from the terminal in linux ?
I am trying to experiment with my phone, but I can not get adb to detect my phone. I am using the following code inside 50-android.rules, but it does not work!
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666", OWNER="pavan"
However, replacing 0fce with the appropriate code for a Samsung Nexus S seems to work, so I do not think there is a problem with the installation.
Am I missing something ? Is trying to get the X10 to work with adb in Linux futile ? (I am asking because I have not any pages talking about this).
Thanks,
Pavan
while having the rules for it set is definitely the better choice, you can also just escalate the adb server to root-rights, which will allow it without problem.
Code:
adb kill-server
sudo adb devices
HI,
Thanks for the response! I have tried the following and it still does not work.
Neither does the adb browser.
trying to use adb
Code:
$ sudo lsusb -v | grep idVendor
idVendor 0x1d6b Linux Foundation
idVendor 0x1d6b Linux Foundation
idVendor 0x8087 Intel Corp.
idVendor 0x8087 Intel Corp.
idVendor 0x0b05 ASUSTek Computer, Inc.
idVendor 0x04f2 Chicony Electronics Co., Ltd
idVendor 0x0fce Sony Ericsson Mobile Communications AB
$ adb kill-server
$ sudo adb kill-server
$ sudo adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Trying to use adbbrowse
Code:
$ ./adbbrowse
[WARNING] Out of OEM specific VK codes, changing to unassigned
[WARNING] Out of unassigned VK codes, assigning $FF
TApplication.HandleException Access violation
Stack trace:
$00000000004D7A2C
$00000000004D7DD6
$00000000004D7F08
$00000000004C76F9
$00000000004C9F41
$00000000004D27FF
The browser window opens and the left pane says device NOT connected.
The phone says it is connected in USB debugging mode.
I am using freeX10 beta 2. (baseband: 2.0.46, kernel 2.6.29)
I am using 64 bit (Arch) Linux if that would help.
pavanky: there is nice program called qtAdb in AUR, works for me in my archbang
tr0llica said:
pavanky: there is nice program called qtAdb in AUR, works for me in my archbang
Click to expand...
Click to collapse
Does this work with X10 ?
The adb on my machine already works with Nexus S, but not with X10.
I will be giving it a try and provide an update once I go home.
Thanks for the information though!
----
I just checked out QtAdb
It does not detect the phone either!
pavanky: do you have usb debugging enabled? what rom are you running?
pavanky said:
The browser window opens and the left pane says device NOT connected.
The phone says it is connected in USB debugging mode.
I am using freeX10 beta 2. (baseband: 2.0.46, kernel 2.6.29)
I am using 64 bit (Arch) Linux if that would help.
Click to expand...
Click to collapse
Sorry if this was not clearer. But I think this is the information you are asking for ?
pavanky: oh ok, sorry, do you have openjdk or properiaty sun java? if you have openjdk you should try jre/jdk
pavanky said:
HI,
The browser window opens and the left pane says device NOT connected.
The phone says it is connected in USB debugging mode.
I am using freeX10 beta 2. (baseband: 2.0.46, kernel 2.6.29)
I am using 64 bit (Arch) Linux if that would help.
Click to expand...
Click to collapse
adb kill-server
sudo adb start-server
balsat said:
adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
Same as
Code:
adb kill-server
sudo adb start-server
does not work
tr0llica said:
pavanky: oh ok, sorry, do you have openjdk or properiaty sun java? if you have openjdk you should try jre/jdk
Click to expand...
Click to collapse
I have the proprietary version. I can not understand why one phone works while the other doesn't.
Hi all,
Thanks for the help! I uninstalled android-sdk provided by the user repo and installed from the android installer. Everything works perfectly!
I'm gonna try this. Should work fine, I've run adb perfectly on both my Ubuntu machines. It's easier to use than in windows, in fact.
sent from my FreeX10 Froyo beta using XDA App
Now Windows 32 bit is supported!
balsat said:
Now Windows 32 bit is supported!
Click to expand...
Click to collapse
Hi Balsat, can you share the sources?
Thanks
(This is not nessesary for MAC but you can have this for further use later,
In general you will need:
Python 2.4 -- 2.7, which you can download from python.org.
JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from java.sun.com.
Git 1.7 or newer. You can find it at git-scm.com)
Setting up a Mac OS X build environment
To build the Android files in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.6 (Snow Leopard).
Android must be built on a case-sensitive file system because the sources contain files that differ only in case. We recommend that you build Android on a partition that has been formatted with the journaled file system HFS+. HFS+ is required to successfully build Mac OS applications such as the Android Emulator for OS X.
Creating a case sensitive disk image
If you want to avoid partitioning/formatting your hard drive, you can use a case-sensitive disk image instead. To create the image, launch Disk Utility and select "New Image". A size of 25GB is the minimum to complete the build, larger numbers are more future-proof. Using sparse images saves space while allowing to grow later as the need arises. Be sure to select "case sensitive, journaled" as the volume format.
You can also create it from a shell with the following command:
# hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg
This will create a .dmg (or possibly a .dmg.sparsefile) file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named "android.dmg" stored in your home directory, you can add the following to your ~/.bash_profile to mount the image when you execute "mountAndroid":
# mount the android file image
function mountAndroid { hdiutil attach ~/android.dmg -mountpoint /Volumes/android; }
Once mounted, you'll do all your work in the "android" volume. You can eject it (unmount it) just like you would with an external drive.
Installing required packages
Install XCode from the Apple developer site http://developer.apple.com/. We recommend version 3.1.4 or newer, i.e. gcc 4.2. Version 4.x could cause difficulties. If you are not already registered as an Apple developer, you will have to create an Apple ID in order to download.
Install MacPorts from macports.org.
Note: Make sure that /opt/local/bin appears in your path BEFORE /usr/bin. If not, add
export PATH=/opt/local/bin:$PATH
to your ~/.bash_profile.
Get make, git, and GPG packages from MacPorts:
$ POSIXLY_CORRECT=1 sudo port install gmake libsdl git-core gnupg
If using Mac OS 10.4, also install bison:
$ POSIXLY_CORRECT=1 sudo port install bison
Reverting from make 3.82
There is a bug in gmake 3.82 that prevents android from building. You can install version 3.81 using MacPorts by taking the following steps:
Edit /opt/local/etc/macports/sources.conf and add a line that says
file:///Users/Shared/dports
above the rsync line. Then create this directory:
$ mkdir /Users/Shared/dports
In the new dports directory, run
$ svn co --revision 50980 http://svn.macports.org/repository/macports/trunk/dports/devel/gmake/ devel/gmake/
Create a port index for your new local repository:
$ portindex /Users/Shared/dports
Finally, install the old version of gmake with
$ sudo port install gmake @3.81
Setting a file descriptor limit
On MacOS the default limit on the number of simultaneous file descriptors open is too low and a highly parallel build process may exceed this limit.
To increase the cap, add the following lines to your ~/.bash_profile:
# set the number of open files to be 1024
ulimit -S -n 1024
Next: Download the source
Your build environment is good to go! Proceed to downloading the source....
Why you posted this? It can be found on android's website. Also,you didn't post the whole tutorial.
why not simply install VirtualBox vor Mac and install a VM within?
...sometimes the life is complicated^^
@SWEATTAIMI did you actually manage to get a fully working build on mac? And if yes which version of OS X?
I've tried many times on OS X 10.7 and eventually ended up installing ubuntu on a separate partition...
secondary partition? what about the users here?
i use a VM on a small **** x86 notebook and can do all the development work + complete compiling. i thought a mac has much better hardware^^
I used to have ubuntu installed in vmware too but compiling took too long and it was really annoying. I rather prefer it this way... No shared resources
popdog123 said:
@SWEATTAIMI did you actually manage to get a fully working build on mac? And if yes which version of OS X?
I've tried many times on OS X 10.7 and eventually ended up installing ubuntu on a separate partition...
Click to expand...
Click to collapse
Fully working what ?
Sent from my LG-P500 using xda premium
ciaox said:
Why you posted this? It can be found on android's website. Also,you didn't post the whole tutorial.
Click to expand...
Click to collapse
This is full for mac
Its a setup only
Sent from my LG-P500 using xda premium
SWEATTAIMI said:
Fully working what ?
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
:|
10 char
popdog123 said:
:|
10 char
Click to expand...
Click to collapse
You mean build then i have not came to that point yet as i downloaded all sources on my Japanese lesson xD
Sent from my LG-P500 using xda premium
I wonder if this will work for ICS on 4GB macbook
caslca said:
I wonder if this will work for ICS on 4GB macbook
Click to expand...
Click to collapse
Yes it will worked on a macbook 2010 version
Sent from Mexico
I have script that I want to make sure works on Mac OS X.
Could anyone test it for me?
Download here. Thanks.
Run it by:
Code:
chmod +x
./test
It's just a simple user input
Script output should be somewhat like this:
Code:
Enter input: [COLOR="SeaGreen"]XDA[/COLOR]
You typed: [COLOR="SeaGreen"]XDA[/COLOR]
What's the script do? I don't think most people want to just run a random script without knowing what it's purpose is.
SkyBehind said:
What's the script do? I don't think most people want to just run a random script without knowing what it's purpose is.
Click to expand...
Click to collapse
Sorry I forgot to explain it. It's just a simple user input
Script output should be somewhat like this:
Enter input: XDA
You typed: XDA
Ew mono
lithid-cm said:
Ew mono
Click to expand...
Click to collapse
>_< ... Do you have a Mac? (If you do can you test this?)
I have a Mac. I downloaded the file, there was no file extension. Tried running it with a .sh extension, no dice. Tried running it in terminal with no extension, again, no dice.
SkyBehind said:
I have a Mac. I downloaded the file, there was no file extension. Tried running it with a .sh extension, no dice. Tried running it in terminal with no extension, again, no dice.
Click to expand...
Click to collapse
Try issuing the command:
Code:
chmod +x
./test
This is what i get on OS X 10.8.2:
michael$ chmod +x test
michael$ ./test
-bash: ./test: cannot execute binary file
It's Compiled as windows portable executable. basically a windows console. as revealed with the linux "file" command
Code:
test: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
You need to check your compile settings buddy.
Alright I compiled it on Arch Linux (32bit)
file test:
Code:
test: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x1e06a9cf1d352f14daa5d1955a12ed185fd76768, stripped
Download the new one, here. Thanks.
(It's a simple user input. I just wanna test if it works on Mac)
Peteragent5 said:
Alright I compiled it on Arch Linux (32bit)
file test:
Code:
test: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x1e06a9cf1d352f14daa5d1955a12ed185fd76768, stripped
Download the new one, here. Thanks.
(It's a simple user input. I just wanna test if it works on Mac)
Click to expand...
Click to collapse
You compiled it for linux as well
Code:
ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x1e06a9cf1d352f14daa5d1955a12ed185fd76768, stripped
I'm not 100% sure but I'm fairly sure that won't work on OSX ( I could be wrong ) you need to compile for Darwin which is what OSX is.
works great on linux tho
trevd said:
You compiled it for linux as well
Code:
ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x1e06a9cf1d352f14daa5d1955a12ed185fd76768, stripped
I'm not 100% sure but I'm fairly sure that won't work on OSX ( I could be wrong ) you need to compile for Darwin which is what OSX is.
works great on linux tho
Click to expand...
Click to collapse
We'll see if it works on OSX or not...
I'm waiting for my Mac testers to be online...
Sorry, same as with the other one:
Michaels-MacBook-Proownloads michael$ ./test
-bash: ./test: cannot execute binary file
Michaels-MacBook-Proownloads michael$
You probably need a Mac to compile it for OS X.
Or maybe this helps:
http://devs.openttd.org/~truebrain/compile-farm/apple-darwin9.txt
Alright I think I've got it!
Can you please please test this new one?
file test:
Code:
test: Mach-O fat file with 2 architectures
Download here. Thanks!
Hi, I've tried run your file. This is the output:
-bash: ./test: Permission denied
Something missing?
alfanumerica said:
Hi, I've tried run your file. This is the output:
-bash: ./test: Permission denied
Something missing?
Click to expand...
Click to collapse
chmod a+x test
alfanumerica said:
Hi, I've tried run your file. This is the output:
-bash: ./test: Permission denied
Something missing?
Click to expand...
Click to collapse
chmod -x test
./test
I get a pop-up error:
Uncaught exception - [email protected]_read
sourcecodepoet said:
I get a pop-up error:
Uncaught exception - [email protected]_read
Click to expand...
Click to collapse
Same here. Lion 10.7.4
Sent from Xperia Mini Pro
I can't do that
Sent from my HTC Desire HD using xda premium
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attempting since monday tonight.
I'll explain more and I'll give more shots on working.
My issue now is to build the boot, recovery image to flash and boot it. The jolla sailfishos as a GUI operating system on Galaxy S3 I9300 model.
FIY : filename = sfa-i9300-ea-1.0.8.19-my1.tar.bz2
Instructions for chroot co,pilation on ubuntu amd64 x86_64 bit:
Code:
sudo mkdir -p /srv/mer/
mkdir -p $HOME/mer/
nano .bashrc
export $MER_ROOT=/srv/mer/
export $MER_ROOT=$HOME/mer/
ctrl +x to save and y
but type sudo apt-get install -y curl
for do the downloading file.
next do the following commands on terminal:
export $MER_ROOT=/srv/mer/
cd $HOME; curl -k -O https://img.merproject.org/images/mer-sdk/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
sudo mkdir -p $MER_ROOT/sdks/sdk ;
cd $MER_ROOT/sdks/sdk ;
sudo tar --numeric-owner -p -xjf $HOME/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
echo "export MER_ROOT=$MER_ROOT" >> ~/.bashrc
echo 'alias sdk=$MER_ROOT/sdks/sdk/mer-sdk-chroot' >> ~/.bashrc ; exec bash ;
echo 'PS1="MerSDK $PS1"' >> ~/.mersdk.profile ;
sdk
Now, do the following instructions:
$HOST>
nano $HOME/.hadk.env
export MER_ROOT="[/home/$user]"
export ANDROID_ROOT="$MER_ROOT/android/droid"
export VENDOR="[samsung]"
export DEVICE="[i9300]"
ctrl +x and y for save it.
nano $HOME/.mersdkubu.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
export PS1="HABUILD_SDK [\${DEVICE}] $PS1"
hadk
save it again
nano $HOME/.mersdk.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
hadk
now save this file.
Now in ctrl + alt + x, it will show a terminal:
type this:
sdk
type your password
hadk
TARBALL=ubuntu-quantal-android-rootfs.tar.bz2
curl -O http://img.merproject.org/images/mer-hybris/ubu/$TARBALL
UBUNTU_CHROOT=/parentroot/$MER_ROOT/sdks/ubuntu
sudo mkdir -p $UBUNTU_CHROOT
sudo tar --numeric-owner -xvjf $TARBALL -C $UBUNTU_CHROOT
hadk
ubu-chroot -r /parentroot/$MER_ROOT/sdks/ubuntu
exit
git config --global user.name "Your Name"
git config --global user.email "Your email"
back again for
hadk
cd $HOME
mkdir -p $HOME/mer/android/droid
repo init -u git://github.com/mer-hybris/android.git -b hybris-10.1
repo sync
after this, you will have HABUILD_SDK
DEVICE=i9300
export $DEVICE
source build/envsetup.sh
breakfast $DEVICE
now type
make hybris-hal
But now as a ota file for flashing on i9300, in this last 2 days in my laptop core2Duo Extreme I'm facing overheating.
So, everyone can test it.
Code:
A little change on mount fixups.
Go to the directory hybris/hybris-boot
nano mount-fixups on i9305| encore)
put the "i9305" | "encore" | "i9300")
Script for booting sailfishingos on an android terminal. This script is to mount the binds folders and for fixing for preventing the /dev/null issue when we all boot the chroot sailfishos.
name of the script : sailfishos.sh - made it on the /extsdCard/ folder.
1) nano /extSdCard/sailfishos.sh and copy the following code
2) ctrl +x to save it
3) bash sailfishos.sh
Code:
su
mount -o bind /dev /data/.stowaways/sailfishos/dev
mount -o bind /proc /data/.stowaways/sailfishos/proc
mount -o bind /sys/ /data/.stowaways/sailfishos/sys
chroot /data/.stowaways/sailfishos/ /bin/su -
echo "nameserver 8.8.8.8" > /etc/resolv.conf
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
See folders on it.
PS: I'll give more shots also more instructions very soon. Thanx.
Another PS: I'll give more news about Jolla sailfish os very soon.
But I need to tell this, I've got i9300 defconfig kernel for Jolla sailfishos very similar to defconfig i9305 kernel and I got it compiled with very success on hadk Ubuntu chroot on mine Ubuntu 14.04 LTS version.
astronfestmon said:
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attemptinh since yesterday tonight.
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
sees folders on it.
Click to expand...
Click to collapse
Screenshots?
Sent from my SM-G900F using XDA Free mobile app
Fantastic... I'll give a try. Plz provide some more details, screenshots & new features from your currently running sailfish os. Thanx for sharing
i fed with adb commands & not able to flash
Uhm ... I gonna wait for this ...
Sent from my SM-G900F using XDA Free mobile app
how to install ?
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
astronfestmon said:
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
Click to expand...
Click to collapse
any update on this?
I followed the above procedure and I can see the Sailfish version and the files list from adb. What next?
EDIT: Just saw your PS in OP
In the end of the week probably I'll release the boot kernel working on.
astronfestmon said:
In the end of the week probably I'll release the boot kernel working on.
Click to expand...
Click to collapse
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
astronfestmon said:
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
Click to expand...
Click to collapse
It would be great if you could make it to boot.
I will try to compile the kernel with CONFIG_CMDLINE="console=tty0" . I'm hoping that would direct kernel panic message to the screen so we could idenfity what the problem is with booting hybris-boot.img
So... Any development?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
astronfestmon said:
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
Click to expand...
Click to collapse
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
redrum781 said:
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Click to expand...
Click to collapse
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
rusty88 said:
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
Click to expand...
Click to collapse
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
MaxAndroided said:
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
Click to expand...
Click to collapse
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
msri3here said:
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
Click to expand...
Click to collapse
yes @msri3here technically that is what i'm doing, its using RIL lib based on cm10.1.3 that was working fine before I flash sailfish, but on sailfish the log that RIL daemon dumps is really a mess and haven't figure out why is failing. One thing that I've notice is that RILD (one of its child process) creates the socket at /dev/socket/rild but it's killed afterwards, the sockets disappear and the process restarts all over again
Stracing RILD is not helping either as it seems that everything is Ok.
I'm trying to buy a new smartphone for day to day use so I can dedicate more time to debug on my i9300.
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
tried your rom but stuck on "samsung galaxy s 3 gt-i9300" screen nothing is happening plus if i touch the screen i get a response from the capacitive buttons but thats all
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
johnaaronrose1 said:
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
Click to expand...
Click to collapse
have you tried using chocolatey on the windows VM, to see if their adb source works for you?
you would need chocolately preinstalled, this thread would explain better.
How To Use Chocolatey
========================= ============================================ HOW TO USE CHOCOLATEY ============== ============= Hi Friends~! This amazing package manager changed my Windoz life
forum.xda-developers.com
after you have chocolatey installed, you would run this command:
choco install adb
essentially, it will dl the latest adb, and wrap all it's variables with the correct permissions, even in a vm. I'm not sure if this will help you, but just wanted to put it out there~!
Have a good day~!
jenneh said:
have you tried using chocolatey on the windows VM, to see if their adb source works for you?
you would need chocolately preinstalled, this thread would explain better.
How To Use Chocolatey
========================= ============================================ HOW TO USE CHOCOLATEY ============== ============= Hi Friends~! This amazing package manager changed my Windoz life
forum.xda-developers.com
after you have chocolatey installed, you would run this command:
choco install adb
essentially, it will dl the latest adb, and wrap all it's variables with the correct permissions, even in a vm. I'm not sure if this will help you, but just wanted to put it out there~!
Have a good day~!
Click to expand...
Click to collapse
The specified link does not AFAIK give instructions on how to install chocolately.
Oh It Does~! As well As a VM demonstration on how to install on an unlisted YT vid. But Okay~! Just trying to help ;-)
The link you supplied with its links to "How to install chocolately" sends me to an advertising site.
johnaaronrose1 said:
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
Click to expand...
Click to collapse
Would this help?
Android SDK Platform Tools for Windows
Android Debug Bridge version 1.0.26 platform-tools_r03-windows.zip (2011-02-23) platform-tools_r04-windows.zip (2011-05-10) platform-to...
cxzstuff.blogspot.com