Database Users

Switched to linux

After switching to linux, my phone no longer recognizes my computer and doesnt give the option to go to disc mode, sorry if its a dumb question but could someone tell me what i need to do to get it working again? Im not familiar with the os yet so im clueless.

you can't use mass storage mode?

it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in

Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Do you have debug turned on on the phone?

Thats because Linux doesnt see your phone. You need to setup UDEV to recognize your Hero. Follow this tutorial. And when I say "Follow" I MEAN FOLLOW. No skipping.
http://forum.xda-developers.com/showthread.php?t=537508

do i have to reinstall linux to do this ?

Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
What flavor do you have?

im using mint i think its based on ubuntu

So, did you follow directions? Should work with any flavor of Linux.

im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)

Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
No, you don't have to reinstall Linux.
Justjusten said:
im using mint i think its based on ubuntu
Click to expand...
Click to collapse
Mint is a derivative of Ubuntu, so yes, it's based off of it.
Justjusten said:
im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)
Click to expand...
Click to collapse
You don't need to create the .bashrc file... it's already there. The period in front of the bashrc indicates that the file is hidden.
To see hidden files, run this command:
Code:
[B]ls -a[/B]
This will show you hidden files, any files with a period in front of it, will always be hidden.

Or navigate to the folder that it says that it is in and press ctrl + h
This will show you all the hidden files inside of the folder. Without having to use the terminal.

Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Did you try pulling down the status bar and clicking on Charge Only to set it to disk mode?
If all else fails you can reboot to recovery and USB-MS toggle. If that doesn't work then something is messed up in your distro. Test if mounting works while in recovery and report your results.

I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?

Justjusten said:
I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?
Click to expand...
Click to collapse
There shouldnt be anything wrong with your Distro. Mint is built off Ubuntu so in essence it should work. Maybe download Ubuntu.

i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it

You cant edit it because you have to have root access. You should try typing in terminal sudo chmod permissions to give you root access. Im definitely not that good at linux but i figured out a majority of it.

make a file in /etc/udev/rules.d/ called 51-android.rules
here is mine.
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666" , GROUP="plugdev"
Make sure you belong to the plugdev group, you probably already are. I can execute adb commands without being root user.

Justjusten said:
i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it
Click to expand...
Click to collapse
just stick to what works and that's windows 7, i hate linux on a pc.

fixxxer2008 said:
just stick to what works and that's windows 7, i hate linux on a pc.
Click to expand...
Click to collapse
Well that is a debate topic for another place. For me I've formatted the drive on my last 4 new laptops and have not looked back.

[ Tutorial / Reference ] Learning to Build for Galaxy Note

--
{
"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"
}
INTRODUCTION
There are several guides and tutorials that teach you how to build your own custom firmware from source.
To the trained eye, the steps to be followed are essentially the same.
But to users with relatively lesser experience in programming or software development/scripting of any kind, it often seems to be a daunting task.
One of the many reasons for this is that users usually have atleast 2 similar guides open side-by-side on their screens.
And when one or two lines of code/instruction do not match, all hell breaks loose.
This might not be the case with you, but it sure was with me.
This guide is based solely on my experience in starting from scratch, trying to build a ROM from CyanogenMod and AOKP sources​​
Before we proceed any further, I would like to clarify that this is NOT a definitive tutorial,
nor is it the best way to get started in ROM development.
There may be ‘kanging’ involved, zipping-unzipping as well.
Purists may take exception to some steps – but then they are purists for a reason.
My purpose is NOT to oppose what the better-skilled developers opine,
nor is it to encourage the said procedures.
However, in the event that I do mention using them –
be aware that the attempt is solely to provide a small impetus to enthusiastic learners, so that it may help them have some know-how on how to finally get started. ​
I intend to proceed slowly, rather than publishing the entire thing all at once
and then having confused users discussing Step 2 and Step 2002 at the same time.
In order to avoid this, the posts that follow will be updated in parts i.e
we shall together proceed ahead once a sizable majority of participants have successfully completed a chunk of required steps.
This, I feel, will ensure that the ensuing discussions are enjoyed and benefitted from by several more users at any given time.
REQUIREMENTS
We would be using the CM10 and AOKP sources as reference to learn building for our device.
For the purpose of this tutorial, we shall work together on the following environment –
◘ Ubuntu 12.04 64-bit
◘ A minimal requirement of a Quad-Core processor with >= 4 GB RAM
◘ A high-speed connection >= 2 mBps
◘ Solid State Drives are highly recommended.
◘ Google Toolbar
◘ Patience
◘ Patience
◘ And more Patience
​
Assuming that you would be syncing either one of the source trees, you would require
about 70-80GB of free space to sync repositories and compile a ROM from start to finish.
Users on Windows have an option of dual-booting.
If they are hesitant to do so, they can also run Ubuntu using a Desktop Virtualization Software.
However, in this case you would then require atleast 6GB of RAM, if not more,
to run both operating systems concurrently.
Users building on a remote server, I presume, would be spoilt for choices different Linux distributions available.
Be sure to have an SCP client in handy.
It is my humble request that we all follow good etiquettes and rules all the more strictly to ensure an enriching learning environment.
◘ Please do not troll here.
◘ The thread is not to be used for smug remarks or aspersions (as most of us are accustomed to)
◘ Code Snippets that will be posted on this thread using the code tag, as part of this thread, are supposed to be entered into the Linux terminal.
◘ You are requested to use Pastebin to post logs and build errors
◘ Please do not use any fancy fonts or bold typefaces.
◘ Please do not create Thank You posts if a particular solution solves your problem.
​
Each and every solution will be verified, and the author in turn will be requested to mark his post in Bold-Green.
Hence the last point above..
It is a given that this shall forever be a Work in Progress.
Things will be added, things will be removed as time flies by.
The only thing that should remain constant is the willingness to learn.
And the willingness to use Google Search.
BIBLIOGRAPHY
◘ [Tutorial] Compile JB on Ubuntu
◘ [TUTORIAL] So You Want To Build AOKP JB? [Ubuntu 12.04+]
◘ CyanogenMod WiKi
◘ Android Open Source Project
◘ Frequent IRC chats with Pier and bajee11
◘ Google chats with other kind developers, users and friends
--

Part 1: Setting-up Build Environment
--
A Build Environment is the state of the machine being used for development, including the directory structure and environment variables for your particular project. ​
Additionally, the command-line build environment for the platform and projects is your build release directory.
And so it follows that though we have our Ubuntu installations done, we are still required
to install additional packages to set-up a build environment suited for our purpose.
OpenJDK is an open-source implementation of the Java Platform, Standard Edition, and related projects.
We shall use OpenJDK-6. Type the following in your terminal -
Code:
$ sudo apt-get install openjdk-6-jdk
At the end of this step you might get a message in terminal related to the need
to update certain elements to complete installation of required packages.
For this, simply run
Code:
$ apt-get update
Python is a general-purpose, interpreted high-level programming language,
whose design philosophy emphasizes code readability.
It may already be installed on your system. But no harm in checking -
Code:
$ [B]sudo apt-get install python[/B]
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Code:
$ [B]sudo apt-get install git-core[/B]
The Android software development kit (SDK) includes a comprehensive set of development tools.
These include a debugger, libraries, a handset emulator based on QEMU, documentation, sample code, and tutorials.
There are 2 ways to install this.
If your Ubuntu setup is on your Home PC and you have GUI access,
you can download the package from here
http://dl.google.com/android/android-sdk_r20.0.3-linux.tgz
To do the same via command line, type this in your terminal -
Code:
$ [B]wget http://dl.google.com/android/android-sdk_r20.0.3-linux.tgz[/B]
This will download the very same package for you to the current working directory.
Now, you have to extract the folder inside the archive, and place it in your home directory.
To do this, enter the following command in your terminal -
Code:
$ [B]tar -xvzf[/B] <filename>.<extension>
For example, if your archive is named android-sdk_linux.tar.gz
where
android-sdk_linux = filename
tar.gz = extension
you will type -
Code:
$ [B]tar -xvzf android-sdk_linux.tar.gz[/B]
Once your folder is extracted, move it to your home directory. Search Google on how to do it.
Next step is to define the path.
For this, go to your home folder and look for a file named .bashrc
For users having the comfort of a GUI, press Ctrl + H incase the file is not visible.
Remote users can use their SCP Client to find the file easily.
Open the file to edit it, and at the bottom paste the following lines -
Code:
# Android tools
export PATH=${PATH}:~/<folder_name>/tools
export PATH=${PATH}:~/<folder_name>/platform-tools
export PATH=${PATH}:~/bin
In the same manner and place, look for the file named .profile and add the following lines at the end -
Code:
PATH="$HOME/<folder_name>/tools:$HOME/<folder_name>/platform-tools:$PATH"
Once, done you now have the Android SDK successfully installed. :good:
In the end, you have to install the remaining packages and libraries and dependencies and what not.
This varies as per the version of the Ubuntu installation.
Since we are (hopefully) on Ubuntu 12.04 (64-bit) , we need to enter the following command in our terminal -
Code:
$ $ s[B]udo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386[/B]
and then
Code:
$ [B]sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so[/B]
In the even that you get errors relating to unavailability of g++ and gcc
run the following in terminal -
Code:
$ [B]apt-get install gcc[/B]
Code:
$ [B]apt-get install g++[/B]
and then repeat the previous steps.
I would also advise that you install the following as well (more on it later) -
Code:
$ [B]apt-get install lzma[/B]
Code:
$ [B]apt-get install screen[/B]
With the above done, all that is left to do is to initialize the repository that you require and then sync it to your machine or remote server. This we do in the next part.
--

Part 2: Fetching sources
--
Repo is a repository management tool that was built on top of Git
.
Repo unifies the many Git repositories when necessary, does the uploads to the revision control system, and automates parts of the Android development workflow.
Repo is not meant to replace Git, only to make it easier to work with Git in the context of Android.​
More information on the subject can be found here.
In our context, we need to download repositories of the correct Android branch (ICS, JB etc) for which we want to build.
But whose branch?
That is completely upto you to decide.
The first step is to 'download and install the repo binaries'. Issue the following commands in terminal -
Code:
$ [B]mkdir ~/bin[/B]
$[B] PATH=~/bin:$PATH[/B]
$ [B]curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo[/B]
$ [B]chmod a+x ~/bin/repo[/B]
With this done, we now make a new folder in our home directory where we would be downloading our rom sources by initializing the relevant repo
Code:
$ [B]mkdir myrom[/B]
$ [B]cd myrom[/B]
For CM10
Code:
$ [B]repo init -u git://github.com/CyanogenMod/android.git -b jellybean[/B]
For AOKP
Code:
$ [B]repo init -u git://github.com/AOKP/platform_manifest.git -b jb[/B]
You will most likely be prompted for certain details like name, email etc. Fill those in and proceed to the next step.
Once you have the above completed ( repo has been initialized in /....) it is time to sync! :good:
Simply issue the command -
Code:
$ [B]repo sync[/B]
You might have come across variations like
Code:
$ repo sync [B]-j4[/B]
or
Code:
$ repo sync [B]-j16[/B]
Essentially, all are performing the same function. Only difference is that by adding that little -j
we are specifying how many jobs we want to run concurrently, which is in a way directly related
to the number of cores powering your machine.
I have a quad-core, he has a dual-core, what should we use?
Go ahead and see for yourself.
Your first sync (rather a download) would likely take around 45 minutes to 1 hour, if you have a decent internet connection.​
The first time I decided to do this, I wasn't aware of how big the repositories could be, or what sort of an internet connection one would require.
As long as it was an unlimited data plan (yes we have limited data plans in our country), it would be fine I thought.
I had the screen active for around 6 hours without any signs of stopping, until I was finally put out of my misery by good friend antiochasylum -
me: Wow
It takes us a day to download movies
20kbps. Its party time if I can get anything
above 100kbps
Matt: Holy ****. Lol. Mrs Antis galaxy s2 lte gets 5500 down.
Blows the **** outta my note
me: :sniff:
Click to expand...
Click to collapse
Sit back and enjoy.
Do not get all tensed if the text on your screen suddenly stops moving OR is stuck at some place.
Unless and until you are back to the bash shell with a definite error message explaining why repo sync was interrupted - you are all good. :laugh:
--

rvd

reserved

one more

last

And this one is for me..... Thanks a lot dude... will keep watching this space..

Thank you so much, this is great for us newbies :highfive:

Wow, wanted to learn since longthanks

Great idea toxic, you might've just encouraged me to start compiling and building again
Sent from my GT-N7000 using XDA Premium HD app

thanks

Grrr888888. thank you very much :good:

Thank you, with my computer it gonna take forever compiling , it's is only dual core 2,1 ghz :silly:.
But since i've got patient, i'm gonna try.
PS: I have plans to install gentoo on the same team at some point in the future so this will be easy in comparison.

Please share this with other users who might be interested so that all can benefit.
Thanks
Sent from my GT-N7000 using xda premium

While setting up Ubuntu via VM for windows i am able to run though entire installation procedure but getting an critical error after i restart when the installation is complete..
sorry, this may not be exactly related with the topic directly but i thought i might find my answer here..
Sent from my GT-N7100 using Tapatalk 2

What would the error message be? I mean what exactly does it say?
Sent from my GT-N7000 using xda premium

http://pastebin.com/VLtJzaqd
Ubuntu log for your ready reference.

sunny2303 said:
http://pastebin.com/VLtJzaqd
Ubuntu log for your ready reference.
Click to expand...
Click to collapse
It seems he SATA controller in your VM has only one port configured and is unavailable to make hotplugging work.​
Make sure you are not trying to run your installation from a Guest/Limited account.
Also, in case you're trying to run Ubuntu from a CD instead of copying files to the the hard disk, you may face some problems.
Sent from my GT-N7000 using xda premium

Thanks this solution worked You were right the isse was with SATA controller.. I had not assigned it. After assigning it under settings, it worked.
Now I have moved slightly ahead... at the path setting stage
export PATH=${PATH}:~/<folder_name>/tools
export PATH=${PATH}:~/<folder_name>/platform-tools
export PATH=${PATH}:~/bin
while we are writing this in .bashrc are we supposed to replace <folder_name>/ with actual folder name? like say extracted folder name is android-sdk-linux which is placed under home.. so should we write <android-sdk-linux> ?

[GUIDE] How to Set Up ADB & Build Android with Fedora KDE

Hello all. I have written a guide to setting up & using Android ADB, & building Android, with Fedora KDE. Almost every guide that I've ever seen for setting up ADB, & a build environment for building Android, is always written for Ubuntu, & ONLY Ubuntu. But I choose to work with Fedora KDE. Why Fedora with KDE??? Because I hate Ubuntu. !!!HATE!!! I also can't stand gnome 3.X. I'm sure I'm not the only one who feels this way, so that's why I'm writing this guide. I've tried different linux distros, & I've found Fedora to be the best of all. It is my favorite now. They also seem to be one of the few distros that stays on top of the linux kernel updates. As of 03/20/13, they're already on kernel 3.8.3!!! Other distros stay way behind. Also, with KDE, you can keep the "windoze" traditional desktop look & feel, especially when you use the "folder view" activity. It's great!!! Well, let's get started.
!!!WARNING!!! Before anything else, I will mention this right now. The Dolphin file manager can destroy your Android build with hidden ".directory" files. Please keep this in mind. I will explain this at the end of the guide.
INSTALL JDK6
-I guess I'll mention this 1st, since this can actually be one of the most painful & confusing parts of all. You'll need to install the java jdk6. As far as I know, Android stuff won't work with the newer jdk7. You can find it on oracle's page here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
-Scroll down & you'll see it. Get the "rpm.bin" version. If your working with 64bit, it should look like this:
jdk-6u43-linux-x64-rpm.bin
-Someone by the name of JR already made a very good guide on how to do this. It is what I followed, & you should too. You can find it here:
http://www.if-not-true-then-false.c...java-jdk-jre-6-on-fedora-centos-red-hat-rhel/
NOTE: When following this guide, be sure to go through only steps 3a & 4a when you reach them. Steps 3b & 4b are for the "non-jdk" jre.
NOTE: The "alternatives" listed in step 4 seems to be some kind of program that creates symlinks for whatever you want, & labels them. When you install, or create the symlinks, you can then use "alternatives" to switch back & forth between the different programs that you make the symlinks for. For example, you can make links for java in jdk6 & jdk7, & then switch to either one or the other, as you please. That way, you can have them both installed, while using only one at a time. You can type "alternatives --config java" to switch, or whatever name you used for the link. For help, type "alternatives --help".
INSTALL SDK
-You can follow these:
http://developer.android.com/sdk/index.html
http://fedoraproject.org/wiki/HOWTO_Setup_Android_Development
SETTING UP ADB
-Download the sdk & unpack it somewhere in your home directory. For example, I like to put mine in "~/Android-Development/sdk" (the ~ symbol is short for your Home folder).
-cd to your sdk tools location. For example, from my Home folder, I would type this:
Code:
$ cd Android-Development/sdk/tools
-NOTE: DON'T TYPE THE DOLLAR SIGN!!! I put it there because that's what you see in the terminal. It's only there for reference.
-NOTE: At any time, you can type "ls", or "ls -l" to see everything in the folder you're currently in.
-Now, execute the android program.
Code:
$ ./android
-Install Android SDK Tools & Platform-tools.
-Install 32bit packages. Since Android is a 32bit OS, you must install the 32bit packages regardless if whether your computer is 64bit or not.
Code:
$ sudo yum install glibc.i686 glibc-devel.i686 libstdc++.i686 zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrender.i686 libXrandr.i686
NOTE: In order to install packages with yum, you must do it as su. You can either type sudo before the command, or you can just type "su" & enter your password to become superuser. If you're new to the command line, it's probably better to use "sudo" instead, that way you won't stay logged in as superuser & potentially mess things up.
-Now, it's time to install the udev rules. Basically, they are the rules that govern whatever device you plug in with USB. You can find all the info on this page:
http://developer.android.com/tools/device.html
-Create an empty file named 51-android.rules to write in. We will create it in /etc/udev/rules.d/
Code:
$ sudo touch /etc/udev/rules.d/51-android.rules
NOTE: "Touch" is a linux command that you can use to create a new, empty file. To see more info on it, type "touch --help", or "man touch" to see the manual page for it. Of course, you can always google it, & anything else as well. Google "linux commands touch".
NOTE: Since this file is in the root user's directories, you will need to enter commands as superuser, or else it won't save. Either type "sudo" before the command, or, if you're comfortable with the command line, log in as superuser by typing "su" & entering your password.
-Now, you can use any text editor to write inside that file you just created. I like to use nano from the command line, so let's use that. ("nano --help", "man nano", google "linux commands nano")
Code:
$ sudo nano /etc/udev/rules.d/51-android.rules
NOTE: In linux, you can copy & paste without even "right-clicking" & selecting copy or paste from the menu. Instead, you can just highlight some text, & go somewhere else & press the mouse middle button to paste it. Highlighting text will automatically copy it, & pressing the mouse middle button will automatically paste whatever you highlighted. No need for "right-clicking" anything. You can do this for the next step.
-Now, from the webpage listed above, just copy & paste the lines with the USB Vendor IDs that you want to use. For example, for Asus, HTC, & Samsung, write these:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
-Save & exit the file.
NOTE: In nano, you can always see important commands at the bottom of the screen. For example, to exit, you hold in the "control" button & press "x".
-Now, check the permissions of the file & make sure everyone can read it.
Code:
$ ls -l /etc/udev/rules.d/
-You should see something like this:
Code:
$ -rw-r--r--. 1 root root 639 Feb 5 14:08 51-android.rules
NOTE: The 1st line indicates whether it's a directory or not. The next 3 lines indicate Read, Write, & eXecute permissions for the user. The next 3 lines indicate Read, Write, & eXecute permissions for the group. The last 3 lines indicate Read, Write, & eXecute permissions for others. The 1st "root" means that root is the user. Root owns that file. The 2nd "root" means that the file belongs to the group root.
-If for some reason you don't see the "r" letters (meaning that it's readable) to the left of the file name, then just change the permissions. Add "read" permissions for all.
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
-Finally, if you didn't do it earlier, now's a good time to do this. Make sure the ADB folders are in your global PATH. This is so that you can use the ADB commands anywhere in the system, no matter what folder you're currently in.
-Return to your home folder.
Code:
$ cd
NOTE: In the linux command line, simply typing "cd" & pressing enter will bring you right back to your Home folder.
-There's a hidden file called ".bash_profile" in your home folder. You can see it if you LIST ALL:
Code:
$ ls -a
-Your global PATH is defined in there. Let's edit it to add the ADB folders.
Code:
$ nano .bash_profile
-You'll see that there's already one line in there with 2 entries that look like this:
Code:
PATH=$PATH:$HOME/.local/bin:$HOME/bin
You can use that as your example as to what the format should look like. The line begins with
Code:
PATH=$PATH:
Then there are 2 entries, with each entry separated by a colon. Each entry must be separated by a colon and NO space.
Code:
$HOME/.local/bin
is one entry, &
Code:
$HOME/bin
is the other entry. Now, we want to add our 2 ADB folders to the list. You can either add each path to your folder separated by a colon & no space, like the example, or you can start your own line. I always like to start my own line underneath that one. So, for example, here's what my new line looks like:
Code:
PATH=$PATH:$HOME/Android-Development/sdk/platform-tools:$HOME/Android-Development/sdk/tools
-Everyone likes to use different folder names. Remember to use the proper path of where you put your folders in.
-Save & exit the file. That's it. Now, reboot your computer, plug in your android device, & test it out. You should be able to type "adb devices" from any folder, & the computer should be able to see it now.

INITIALIZING YOUR BUILD ENVIRONMENT
-For me, this was the hardest part of the whole process, as there wasn't a lot of help on how to do this for Fedora with KDE. Whatever few guides for Fedora I found out there were usually missing something here & there. My goal is to change that & help everyone. I've gone through this multiple times now, including multiple reinstalls of Fedora 18 from scratch.
-You'll need to install lots of drivers & libraries.
NOTE: Use Apper, the software management program, to look up drivers & libs. Apper will show you many different files that have the name that you typed in, whereas yum won't. Personally, I like to look things up with Apper so I can get lots of hits, & then actually download them by typing them in manually with yum. Yum shows you what it's actually doing behind the scenes while it's downloading things, whereas Apper doesn't. If yum gets stuck & hangs, you can actually see what's going on, whereas Apper won't show you anything & will just leave you wondering what's going on.
NOTE: I have found it to be a good idea to always look for the development (-devel) version of anything that you have to install. Not everything has a development version, but some do. For example, if you look up "flex" in Apper, you'll see that there's also a "flex-devel". Be sure to download them both.
-Here is what I went by:
http://fedoraproject.org/wiki/HOWTO_Setup_Android_Development
http://source.android.com/source/initializing.html
http://wiki.cyanogenmod.org/w/Main_Page
http://wiki.cyanogenmod.org/w/Build_for_maguro
-I used the lists on the fedora page, & I also used the lists of required packages for Ubuntu 10.04 & 12.04. I chose to try a build for Samsung Galaxy Nexus, since that's what I have. While going through the Ubuntu lists, you must keep in mind that some of these packages don't exist for Fedora, & many others do exist with slightly different names. It is best to spend some time & look them up 1 at a time using Apper. For example, typing "libxml2-utils" into Apper shows nothing, but typing in "libxml2" shows results. Finally, whatever you still can't find, you must google search it. For example, google search = "fedora libxml2-utils" You'll get clues & answers from what other people have already found about them. I mainly used the Ubuntu lists of necessary libs to download. So, without further ado, here's everything that I did that works for me...
Code:
$ sudo yum install git gnupg gnupg2 flex flex-devel bison bison-devel gperf gcc gcc-c++ make automake kernel-devel zip curl zlib zlib-devel glibc glibc-devel ncurses ncurses-devel xulrunner xulrunner-devel libX11 libX11-common libX11-devel xorg-x11-proto-devel readline readline-devel mesa-libGL mesa-libGL-devel mesa-libGLU
NOTE: You won't need mingw32 & tofrodos.
Code:
$ sudo yum install python-markdown libxml2 libxml2-devel libxslt libxslt-devel perl perl-devel perl-Switch SDL SDL-devel wxGTK wxGTK-devel squashfs-tools pngcrush schedtool
NOTE: If you installed Fedora with the options for development programs, than some of these will be installed already. This list may be a slight bit of overkill, but I purposely wrote down everything anyway, so that way nobody misses anything. I went through hell when figuring this out, so it's better to be safe than sorry.
NOTE: If you've been doing everything logged in as superuser, be sure to exit su when you're not installing things anymore. If you create directories as root user, you won't have permissions to access them under your own name, unless you manually change the permissions. Other permissions issues can arise too.
-After all this, it's just a matter of installing the directories & repo, & following the remaining directions on the CyanogenMod Wiki build guide page. I wanted to sync up with the Jellybean branch, so as an example, I set my directories up like this:
Code:
mkdir Android-Development/Builds/bin
mkdir Android-Development/Builds/CM10.1_Jellybean
-Whenever I download the repo command, I do it like this:
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/Android-Development/Builds/bin/repo
-You'll need to add this to your global PATH as well, so be sure to do that, then log out & back in again, or reboot to make it active. Do that, & then continue.
-Then, I go inside the CM10.1_Jellybean folder to do the repo init. (Get ready for repo sync. That takes hours!!!)
-That's pretty much it. : ) Be sure to read through the sites & all their instructions & guides to help you understand everything.
!!!WARNING!!! Here is what I mentioned all the way at the beginning. Please don't forget the most important thing of all: those damn hidden ".directory" files. Any time you change the folder views in Dolphin File Manager, it places a hidden ".directory" file in that folder. THESE HIDDEN FILES WILL DESTROY YOUR BUILD!!! I went through hell with this, trying to figure out what was going on. I always set up the Android folders to show in "details" view mode, so that they're easier to see. Every time I tried to build, it would build for 5 or 10 minutes, & then fail, citing errors in java. I eventually realized that the ".directory" files were the cause of all the problems.
If you change the folder views, you need to get rid of those hidden ".directory" files. You'll have to do it in terminal. A good way to do it is by using the "find" command to find them all, & then pipe the output of that into the "rm" command to remove (delete) them all. ("find --help", "man find", google "linux commands find")
The "find" command can find whatever you're looking for in the current directory, & in all of its sub-directories as well. With the "rm" command, you can also use the "v" option. "V" stands for "verbose". It will show you everything that is being done, as it's being done. As an example, here's how I do it on my computer:
Code:
$ cd ~/Android-Development/Builds/CM10.1_Jellybean
$ find -name .directory -exec rm -v '{}' \;
That will find all of the ".directory" files & delete them all. It works pretty fast too. With the "v" option, it will show you what's going, while it's happening, as well. So, if you're like me & think that it's much easier to see huge lists of folders in "details" view mode, feel free to set it for the current directory & all sub-directories as well. However, DON'T FORGET TO DELETE all of the ".directory" files before you start building, or your build WILL FAIL!!!
Well, as you can see, you can customize some things to your liking. There's plenty of learning involved, so be ready to spend lots of time with everything. Good luck, & have fun!!!

Now, I'd like to add a personal note. After all this, I'm able to build Android from source with no problem now. However, I tried porting CyanogenMod & building ClockworkMod recovery for some Ainol Tab that I have. Long story short, in the end, it didn't work. I learned about having to build your own device tree, & I found myself completely lost in a sea of xml & java that I didn't understand at all. That's when I realized how much I don't know. It's also when I quickly realized the good advice of cyanogen himself...
http://forum.xda-developers.com/showthread.php?t=667298
"... Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. ..."
His advice is dead on accurate. Now I know why he says the things he said. I have no previous experience with java, or any other programming language. In trying to do these things, I found myself completely lost in code that I didn't understand at all. How can I possibly mess around with entire ROMs when I don't even know what's going on under the hood???
Since then, I've been concentrating most of my spare time learning java. It's a bit overwhelming to say the least, but I am getting it now. Recently, I took a peek back at all the code that confused me before, & I'm actually starting to understand it all now. I'm no longer lost. Studying java (& xml) is actually working, & quite well too. I can personally confirm cyanogen's advice to be spot on, & well worth listening to.
So, in conclusion, if you're wanting to get into messing around with ROMs & stuff, but you have no programming experience, I think it would be best to take cyanogen's advice & start at the higher levels first. Learn some java (& xml), & learn to build a simple app or two for Android. You'll better learn how the system works that way. That's what I'm doing now, & it's really working for me. Doing this should help you out with ROMs, & app development too. Well, I hope this is helpful to everybody looking to get into all this stuff. Good luck, & have fun!!!

Glad I'm not the only Fedora user building android around here. I admit, I'm no good at java, but I have really only been focusing on kernel stuff for my device. Good luck to anyone using this.

XirXes said:
Glad I'm not the only Fedora user building android around here. I admit, I'm no good at java, but I have really only been focusing on kernel stuff for my device. Good luck to anyone using this.
Click to expand...
Click to collapse
I guess different people will have different experiences depending on what kind of knowledge they have. For me, I ran into trouble when I tried to port CyanogenMod to a different device on my own. I found that my knowledge was not quite up to par. Studying java is helping me in regards to both ROM development, & app development as well. It's just what I need because I also want to make games.

Very nice guide. I can tell you spent a lot of time putting this together. thank you!
I already had a mostly working Android SDK, and was successfully building kernels for my Ainol Elf2. However, I was never able to build the Elf2 ported version (by Christian Troy) of Cyanogen 10. Perhaps after starting over with my Java installs, this will work now. I have had the Android SDK installed for quite some time, but after v4.2, it would no longer update itself. Now it does.
Not that I want to use 4.2 on my Elf2. I hate they dropped Bluez and now USB Bluetooth dongles no longer work. That is a show stopper for my Elf2. However, my newly purchased Samsung GS3 might benefit nicely. I plan on starting to build a new kernel for this tonight.
BTW, I am still on Fedora 14 32bit, because I also hate Gnome 3 and the latest KDE's as well. My F14 is still kicking along just fine, with updates manually compiled by me.
Nice Job!

Thanks for sharing!! Good job!!

lexridge said:
Very nice guide. I can tell you spent a lot of time putting this together. thank you!
I already had a mostly working Android SDK, and was successfully building kernels for my Ainol Elf2. However, I was never able to build the Elf2 ported version (by Christian Troy) of Cyanogen 10. Perhaps after starting over with my Java installs, this will work now. I have had the Android SDK installed for quite some time, but after v4.2, it would no longer update itself. Now it does.
Not that I want to use 4.2 on my Elf2. I hate they dropped Bluez and now USB Bluetooth dongles no longer work. That is a show stopper for my Elf2. However, my newly purchased Samsung GS3 might benefit nicely. I plan on starting to build a new kernel for this tonight.
BTW, I am still on Fedora 14 32bit, because I also hate Gnome 3 and the latest KDE's as well. My F14 is still kicking along just fine, with updates manually compiled by me.
Nice Job!
Click to expand...
Click to collapse
Thanks!!! Yes, I did spend quite a bit of time on it. I always try to do everything as perfect as I can.
What a coincidence... It was messing around with my Ainol Novo7 Crystal tab that really pushed me into this journey of learning. I think that one & the Elfii are almost the same. That Christian Troy guy seems to be an absolute Linux master. I hope I can be as good as him someday.
I think many people should use Fedora. It may not be so easy for beginners, but the more people that help by writing helpful guides for different things, the easier it will be to transition to. It's really great. I even run it on my little Acer Aspire One A522 netbook with no problems.
Sent from my Galaxy Nexus using xda premium

PotatotreeSoft said:
Thanks for sharing!! Good job!!
Click to expand...
Click to collapse
Thank you!!! I hope it helps many people.
Sent from my Galaxy Nexus using xda premium

Thanks for "going the extra mile" (x10!) and taking the time to lay out such a well-organized procedure. Describing potential pitfalls is quite valuable as well. Sharing learning experiences helps everyone. And good luck with Java.

!!!WARNING!!! Here is what I mentioned all the way at the beginning. Please don't forget the most important thing of all: those damn hidden ".directory" files. Any time you change the folder views in Dolphin File Manager, it places a hidden ".directory" file in that folder. THESE HIDDEN FILES WILL DESTROY YOUR BUILD!!! I went through hell with this, trying to figure out what was going on. I always set up the Android folders to show in "details" view mode, so that they're easier to see. Every time I tried to build, it would build for 5 or 10 minutes, & then fail, citing errors in java. I eventually realized that the ".directory" files were the cause of all the problems.
Click to expand...
Click to collapse
You can disable this via:
Menu: Settings > Configure Dolphin > General > Behaviour and set it to common view for all folders. Found here

hi, im stuck ins this step
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/Android-Development/Builds/bin/repo
how can i make this work??
what im missing??
sorry and thanks

plmosqueda said:
hi, im stuck ins this step
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/Android-Development/Builds/bin/repo
how can i make this work??
what im missing??
sorry and thanks
Click to expand...
Click to collapse
Oh, hello. Sorry, I've been away for a very long time. It's cause I'm so busy trying to fix my screwed up life.
Were you still having trouble with this??? Does anything happen at all when you type the command??? I haven't done this in quite a long time now, but if I remember right, I think that this command looks like it doesn't do anything, but it really does. Be sure to check your folders for the repo command afterwards. Curl is a program you can use for downloading things. As long as you have it installed, it should at least tell you something when you type it in. By the way, nice Gameboy.

3ndymion218 said:
Oh, hello. Sorry, I've been away for a very long time. It's cause I'm so busy trying to fix my screwed up life.
Were you still having trouble with this??? Does anything happen at all when you type the command??? I haven't done this in quite a long time now, but if I remember right, I think that this command looks like it doesn't do anything, but it really does. Be sure to check your folders for the repo command afterwards. Curl is a program you can use for downloading things. As long as you have it installed, it should at least tell you something when you type it in. By the way, nice Gameboy.
Click to expand...
Click to collapse
Done XD, i was having ṕroblems with the global path. Well in now in Arch. All works fine, im trying to make a custon recovery for alcatel Ot 983

A bit late to the party but just found this great guide , too bad I didnt find it one year ago It took me almost a full day to figure all this out using Eclipse Kepler to dl the sdk and Nano to write new rules (had to find the rules...) ...
But all in all once you have done it one time seems to me the process is more straitfoward than with a comparable ubuntu system
this well written guide deserves more publicity!
Thanks!

Flashing Windows 10 Core to Raspberry PI 2

Hi guys!
As some of you might have seen it already: Microsoft has released an Insider Preview to the Raspberry PI 2.
Here are the instructions on how put the image on an SD card:
Source: http://ms-iot.github.io/content/win10/SetupRPI.htm
We have provided a utility to provision your SD card with the Windows 10 IoT Core Insider Preview. The following steps can only be executed on a system running Windows 10 (build 10069 or higher).
Follow these instructions to configure your SD card:
NOTE: you will need to follow these instructions on a physical Windows machine (and not a VM) because you need access to the SD card reader.
Please download the package "Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2" from the Microsoft Connect here. If you see a blank page or no downloads listed, please make sure you are signed into Microsoft Connect by looking at your login information at top right part of the screen. If you did not sign up for the Microsoft Connect program, please refer to the instructions in the "What you need" section above.
Make a local copy of the flash.ffu contained in the downloaded package "Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2".
Insert an SD card into your SD card reader.
Open an administrator command prompt and navigate to the folder containing your local flash.ffu.
Find the disk number that your SD card is on your computer. This will be used when the image is applied in the next step. To do this, you can use the diskpart utility. Run the following commands:
Code:
diskpart
Code:
list disk
Code:
exit
Using the administrator command prompt, apply the image to your SD card by running the following command (be sure to replace PhysicalDriveN with the value you found in the previous step, for example, if your SD card is disk number 3, use
Code:
/ApplyDrive:\\.\PhysicalDrive3
below):
Code:
dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
Click on the "Safely Remove Hardware" icon in your task tray and select your USB SD card reader to safely remove it from the system. Failing to do this can cause corruption of the image.
Click to expand...
Click to collapse
This is all good and fine, but most of us don't have a physical computer running Windows 10, so as the site mentions VMs don't have access to physical drives or the card reader, so you can't format and partition a physical disk (you can virtualize it and install it onto the virtual drive, create similar partitions on the physical drive and copy the contents of the virtual drive onto it, and copy the BCD of the virtual hard drive, but that's not 7what we want to do). To be able to flash the Windows Core image onto the SD card we need the latest version of a tool called dism.exe. The latest version of this tool is included with Windows 10 (that's why this manual says that you need Win 10 to do it), but it's also available as part of the Windows Assessment and Deployment Kit and luckliy enough Microsoft has made it available for everyone, so we don't need to scrap it with its dependant DLLs from Win 10.
To be able to flash the image from a computer that's running Windows 7 or higher (I haven't tried from anything below it) we need to first download and install Windows Assessment and Deployment Kit (ADK) RC for Windows 10.
Download page: https://msdn.microsoft.com/en-gb/windows/hardware/dn913721.aspx
Direct download: http://go.microsoft.com/fwlink/p/?LinkId=526740
When installing just install it normally, on the step "Select the features you want to change" tick only the box that says "Deployment Tools" and click Install
{
"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"
}
After the install open a CMD window as an Administrator (you have to type cmd to the start menu search and right click on the cmd.exe and click on run as administrator)
In CMD navigate to:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM
And follow the same steps as in the instructions on the MS website. (get the disk number, and flash it with dism.exe).
Code:
dism.exe /Apply-Image /ImageFile:"C:\Image\File\Location\flash.ffu" /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
(Don't forget to change C:\Image\File\Location to the location where you extracted the file from the downloaded ZIP file, also change the number of the physical drive)
On the MS site it also doesn't mentions that the smallest SD card that you can use is 4 GB, anything under that will generate a CRC error when trying to flash the image onto the SD card.
If you want to write your own apps for it (I assume that's why you have downloaded the preview, you'll need Visual Studio 2015)

Mostly a proof of concept that it runs on an ARM device, good thing most basic services are already running.
Have you seen any startup app around for testing?

There are a bunch of samples available on the MS-IOT Github:
https://github.com/ms-iot/samples
I Just bought the Raspberry PI 2 today and been messing on with it, coding seems fairly simple through visual studio, not too distant from Arduino. (im not much of a code expert though).
Im going to eventually use my Rpi to control my partially built Arduino Drone.

So, I know the Raspberry Pi 2 can run Windows 10, but anyone know if the UDOO can run it?

I haven't tried this yet, but you should be able to use USB passthrough to get access to card reader from a Windows 10 VM (at least in Virtualbox)

Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the http://www.rmprepusb.com/tutorials/getwaiktools/GetWaikTools.7z?attredirects=0&d=1
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.

I tried to follow your directions exactly but imagex doesn't seem to work, it just shows me all of the parameters. Could you offer any suggestions?
---------- Post added at 05:54 PM ---------- Previous post was at 05:46 PM ----------
Snaipersky;60701419
[* said:
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
[/LIST]
.
Click to expand...
Click to collapse
I added the number 1 after install.wim and it started working. Is that correct? I will report later if it works.

Snaipersky said:
Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the http://www.rmprepusb.com/tutorials/getwaiktools/GetWaikTools.7z?attredirects=0&d=1
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.
Click to expand...
Click to collapse
Following these directions, can one still flash windows 10 for use on the rpi2?

Nice Idea..
Will Try this

Snaipersky said:
Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.
Click to expand...
Click to collapse
You can choose which parts to install when installing ADK (in this case Deployement Tools which is only ~50 MB), so it will only download a minimal amount of data. I chose to do it this way as I run my Win 10 VM on ESXi and all the USB ports are disabled for security reasons.

Are those of us with a B+, I think it was called left out? I have one collecting dust that I would like to do something like this with.

help ASAP
viktorgino said:
Hi guys!
As some of you might have seen it already: Microsoft has released an Insider Preview to the Raspberry PI 2.
Here are the instructions on how put the image on an SD card:
Source: http://ms-iot.github.io/content/win10/SetupRPI.htm
This is all good and fine, but most of us don't have a physical computer running Windows 10, so as the site mentions VMs don't have access to physical drives or the card reader, so you can't format and partition a physical disk (you can virtualize it and install it onto the virtual drive, create similar partitions on the physical drive and copy the contents of the virtual drive onto it, and copy the BCD of the virtual hard drive, but that's not 7what we want to do). To be able to flash the Windows Core image onto the SD card we need the latest version of a tool called dism.exe. The latest version of this tool is included with Windows 10 (that's why this manual says that you need Win 10 to do it), but it's also available as part of the Windows Assessment and Deployment Kit and luckliy enough Microsoft has made it available for everyone, so we don't need to scrap it with its dependant DLLs from Win 10.
To be able to flash the image from a computer that's running Windows 7 or higher (I haven't tried from anything below it) we need to first download and install Windows Assessment and Deployment Kit (ADK) RC for Windows 10.
Download page: https://msdn.microsoft.com/en-gb/windows/hardware/dn913721.aspx
Direct download: http://go.microsoft.com/fwlink/p/?LinkId=526740
When installing just install it normally, on the step "Select the features you want to change" tick only the box that says "Deployment Tools" and click Install
After the install open a CMD window as an Administrator (you have to type cmd to the start menu search and right click on the cmd.exe and click on run as administrator)
In CMD navigate to:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM
And follow the same steps as in the instructions on the MS website. (get the disk number, and flash it with dism.exe).
Code:
dism.exe /Apply-Image /ImageFile:"C:\Image\File\Location\flash.ffu" /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
(Don't forget to change C:\Image\File\Location to the location where you extracted the file from the downloaded ZIP file, also change the number of the physical drive)
On the MS site it also doesn't mentions that the smallest SD card that you can use is 4 GB, anything under that will generate a CRC error when trying to flash the image onto the SD card.
If you want to write your own apps for it (I assume that's why you have downloaded the preview, you'll need Visual Studio 2015)
Click to expand...
Click to collapse
was following the method no. 1 and this was happening
"C:\Users\adi\Desktop>/ApplyDrive:\\.\PhysicalDrive1
The filename, directory name, or volume label syntax is incorrect."
what to dousing windows 10 ( still updating )

I will this as soon as possible

girron said:
Following these directions, can one still flash windows 10 for use on the rpi2?
Click to expand...
Click to collapse
No clue, haven't bothered with IOT. I'd recommend a sandboxed install of VS2015CE and building an image that way.
viktorgino said:
You can choose which parts to install when installing ADK (in this case Deployement Tools which is only ~50 MB), so it will only download a minimal amount of data. I chose to do it this way as I run my Win 10 VM on ESXi and all the USB ports are disabled for security reasons.
Click to expand...
Click to collapse
My problem is the ADK .iso is about as big as the W10 .iso. For those with poor connections, that could take quite a while. Why do both, when the imagex method is faster?

Snaipersky said:
My problem is the ADK .iso is about as big as the W10 .iso. For those with poor connections, that could take quite a while. Why do both, when the imagex method is faster?
Click to expand...
Click to collapse
For me ADK insalled from the Internet, the insall file that I downloaded was a 1.5 MB file.

I completely agree with @viktorgino

[Guide] Mac OsX Snow Leopard on Zenfone 2 with Qemu-KVM

I manage to run Mac OsX Snow Leopard on zenfone 2 (thanks to ycavan and his windows 10 guide). I create a guide to help people to test it, so lets begin:
https://www.youtube.com/watch?v=COV_l-f7FO0
Edit: This guide works for install windows too. Please see post # 7: https://forum.xda-developers.com/showpost.php?p=72426017&postcount=7
You must have a kernel with KVM function enabled. I personally use this rom
which include KVM kernel: https://forum.xda-developers.com/zenfone2/development/rom-rbr-v1-0-t3550544
Download OsX Snow Leopard Iatkos S3V2 iso image (torrent search iATKOS_S3_V2.zip)
Download and Install VirtualBox 4.3.40 (newer version doesnt work) on PC
Open it and create a Virtual Machine (VM) as following:
Name: Snow Leopard
Type: Mac OS X
Version: Mac Os X (64 bit).
Ram: in the top green right
Create a Virtual Hard Drive named SnowLeopard (vdi format, 10 gb or up recommended, fixed size)
Click on Configure:
On System untick disquette and untick enable efi
On Display....video memory full to the right
On Storage click on the cd image and select your iatkos.iso previously unzziped
Click ok and start VM (green arrow)
When a chameleon image appears press F8 and type: -x busratio=29 (if busratio does not work and get kernel panic, you must google your PC processor´s bus ratio and change this number with yours)
Installation now begin:
Select your language
click on Utilities and disk utility. click on your disk, click on erase and select Mac OSX extended(journaled) and click erase. Then close disk utility and continue with installation. Click on continue, right arrow, then click in your disk and select Customize:
On bootloader untick AsereBLN and tick chameleon v2 rc4
On bootloader option tick Graphics Enabler
On drivers, in main hardware tick on SATA/IDE, and tick network
Click OK and click on Install. At this point the OSX installation will begin.
Reboot the virtual machine and your OSX should start.(if you get a kernel panic for VodooHDA kext, you have to delete the kext with this guide: http://www.osxlatitude.com/remove-kext-from-single-user-mode/ it is located in system/library/extensions).
When you started the VM, go to safari and search for "Multibeast Snow Leopard Edition", and download it. Open it and tick EasyBeast Install, and above tick ShowallFiles on OSx86 software. Click install. Reboot your machine. Go to applications, open showallfiles and click Show. Go to finder, SnowLeopard disk, /Extra folder and in extensions folder delete ElliotForceLegacyRTC.kext
Open safari, go to https://github.com/kholia/OSX-KVM/blob/master/kexts/QemuUSBTablet-1.2.pkg and download QemuUSBTablet-1.2.pkg and install this package. Power off Virtual Machine.
In your pc go to C:\Users\(your user name)\VirtualBox VMs\SnowLeopard and copy SnowLeopard.vdi to your internal storage on phone (you must have at least 11 gb of free space).
On your phone:
Go to Play Store and install Linux Deploy. Open it and click on down arrow. Change this options: distribution (ubuntu), Suite (xenial), username (android), password (advr), enable init, enable mounts and in mount points add /sdcard , enable ssh, dont enable GUI. Back and in the three dots click on install. It can take over 20 minutes to complete. Click on start.
Download, unzip and copy my script attached in your internal storage (not microsd).
Download aSpice Free from Play Store. Open it and in connect type 127.0.0.1:5901. Dont click connect, only minimize app
Download Termius from Play Store. Open it and click bottom right to start a new session. Type localhost:5900 and click connect. User: android pass: advr
Once connected type the following:
sudo su
apt-get update
apt-get install qemu-kvm (type y if prompted)
cp /sdcard/osx.sh /
chmod a+x /osx.sh
/osx.sh
If you get "QEMU 2.5.0 monitor" you are right, if not, search for errors.
Open aSpice free and click connect. VOILA! You should see your osx Snow Leopard starting!
thanks to @ycavan and his guide: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299

Thank you very much.
Can I use your guide for installing windows, or not?

bahaa87 said:
Thank you very much.
Can I use your guide for installing windows, or not?
Click to expand...
Click to collapse
Yes, the concept is the same. I recommend you use this guide made by Ycavan: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299 to run Windows, i personally use it, but for ease to manage I create the images (windows, osx) in virtualbox first and copy them to my phone and ejecute in vdi format on qemu-kvm.

this is awsome!!! i'll be trying it tonight! any luck with the newer operating systems?

bonznumber1 said:
this is awsome!!! i'll be trying it tonight! any luck with the newer operating systems?
Click to expand...
Click to collapse
Newer OS should work, I installed SL because i have this iso file on hand, but i dont think there are any problem installing Yosemite, EC, Sierra, considering obviously it will consume more resources

alvavaca said:
Yes, the concept is the same. I recommend you use this guide made by Ycavan: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299 to run Windows, i personally use it, but for ease to manage I create the images (windows, osx) in virtualbox first and copy them to my phone and ejecute in vdi format on qemu-kvm.
Click to expand...
Click to collapse
I tried Ycavan guide but I don't understand all steps. And I don't find any video explain it. So I want to try another guide to install windows in my phone, because I need it very much.

bahaa87 said:
I tried Ycavan guide but I don't understand all steps. And I don't find any video explain it. So I want to try another guide to install windows in my phone, because I need it very much.
Click to expand...
Click to collapse
My guide works for installing Windows too. Instead of installing mac osX in virtualbox you must install windows (with any iso installer image) and create a disk (vdi) called windows (no matter which version is, 7, 8, 10) and use this script instead of the other. The other steps are the same, only continue from "On the phone" part. Obviously you must copy the script attached on this post instead the other and to start windows you must run this on termius (type one by one and press enter):
sudo su
apt-get update
apt-get install qemu-kvm (it take a while) type "y"
cp /sdcard/windows.sh /
chmod a+x /windows.sh
/windows.sh
My guide differs from Ycavan in that he installs the system on the phone and I create the image on the pc with virtualbox and then transfer it to the phone, but the concept is the same. I give you my scripts ready to use, Ycavan explains how to create the scripts (is hard to understand if you dont know the elementary concepts). Good luck.

alvavaca said:
My guide works for installing Windows too. Instead of installing mac osX in virtualbox you must install windows (with any iso installer image) and create a disk (vdi) called windows (no matter which version is, 7, 8, 10) and use this script instead of the other. The other steps are the same, only continue from "On the phone" part. Obviously you must copy the script attached on this post instead the other and to start windows you must run this on termius (type one by one and press enter):
sudo su
apt-get update
apt-get install qemu-kvm (it take a while) type "y"
cp /sdcard/windows.sh /
chmod a+x /windows.sh
/windows.sh
My guide differs from Ycavan in that he installs the system on the phone and I create the image on the pc with virtualbox and then transfer it to the phone, but the concept is the same. I give you my scripts ready to use, Ycavan explains how to create the scripts (is hard to understand if you dont know the elementary concepts). Good luck.
Click to expand...
Click to collapse
Thank you very much.
I'll try it tomorrow.

apt-get is a debian tool...not found on android...how did u manage to use it?

Apt-get is used in linux deploy...not in android system