Develop Bugs

Android Dev. How-To Guide: Compiling the Android/Linux kernel for the Epic Touch 4G

Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!

I'll take this...

and this...

One more...

Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium

Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium

Awesome!! tyvm!!

Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.

all u need now is a video tutorial

My man!!! Thank you for this!!
Sent from this phone

Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?

dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.

You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.

Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App

Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium

Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App

Great Guide!
Very informative and well put, Thank You.

thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk

Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!

obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!

[B2G][DEV-ONLY]Nigel meets the Fox

Project EpicB2G presents...
Nigel Meets the Fox (Boot 2 Gecko Kernel)
This is not an Android kernel. If that's what you're looking for, move along.
​
What is Boot 2 Gecko? If you have to ask yourself what is Boot 2 Gecko, then read up on it HERE. If you still don't understand, then this thread isn't for you.
About Boot 2 Gecko:
Firefox OS (project name: Boot to Gecko also known as B2G) is an open source operating system for smartphones and tablet computers being developed by Mozilla. It is an implementation of letting HTML5 applications integrate the device's hardware directly by using JavaScript. It has been demonstrated on Android-compatible smartphones. Boot 2 Gecko is HTML5 based and runs on top of a Android base system, BUT the kernel will not be able to boot android, just Boot 2 Gecko. ONLY USE WHEN A BOOT 2 GECKO ROM IS AVAILABLE!
This kernel was made available so future developers of Boot 2 Gecko can have a pre-compiled kernel for the operating system. For compiling instructions, see post #2.
WARNING!
This is a BOOT 2 GECKO KERNEL. DO NOT USE ON ANY ANDROID ROMS.​
Want to help contribute to the development of Boot 2 Gecko? Checkout the source HERE!
Download Nigel meets Fox (Boot 2 Gecko Kernel):
By clicking the link below you agree that you are flashing this kernel at your own risk. Neither myself, Project EpicB2G, nor anyone but yourself are responsible for any problems that may occur before, during or after flashing this kernel. You also agree that this kernel is to be flashed ONLY on the Sprint Galaxy S II Epic 4G Touch!
I agree to the terms and conditions set forth by XDA and Nigel...

# Boot to Gecko (B2G)
Boot to Gecko aims to create a complete, standalone operating system for the open web.
You can read more about B2G here:
http://wiki.mozilla.org/B2G
and talk to us on IRC:
#B2G on irc.mozilla.org
## Prerequisites
### Linux
* A 64 bit linux distro
* See http://source.android.com/source/initializing.html on configuring USB access.
* 20GB of free disk space
* autoconf-2.13
* git
* ccache
* gcc/g++ __4.6.3 or older__
* bison
* flex
* 32bit ncurses
* 32bit zlib
* make
Additionally, if you're building the emulator, you probably need the the Mesa
implementation of OpenGL. On Ubuntu, this is the __libgl1-mesa-dev__ package.
Ubuntu 12.10 ships with gcc 4.7 by default, which causes build errors pretty
early in the process. To use gcc 4.6, edit .userconfig and add
export CC=gcc-4.6
export CXX=g++-4.6
Of course, you'll need the g++-4.6 package installed.
### OSX
* XCode
* 20GB of free space
* homebrew
* git (if not using XCode 4)
* gpg
* ccache
* autoconf-2.13 - brew install https://raw.github.com/Homebrew/homebrew-versions/master/autoconf213.rb
## Fetch the source code
To build Boot 2 Gecko for the D710, you will have to fetch a custom source code from Nigel's GitHub, or your own if you forked it.
To begin type:
mkdir -p firefoxos
cd firefoxos
git clone git://github.com/EpicB2G/B2G.git
Once the source is present on your drive, make sure you have the B2G folder and type:
cd B2G
Now you're ready for part two!
## Configure
Run config.sh to get a list of supported devices:
./config.sh
And then run config.sh for the device you want to build for:
./config.sh d710
### Udev Permissions
If you get "error: insufficient permissions for device"...
Obtain ID of device manufacturer (first 4 hexidecimal digits before colon):
$ lsusb
Add a line to /etc/udev/rules.d/android.rules (replacing XXXX with 4 digit ID):
SUBSYSTEM=="usb", ATTRS{idVendor}=="XXXX", MODE="0666"
Restart udev before re-plugging your device for it to be detected:
$ sudo service udev restart
Re-run configure:
./config.sh d710
### Building against a custom Gecko
It can sometimes be useful to build against a different Gecko than the one specified in the manifest, e.g. a mozilla-central checkout that has some patches applied. To do so, edit .userconfig:
GECKO_PATH=/path/to/mozilla-central
GECKO_OBJDIR=/path/to/mozilla-central/objdir-gonk
## Build
Run build.sh or bld.sh to build B2G.
./build.sh
If you want to just build gecko or some other project, just specify it:
./build.sh gecko
## Flash/Install
Make sure your phone is plugged in with usb debugging enabled.
To flash everything on your phone:
./flash.sh
Please note that heimdall should be installed on your linux box.
To update gecko:
./flash.sh gecko
To update gaia:
./flash.sh gaia
## Update Repos
To update all repos:
git pull
./repo sync
To update a specific repo (eg, gaia):
./repo sync gaia
## Debug
To restart B2G and run B2G under gdb:
./run-gdb.sh
To attach gdb to a running B2G process:
./run-gdb.sh attach
## Test
To run the Marionette test suite on the emulator:
./test.sh
To run specific tests (individual files, directories, or ini files):
./test.sh gecko/dom/sms gecko/dom/battery/test/marionette/test_battery.py
Specify the full path if you're using a different Gecko repo:
./test.sh /path/to/mozilla-central/dom/battery/test/marionette/test_battery.py

Thanks, will give it a try.

Looks very interesting
Sent from my SPH-D710 using xda premium

My only question is...
Does this need the B2G ROM or does the kernel boot into a user interface?
The Mozilla website confused me.
Sent from my SPH-D710 using xda premium

Very interesting. I hope this goes better than the last OS port.

So do we still have to build b2g to install the os? Or will this ever be a flashable rom zip?
This is just quite different from everything I've come across so far.
*wearing flame retardant suit*
Sent from my SPH-D710 using xda premium

Anyone try this yet? I don't understand what it is but don't want to ask questions because that doesn't really seem accepted lol..
Sent from my SPH-D710 using Tapatalk 2

I'm thinking we need the ROM to go with this...
Sent from my SPH-D710 using xda premium

Mattix724 said:
I'm thinking we need the ROM to go with this...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Do a data and cache wipe and flash as a kernel.
Sent from my SPH-D710 using xda app-developers app

Some quick research. I had tried Firefox os on my PC.
Firefox OS is a new mobile operating system developed by Mozilla's Boot to Gecko (B2G) project. It uses a Linux kernel and boots into a Gecko-based runtime engine, which lets users run applications developed entirely using HTML, JavaScript, and other open web application APIs.
Click to expand...
Click to collapse
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS
How to install. https://developer.mozilla.org/en-US...o/Installing_Boot_to_Gecko_on_a_mobile_device
There is only 1 step which I am sure doesn't apply here. We already have boot.img from the op.
Am I correct op? We don't need to do anything such as
Code:
flash.sh
? And after we flash the boot.img in mobile Odin does phone boot into Firefox os?
Or this is just the kernel which allows one to flash Firefox os? But then where is the Firefox os? Lol so confused now.
Sent from my SPH-D710 using xda app-developers app

HTML5
I am assuming this is in response to Adobe not supporting android 4.0+ and the future platforms integrating html5. Just a guess...please tell me if I mis-interpreted.....

BluesRulez said:
Some quick research. I had tried Firefox os on my PC.
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS
How to install. https://developer.mozilla.org/en-US...o/Installing_Boot_to_Gecko_on_a_mobile_device
There is only 1 step which I am sure doesn't apply here. We already have boot.img from the op.
Am I correct op? We don't need to do anything such as
Code:
flash.sh
? And after we flash the boot.img in mobile Odin does phone boot into Firefox os?
Or this is just the kernel which allows one to flash Firefox os? But then where is the Firefox os? Lol so confused now.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Exactly my thoughts. Normally flashing a kernel does just that... Flashes a kernel. We would still need a compatible ROM.
I'm just not willing to be all brave with my phone since my laptop got stolen :/
Sent from my SPH-D710 using xda app-developers app

themisterwilson said:
Exactly my thoughts. Normally flashing a kernel does just that... Flashes a kernel. We would still need a compatible ROM.
I'm just not willing to be all brave with my phone since my laptop got stolen :/
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
True, I had mobile Odin loaded with boot.Img and was about to tap flash firmware and then I was like let me really look into this.
Sent from my SPH-D710 using xda app-developers app

Alright folks, a few things here...
I am going to close this up for a bit until the OP can come up with a better description for what this actually is as there is a ton of misinformation about it and it is as vague as it comes.
Removing the download link as well for the reasons stated above. I don't want people bricking their devices over this.
Last but not least, not having source makes this kernel non-GPL compliant as per GPL regulations on xda-developers.
OP, please contact this area's moderators (jayharper08) and let him know when things are ready from your end, so that the thread can be re-opened.
Thanks and thread closed.

I have spoken with Nigel (OP) and he will be updating the OP with more info on what exactly this is with better instructions. Link to source will be posted also.
Please keep it on topic.

The modified B2G repo is available here: https://github.com/EpicB2G/B2G . This is what is to be used, and I'll be updating the op.

Hmm, the OP should be GPL compliant now, and I think I've set enough warnings.
Nigel's back.

BluesRulez said:
Bump bump guy..
I get you are excited but that's just wrong.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
And against the rules. Please don't do that.
Sent from mALL GLORY TO THE HYPNOTOAD!!

jayharper08 said:
Please keep it on topic.
Click to expand...
Click to collapse
I don't believe "bumps" are on topic............. I've already asked once. Next time there won't be a "please" in front of my statement.

[ROM] Ubuntu Touch Preview [02/27: Alpha Update #1]

** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Kindle Fire 1st Gen and see for yourself.
CHANGES:
[02/27] Fixed the UI DPI settings. Needs to re-flash following the instructions below.
Instructions [CHANGED 02/27]:
1. Make a Titanium Backup and/or backup in recovery of your current Android. This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Kindle Fire 1st=Gen Mini-Android base for Ubuntu Touch and place it on your device:
[02/27] http://goo.im/devs/Hashcode/otter/ubuntu-phablet/phablet-20130227-otter.zip
md5sum: 4584b054391fe744230d9fd28686c37c
3. DUE TO OUR DATA PARTITION SIZE WE HAVE SPECIAL INSTRUCTIONS FOR PLACING THE UBUNTU TOUCH ROOTFS ON OUR DEVICE:
3a. Download a custom Ubuntu Touch Rootfs Installer ZIP:
http://goo.im/devs/Hashcode/otter/ubuntu-phablet/ubuntu-rootfs-installer.zip
3b. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
3c. On your PC extract open the Ubuntu Touch Preview Filesystem .zip and extract the *.tar.gz file inside
(currently called: manhattan-quantal-armhf-tar-20130227-1.tar.gz)
3d. rename this to: ubuntu-rootfs.tar.gz and place it at the root of /sdcard on the Kindle (not in any subdirectories)
4. Reboot into recovery.
4a. Wipe system and Factory Reset (wipes data/cache).
IMPORTANT:
4b. Install the ubuntu-rootfs-installer.zip FIRST (this actually uses the ubuntu-rootfs.tar.gz file we placed on the /sdcard), and then the phablet-2013xxxx-otter.zip SECOND.
5. Reboot and Enjoy
NOTE: The preview comes pre-loaded with several users in the login screen and they have data to browse around with. Move to the "Guest" account and tap on area where it tells you to login.
WHAT WORKS:
Display
Touch screen
WHAT DOESN'T WORK:
** OVER TIME YOU WILL RUN OUT OF MEMORY AND THE DEVICE BECOMES TERRIBLY SLUGGISH. THIS IS DUE TO OUR 512MB RAM AND HOPEFULLY THIS IS FIXED AS TIME GOES ON BY CANONICAL **
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
[FIXED 02/27] Need to adjust the GRID_UNIT_PX in /home/phablet/.bashrc to be slightly smaller so that the on-screen keyboard fits correctly
Oddly no WIFI yet. Still troubleshooting.
No sound
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above for the Kindle Fire)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch

RESERVED

The data extract is around 900MB. So plan accordingly Normally the 500MB internal .tar.gz file is extracted to /data and then extracted out from there, but we have to avoid this. Hence the longer rootfs install instructions.

Awesome work Hashcode! I'll be installing this and testing when I get home from work. Since it's CM based I assume ADB shell and logcat will work? I'm familiar with Linux so I've been looking forward to this.

Awesome. @HashCode- you still amaze me every time I see you post! Great job! And for step three is it a,b or c. Or a, b and c?
Edit: never mind I was confused. Thanks again.

After messing around for a bit I went back to Android. Its actually pretty smooth. Way better than I thought. Once WiFi and rotation get fixed I'll probably use it more. But it is what it is, a Preview. Great job Hash! Hope you can keep this updated!

Thank you x 1000000! Nice work, Keep it up!

Hashcode said:
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Kindle Fire 1st Gen and see for yourself.
Click to expand...
Click to collapse
How much memory does this take on the SDCARD? Currently I am dualbooting, and can I dualboot this and stock MoDaCo?

Will this work with this
http://forum.xda-developers.com/showthread.php?t=1615093
Sent from my DROID2 GLOBAL using xda premium

Currently I would not suggest dual booting this. It should work tho. But if you read, there is memory management issues and it will become sluggish. Extremely. And it isn't even finished, there is a lot of issues. But once they get worked out, I'm going try to dualboot it.

Ichigo said:
Please stop asking about dual booting. He already said that we have a longer rootfs install instructions to avoid it extracting to the data partition and then extracting the files from there. Everything works fine when dual booting. It's just as smooth. The only thing that may make it buggy is lack of cpu.
Click to expand...
Click to collapse
Sorry for spamming the thread.
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!

greezal said:
Will this work with this
http://forum.xda-developers.com/showthread.php?t=1615093
Sent from my DROID2 GLOBAL using xda premium
Click to expand...
Click to collapse
You could repartition for a larger data, but its memory issues that concern me currently.
Sent from my DROID RAZR HD using Tapatalk 2

Hashcode said:
You could repartition for a larger data, but its memory issues that concern me currently.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
So is memory management is first priority?

Tried it out
Sure does scroll nice! :laugh: Seriously, it does have a very pretty interface, which might be highly functional. Kinda like the using the original germ of an idea that was used in the original Kindle but all grown up. Can't wait to be able to do something useful with it.
Thanks Hashcode. Always fun to try these things. Instructions were spot on.
Now lets see if I can restore using the today's update to TWRP. I needed to test it anyway.

Awesome, will try this later. There still seems more development to come, will test when WIFI is fixed. I have expected this to come, I am more excited about FireFox OS though.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
Does anybody have any screenshots of this? Would like to see the Preview.
Sent from my Nexus 7 using xda app-developers app

Difference between 2/27 & 2/28 Builds
Out of curiosity, what's the difference between the two builds?

DarthVesh said:
Out of curiosity, what's the difference between the two builds?
Click to expand...
Click to collapse
The fact that there is only one build

Haha well I looked in the goo.im folder and one is dated for 2/27 & the other for 2/28..so I can assume they're the same? Lol
Sent from my SGH-I897 using xda app-developers app

Oh I sorry I didn't check the goo.im folder only the First post. So I don't know, try it and see what you see?

DarthVesh said:
Haha well I looked in the goo.im folder and one is dated for 2/27 & the other for 2/28..so I can assume they're the same? Lol
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
So see any major diffs?
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!

[Q] chroot Ubuntu on Nexus 7 (2013)

Not sure if anyone is interested or not but I have a chrooted Ubuntu 12.04 and Ubuntu 13.10 on my N7 running.
If anyone is interested I can post the steps and scripts I used, so you can do it yourself, and learn as you do it which is fun lol.
Most of the information is available via google searches however some things are not mentioned.
I have almost got LXDE running in the chroot without vnc, however not fully.
The problem I am having is when I startx or xinit /usr/bin/lxsession it displays a blank screen. When I kill the process, the LXDE background displays with a cursor. Not sure why it waits to display when I kill the process kind of weird.
Anyways thoughts, comments, constructive criticism.

photo of the adb screen launching startx img1.jpg
photo of the actual N7 screen img2.jpg

I guess there is a guide already from what I read.
No need for a guide unless someone wants to try making their own Ubuntu chroot. Then you will have the ability to make you own image size etc.
If anyone is interested or wants to do this post here and I will provide the steps.
And assist with scripts and what not.
By no means did I come up with this on my own, however many guides have scripts that don't work etc due to your version on android or device etc.
Sent from my Galaxy Nexus using xda app-developers app

I'm using the guide in the General Section to use Kali PwnPad with my N7. I was using Backtrack with my 2012 and just bought a 2013 and very happy so far that everything works with Kali but with a better performance!
Wifi USB host was the main concern and it works great.
Nice job you have done too can you send me or share your chroot script please?

djxtabay said:
I'm using the guide in the General Section to use Kali PwnPad with my N7. I was using Backtrack with my 2012 and just bought a 2013 and very happy so far that everything works with Kali but with a better performance!
Wifi USB host was the main concern and it works great.
Nice job you have done too can you send me or share your chroot script please?
Click to expand...
Click to collapse
yes, do you need startup scripts or launch scripts for vnc and x
or just the chroot script to get into linux?

UPDATE
I made scripts which will allow the creation of the linux image right on the device itself.
It downloads approximately 200 megs for the packages, no more need to download huge image files...
Right now ubuntu works for sure testing others...

userdelroot said:
I made scripts which will allow the creation of the linux image right on the device itself.
It downloads approximately 200 megs for the packages, no more need to download huge image files...
Right now ubuntu works for sure testing others...
Click to expand...
Click to collapse
Great job! Could you share those somewhere (I'm interested in running other distributions e.g. Fedora and Mer)

vrutkovs said:
Great job! Could you share those somewhere (I'm interested in running other distributions e.g. Fedora and Mer)
Click to expand...
Click to collapse
of course, but need to finish scripts and work out some bugs.

userdelroot said:
of course, but need to finish scripts and work out some bugs.
Click to expand...
Click to collapse
Hey, any news on this?

vrutkovs said:
Hey, any news on this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2627255

[SCRIPT FOR STOCK] AutoScripts

AUTOSCRIPTS​
Hi Everybody!
That's my first work for the Moto X Play so I hope You'll appreciate it.
It's simply an automatic flash script, just in case You won't have to remember all these shi*ty codes.
It's personally created and tested by me, so I'm sure it works, but I don't assume any responsibility for damaged devices.
!!REMEMBER! I DON'T PROVIDE ANY STOCK ROM!!
My script (as you'll see) works both with Ubuntu (and derivates), Fedora (yes, both with dnf and yum installer) and Windows.
If you have any question/suggest feel free to post it here and if I helped you feel free (too) to hit thank and maybe buy me a coca (I don't really like alchoholic drinks).
HOW TO​1) Download it from MY GITHUB PAGE.
2) Put on your Home Folder (or anywhere You want).
3) Unzip it (You'll see a file called flash.sh, for linux users, and some files for windows users).
4) Open a terminal and cd the folder where you have saved flash.sh.
5) Copy the code below (for Linux) or simply double-click on flash.bat (for Windows. It doesn't request administrator privilegies).
Code:
$ chmod +x flash.sh
$ ./flash.sh
6) Follow the instructions on screen.
7) Enjoy.
BUGS​All the Scripts is tested personally by me before any upload so I'm sure they'll work. Anyway if you encounter any problems please post it in bug's tab HERE!
VERSIONS​AutoScript Linux
Fixed Wipe and NoWipe options.
Added support for ArchLinux (both with pacman and yaourt)
BugFix
NEW:
1) Added sperimental support for Gentoo linux and other OS's with emerge (I haven't Gentoo so I don't assure it works as expected!)
2) One script for rule 'em all!
AutoScript Windows
Added a script for logcat.
Cleaned the codes on flash.bat.
Added ability to exit the script on any question simply press K.
Fix some bugs and clean code.
Added ability to relock the device
BugFix
F.A.Q.​1) Why it doesn't work with device XYZ?
It's because my AutoScripts is developed only for Moto X Play.
2) The Scripts have only formatted my device. You piece of sh*t!!1!11!
Have you downloaded the ROM and put the files on the Flash's folder? You can find it HERE.
3) When do you upload an update?
I'll do it as soon as possible. Don't hassle me with that unuseful quest please.
4) Thank man, your work is fantastic!
Please hit thank button, don't write a post for that.
5) I've read your work and the codes is fuc*ing ugly and long.
I know. If you have a suggestion please tell me and I'll see if i can do anything.
XDA:DevDB Information
AutoScripts, ROM for the Moto X Play
Contributors
ScardracS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Stock
Version Information
Status: Stable
Stable Release Date: 2016-06-19
Created 2016-06-19
Last Updated 2019-03-05

Reserved

Is this rooted? And bloats removed.?
Sent from my XT1562 using Tapatalk

manan001 said:
Is this rooted? And bloats removed.?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
It's just a helper script to install stock

manan001 said:
Is this rooted? And bloats removed.?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
No, It isn't. I could ask to @GtrCraft if I can use his rooted version.

ScardracS said:
No, It isn't. I could ask to @GtrCraft if I can use his rooted version.
Click to expand...
Click to collapse
Yeah go ahead, also can you make a script without the userdata wipe and tell us which stock version is present in the zip (variant, build number etc.)?
Sent from my XT1562 using XDA Labs

Windows script
I made a Windows version of the script.
Copy the Firmware into the folder
Run flash file and follow the instructions.
Download: https://drive.google.com/file/d/0B4ryT_zqtaHWWFhldFpfNFBjVDA/view?usp=sharing

It's possible to add support to dual sim xt..63 br?
Thx! Nice idea.

GtrCraft said:
Yeah go ahead, also can you make a script without the userdata wipe and tell us which stock version is present in the zip (variant, build number etc.)?
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Thanks. The build is based on MPD24.107-52 for the XT1562

axxx007xxxz said:
I made a Windows version of the script.
Copy the Firmware into the folder
Run flash file and follow the instructions.
Download: https://drive.google.com/file/d/0B4ryT_zqtaHWWFhldFpfNFBjVDA/view?usp=sharing
Click to expand...
Click to collapse
Thanks man! I'll add it to my main script (with proper credits )

I'm uploading the V2 with the script for Windows, thanks to @axxx007xxxz, (I haven't tested if it work 'cause I haven't Windows).
In the script for linux I've also added the possibility to delete (or not) userdata
P.S.
For XT1563 and rooted version expect tomorrow 'cause I'm too busy, sorry

i need unlock the bootloader?

Sorry for my loong absence but I was really busy on the real world. I'm working on a few bugs of my AutoScript (I was missing some codes). I hope @axxx007xxxz will update his Script for Windows soon.

Tried this yesterday, works like a charm, I used the windows script.

@ismatab this script is for people who have unlocked their phone and want to return to stock build. If you have your bootloader locked you can't flash it

Uploading new build. Now you don't need to put your device in bootloader mode before plug it to the PC 'cause the script do it automatically

[ROM][STOCK][SCRIPT] Stock Rom with AutoFlash Script
ScardracS said:
Uploading new build. Now you don't need to put your device in bootloader mode before plug it to the PC 'cause the script do it automatically
Click to expand...
Click to collapse
I'll upload Windows script soon, sorry for the delay.

So right now i have CM13 installed, but would like to go back to stock. I am rooted and have an european version (dual Sim) I am on windows.
If i use the windows script, i just have to follow the instruction ? do i need to download a stock rom first ? is (/XT1562_LUX_RETEU_6.0.1_MPD24.107-52_cid7) the good one ?
It doesnt matter if i loose my data. i would prefer to actually as i want a fresh install.
Will i keep my phone rooted ?
Thanks for the tool and your answers !
Cheers

QuentinPdeB said:
So right now i have CM13 installed, but would like to go back to stock. I am rooted and have an european version (dual Sim) I am on windows.
If i use the windows script, i just have to follow the instruction ? do i need to download a stock rom first ? is (/XT1562_LUX_RETEU_6.0.1_MPD24.107-52_cid7) the good one ?
It doesnt matter if i loose my data. i would prefer to actually as i want a fresh install.
Will i keep my phone rooted ?
Thanks for the tool and your answers !
Cheers
Click to expand...
Click to collapse
If you open Download's tab you'll se a file called Stock vX.zip. It contains the stock rom plus the file script.bat. You have simply to double click on it.

For the ROM 6 .0.1 it most be added the system.img_sparsechunk.9 line to the script, also the Stock vX.zip dont say if is compatible with XT1563, the Windows.zip in other comments said this, also, in Windows Zip the ADB is missing.
Anyway, thaks for the script