Related
I was wondering if anyone has got Ubuntu working on the Milestone X2 using the Ubuntu.sh script? I suppose the question would be does the MX2 even support loop devices? I have been looking over the file system, and have found the directories "Loop1 - Loop7", yet the file structure is different. I'M actually looking into altering the script, however, even with a custom script, would it even work? because of Motorola's locked down bootloader, and fort Knox phone design.
Sent from my Milestone X2 using XDA
[email protected]:/#
Nevermind.
AndroidVNC
I'm having trouble getting AndroidVNC to connect. I've setup VNC to connect to localhost with password ubuntu on port 5900, and it says it can't connect to 127.0.0.1:5900. How can I resolve this? Also, when I go into [email protected] and type apt-get update, it says some packages can't be installed, and its the same when I run apt-get install tightvncserver. If anyone is obliged to help it would be most appreciated.
Nevermind, I have AVNC working. I had the wrong ubuntu image..... LOL...now I feel like a fool.
Please insert smack here.
Sent from my Milestone X2 using XDA
Moderator please delete this post. Thanks.
Sent from my Milestone X2 using xda premium
It's time. As offered previously for the Nook Color and HP Touchpad...
A Build CM9-for-NookTablet Walkthrough
What is this?
This document provides instructions for developers to build a complete Cyanogenmod 9 update.zip for the Nook Tablet aka "acclaim" (and more theoretically the newer 512MB model, aka "elation") from source code. The instructions require a Linux computer and appropriate tools (discussed below).
It is important to emphasize that CM9 is a work in progress and if you try it you will be building/using something in mid-development. Things may break and/or not work at any time. Read below, the build instructions, and the relevant licenses for additional info and disclaimers.
Hopefully, for those developers who are interested and willing to take the risks, this can be a fun and educational experiment. And hopefully more developers will help chrmhoffman, kuzma30, mik_os, and others improve CM and the 3.0 kernel.
So does this build use the new, experimental 3.0 kernel then?
Update: At first, I mentioned that 2.6.35 was also supported, but apparently this will require additional files that aren't currently installed. So for now, yes, it uses the 3.0 kernel, which may not be compatible with the newer 512MB NTs. Although it is not confirmed one way or the other, as it has not been tested on these devices.
The configuration uses the experimental 3.0 kernel, which is built on-the-fly from the latest source code.
Unless you really want to take some risks, if you have a newer-model 8GB/512MB Nook Tablet (aka "elation"), the 3.0 kernel build is not for you...yet! It may boot, it may not. It has not been tested by any of the developers with that device, and as of this writing there are known kernel issues with the 512MB. (So actually, this is a good opportunity for developers to try it and contribute.) The 3.0 kernel development thread has more on this.
Any further discussion below assumes the 3.0 configuration, as the 2.6.35 branch isn't as up-to-date and isn't really being maintained. 3.0 is the future!
These instructions are for Linux. How do I build on Windows/Mac/etc?
If you have Mac or Windows or something else, you may consider installing a virtual machine such VirtualBox (which is free). Then run Linux, say a Ubuntu distribution, as a guest from your host computer. This allows you to "sandbox" your development environment, and gives an opportunity to learn about Linux with actual hands-on experience, all without reformatting your computer...
CM9 can also be built on Mac natively, either in Snow Leopard or Lion. Instructions for building (CM7) on a Mac can be found on the CyanogenMod wiki.
A few modifications need to be made to those instructions for CM9 & Lion, but such instructions aren't hard to find.
Will my build actually be usable?
CM9 (and the acclaim port) is in active development, and when you do a build from the latest source, you are using a bleeding-edge build of whatever happens to be in the repositories at the time. There is no guarantee it will work in any capacity. It may actually cause terrible damage. So only try at your own risk, and assume responsibility for your actions. If you find a bug, help fix it.
It is critical that you understand the risks before trying this and fully back up your system before trying any build. It is equally important to have a bootable SD standing by so that you can restore your device to a known good version if something goes terribly wrong, which may actually happen. Hopelessly staring at a non-booting device is never fun. There are other threads about recovering hosed acclaim systems, so I will leave you to finding and understanding them and preparing yourself for solving such problems. You should always assume the worst will happen, so be prepared.
Speaking personally, I don't have either model of NT and have never run CM9 on one, so can not attest to its usability per se. You should consider this a work in progress full-of-bugs until told otherwise.
Which bootloader is this using?
Cyanoboot, based on u-boot. The full github repo w/history (rather than raw files) is now available as well. Special credit to bauwks for fixing the locked bootloader design flaw.
Will this build result in a working update.zip suitable for use with ClockWorkMod recovery?
The build process has been modified to generate a fully flashable update.zip, but, as, with everything else, nothing is guaranteed.
Does this create a build for SD Card or for EMMC (internal storage)?
EMMC.
I'm stuck! I've been at it for hours. Something isn't working. Where can I get help?
If you have never built an operating system before-- this may be a good way to learn, provided you accept the risks and consequences of trying. This and other forum threads may be a good place to look for help. Also try IRC.
You are also able to leave comments in the walkthrough document itself. If you have a tip that might help others, post it there. If I get a chance, I'll take the best of them and incorporate it into the doc.
Does this build ClockworkMod recovery too?
It should. Check the $OUT directory for two files-- recovery.img and recovery.img.sdcard. The recovery.img file is (hopefully) flashable via fastboot:
fastboot flash recovery recovery.img
The recovery.img.sdcard can be renamed to recovery.img and put on your sdcard.
Can I build twrp2 instead of ClockWorkMod?
TWRP2, in case you're not familiar with it, is an alternative recovery image created by Team Win, particularly user dees_troy. It can be used for flashing update.zip files and making/restoring backups, among other things.st
The 3.0 build configuration currently contains the needed settings for a twrp build. You will just need to replace the ~/android/system/bootable/recovery repo with twrp's source code. You can do this by adding the following lines to your local_manifest.xml file:
<remove-project name="CyanogenMod/android_bootable_recovery"/>
<project name="TeamWin/Team-Win-Recovery-Project" path="bootable/recovery" remote="gh" revision="master" />
You can then repo sync (per the instructions) and then do this command to rebuild the recovery using twrp2.
mka recoveryimage
The recovery.img and recovery.img.sdcard files in $OUT should now contain the latest twrp2. (If it doesn't, try clearing out the recovery-related files in $OUT, including $OUT/obj/RECOVERY_EXECUTABLES)
Please direct twrp2-related questions and solutions to the twrp2 thread, not here.
Who do I thank?
Thanks to chrmhoffmann, mik_os, kuzma30, cyanogen, arcee, nemith, Texas Instruments, Barnes & Noble, and all the other devs, testers, and contributors, of which there are many. And special thank to bauwks, who made this all possible.
For this walkthrough in particular, big thanks to chrmhoffmann as well as eyeballer for testing. Everyone-- go find a thread by these people and thank them.
Who do I blame?
Yourself. Only yourself.
To whom do I donate?
Not to me. You can donate to any of the above if you feel like it. I do suggest considering a donation to the Electronic Frontier Foundation, who among other noble activities are fighting to keep "jailbreaking" and its Android phone and tablet equivalents legal. Your Android devices are full-fledged computers. Don't let corporate or government special interests take away the right to mess with your own possessions as you wish.
Finally, good luck. We're all counting on you. If and when you have problems, post them, and hopefully others will help find a solution.
Developers are needed. Enquire within.
-ft
(twitter)
-----
How To Build CM9 for Nook Tablet From Source
(Google Doc... or is it Google Drive now?)
And one more thing...
If I think of something to add, I'll put it here.
Good stuffs. I'll give it a try later in the week. I have everything set up. Going to be fun testing.
Im planning on doing this too. Thanks for making a guide, although I'll probably be in the IRC within 5 minutes of starting with questions
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Thank you very much for putting this together!
I am testing on an 8GB nook.
I can verify that the cwm and twrp2 recovery images boot with the 3.0 kernel, however CM9 fails to boot, it hangs on a blank screen with the backlight on and eventually just reboots. I am not able to get it to connect via usb to print logcat so I don't think it is getting very far.
Do you happen to have any instructions for tapping into the serial on these devices to see what is going on?
Also, with the new cwm it will not mount the sdcard through the menu. If I open a shell within cwm recovery I can mount it fine, except it is read-only.
In case it is useful, here is a dmesg from cwm:
http://pastebin.com/0fkyuSwe
arcon2600 said:
Also, with the new cwm it will not mount the sdcard through the menu. If I open a shell within cwm recovery I can mount it fine, except it is read-only.
In case it is useful, here is a dmesg from cwm:
http://pastebin.com/0fkyuSwe
Click to expand...
Click to collapse
Ah, this is very interesting! It's similar behavior to twrp.. a mounting issue with sdcard... wonder if this means the kernel is somehow not letting it mount, or if the problem is with recovery.fstab...
New patch, there shouldn't be a gpio_wp pin assigned to begin with...
Also, this is tested on my 8GB, I don't have a 16GB to test with.
diff --git a/arch/arm/mach-omap2/board-nooktablet.c b/arch/arm/mach-omap2/board-nooktablet.c
index de38b5c..a10dd93 100644
--- a/arch/arm/mach-omap2/board-nooktablet.c
+++ b/arch/arm/mach-omap2/board-nooktablet.c
@@ -684,7 +684,7 @@ static struct omap2_hsmmc_info mmc[] = {
.mmc = 1,
.caps = MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA | MMC_CAP_1_8V_DDR,
// .gpio_cd = -EINVAL,
- .gpio_wp = 4,
+ .gpio_wp = -EINVAL,
.nonremovable = false,
// .no_off_init = true,
#ifdef CONFIG_PM_RUNTIME
Build environment ready but cannot use repo command
HI! i would love to build a zip with the new kernel but i cannot use the repo command in the terminal in Linux Mint latest build. I have downloaded Android SDK and all the required build libraries and set up all the directories. i have the NTsparkkernel folder in the android directory. Could anyone offer some advice on how to apt-get (the REPO module) so I can build the zip. Thank you for your time. Bruce
about repo
C64assembly said:
HI! i would love to build a zip with the new kernel but i cannot use the repo command in the terminal in Linux Mint latest build. I have downloaded Android SDK and all the required build libraries and set up all the directories. i have the NTsparkkernel folder in the android directory. Could anyone offer some advice on how to apt-get (the REPO module) so I can build the zip. Thank you for your time. Bruce
Click to expand...
Click to collapse
The repo command is actually something you get from Google. It's not in the apt-get repositories.
To install the repo script:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
The repo binary will be in ~/bin and you can add this to your path if you like.
Confirmed by chrmhoffmann and committed. Thank you!
Thank you for this guide. I've compiled stuff before, but built my first Android from source last night. Although the build from that time has random reboots (the nature of the beast).
I'll be building quite a bit I think
Damn see I'm just porting right now I wanna build from source but my PC isn't Linux friendly yet I'm waiting on a tb internal so I can set up and learn this but it just looks so complicated and idk why. I feel once I learn it probably be easy as hell. Thanks Fattire
__________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Danrarbc said:
Thank you for this guide. I've compiled stuff before, but built my first Android from source last night. Although the build from that time has random reboots (the nature of the beast).
I'll be building quite a bit I think
Click to expand...
Click to collapse
Hey congrats and welcome to the club!
Cannot Make the bacon...
Hey Fattire! Thank you for your guide. I was able to finally download the source for cm9 and add the 3.0 kernel repository. I have everything in one folder. I am new to Linux and had to add a Path command to get Repo Sync to work correctly. Once I got the Repos I ran into another problem trying to issue command cd ~/android/system/vendor/cm , then enter “./get-prebuilts”. The Make Bacon and or Croot <enter> brunch acclaim does nothing either. It seems I am missing somthing here. Maybe a different distro of Linux besides Mint would work better for me... getting close to building (i hope). Thanks!
I have to issue PATH=~/bin:$PATH every time I repo sync.
C64assembly said:
Hey Fattire! Thank you for your guide. I was able to finally download the source for cm9 and add the 3.0 kernel repository. I have everything in one folder. I am new to Linux and had to add a Path command to get Repo Sync to work correctly. Once I got the Repos I ran into another problem trying to issue command cd ~/android/system/vendor/cm , then enter “./get-prebuilts”. The Make Bacon and or Croot <enter> brunch acclaim does nothing either. It seems I am missing somthing here. Maybe a different distro of Linux besides Mint would work better for me... getting close to building (i hope). Thanks!
Click to expand...
Click to collapse
I use Ubuntu here I started with 10.04 LTS since it was the the build used and supported by Googles build instructions. Yous should still be able to do it though.
Did you initialize the build environment using ". build/envsetup.sh" at android/system (it looks like is the base of your source from your post)
Yes. Thank you for your advice KeithN. I am going to start from scratch. I might just put Ubuntu 10.04 on my comp tonight if I cannot get it to build properly.
I'm going for Ubuntu 12.04 command-line. If that doesn't go well, I'll go for 10.04 as well.
I built mine on 12.04 (Xubuntu, but that doesn't matter so much).
I added a debian sqeeze apt repository to get sun-java6-jdk, then used -f install when it complained because one of it's dependencies exists in Ubuntu but not that same version #. Commented out the repository after it installed so I don't get more debian packages on accident. For everything else I think it was just following the guide as-is.
C64assembly said:
I am new to Linux and had to add a Path command to get Repo Sync to work correctly.
Click to expand...
Click to collapse
Yes, I had recommended doing that. The PATH=$PATH:~/bin command will ensure that no matter what directory you type "repo", it'll know where to find the file.
C64assembly said:
Once I got the Repos I ran into another problem trying to issue command cd ~/android/system/vendor/cm , then enter “./get-prebuilts”. The Make Bacon and or Croot <enter> brunch acclaim does nothing either. It seems I am missing somthing here. Maybe a different distro of Linux besides Mint would work better for me... getting close to building (i hope). Thanks!
I have to issue PATH=~/bin:$PATH every time I repo sync.
Click to expand...
Click to collapse
Instead of entering it every time, you can add that PATH statement so that it's automatically invoked when you open a new Terminal window.
Just add the line to an "invisible" file (it's invisible because it starts with a period (.) and won't show up in a normal listing) called .bashrc in ~/.bashrc (the ~ is a shortcut for your home directory, or /home/youraccountname/). The hidden .bashrc file will probably exist already. Just add the statement to the end.
Keithn said:
Did you initialize the build environment using ". build/envsetup.sh" at android/system (it looks like is the base of your source from your post)
Click to expand...
Click to collapse
This is right. Try this:
$ cd ~/android/system
$ . build/envsetup.sh
(the $ represents the prompt and should not be typed. For the second command, it's literally a period followed by a space followed by build/envsetup.sh)
I am using the latest 12.04 ubuntu, fwiw.
I know this is for CM9, but any help would be appreciated (trying aokp). I had issues with the packaging of the .zip it looks like. I was able to build for my fascinate so I know the source will build. Any suggestions?
Output
Intro:
Ok, im sure you all want to get your hands dirty in development! Well we need more of that. So i decided to write a little guide on how to build your very own kernel from source using ubuntu.
NOTE- You need a computer running ubuntu! i use ubuntu 10.04 but any version should work fine.
Click to expand...
Click to collapse
Setting Up Your Build Environment:
Get required packages by using the following commands in a terminal window.
32bit and 64bit systems:
Code:
sudo apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
64bit only:
Code:
sudo apt-get install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
Click to expand...
Click to collapse
Making Working Directories:
Open new terminal window
Type:
Code:
mkdir android
Type:
Code:
cd android
Type:
Code:
mkdir kernel
Now you have the directories where we can put the source code into and build from.
Click to expand...
Click to collapse
Getting the Build Toolchain:
In already open terminal window type the following commands...
Type:
Code:
cd
Type:
Code:
cd android/kernel
Type:
Code:
mkdir toolchains
Now download the toolchain from HERE and extract into the "toolchains" folder that we just created.
Click to expand...
Click to collapse
Gathering The Source:
For this we are going to just grab a copy of sportsstar89's kernel source since he has it up on github. (yes, its the newly released ics kernel)
Open a new terminal window
Type:
Code:
cd android/kernel
Type:
Code:
git clone git://github.com/Sportsstar89/Amaze-ics-sense.git
Once the source has been cloned to your "android/kernel" directory, you should see a folder with the name "Amaze-ics-sense". Leave it named that or you will have to edit some of the commands to work.
Click to expand...
Click to collapse
Building The Kernel:
Now is the fun part, we are about to build your first kernel!!!
Open a new terminal window
Type:
Code:
cd android/kernel/Amaze-*
(the "*" saves us from typing so much)
Type:
Code:
export ARCH=arm
Type:
Code:
export CROSS_COMPILE=~/android/kernel/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
Type:
Code:
make sports_ruby_defconfig
Type:
Code:
make menuconfig
(make any changes you want... if you dont need to make changes, use arrow keys and enter key to select exit until you are back to the terminal.)
Type:
Code:
make -j4
Build will take a few minutes depending on the speed of your computer...
Click to expand...
Click to collapse
After Build Completes:
The build should complete without errors. If it did, you will need to find the "zimage" that the build generated.
It will be in- "/android/kernel/Amaze-ics-sense/arch/arm/boot"
Grab it and put it on your desktop for now...
Click to expand...
Click to collapse
Finishing Up the Kernel:
Now is the slightly tricky part for some... We will be using windows for this part of the tutorial.
Follow this to get Cygwin and Dsixda's Kitchen setup (thanks Dark Nightmare)
Once you have that setup, you will want to use cygwin to unpack and repack the boot.img.
First navigate to the cygwin install directory. then put any ics rom into the "original_update" folder. (it doesnt matter what rom, cause we dont need to keep the rom)
Next, open up the Cygwin bash shell and type the following commands.
Type:
Code:
1
Type:
Code:
y
(then change the name of the working folder to "WORKING_kernel")
Type:
Code:
2
(this will leave the updater-script in the rom alone so the process is quicker)
Now in the "WORKING_kernel" folder you will see a boot.img. That means everything is going good so far.
Now we want to unpack that boot.img so we can replace the zimage with the one we made earlier.
Type:
Code:
0
(for advanced options)
Type:
Code:
20
(for boot.img tools)
Type:
Code:
w
The boot.img is now unpacked into the "BOOT-EXTRACTED" folder. Take the zImage that we made earlier and put it in that folder, Replacing the old one. Then go back to the cygwin terminal.
Type:
Code:
b
(this will repack the boot.img with the new zImage inside)
CONGRATULATIONS!!! you have just build your first kernel! Now if you go back to the "WORKING_kernel" folder, you can take that boot.img out and flash it the same way you would any other boot.img.
Click to expand...
Click to collapse
Rebuilding:
If you decide to make changes to your kernel, make sure you start fresh with these commands.
Type:
Code:
cd
Type:
Code:
cd android/kernel/Amaze-ics-sense
Type:
Code:
make clean
If your build fails or you just want to make another build, but not from scratch just type this command.
Type:
Code:
make -j4
Click to expand...
Click to collapse
Flashing Methods:
Fastboot-
If you have fastboot setup, you can use the following command from a command prompt to flash the boot.img to your phone when in bootloader mode.
Code:
adb reboot bootloader
Code:
fastboot flash boot boot.img
Hasoon's Toolkit-
This is for the people who dont know how to use fastboot.
download the toolkit From Here
place it in the kernel folder.
Select "with this command" and press Flash kernel.
Click to expand...
Click to collapse
Credits:
Sportsstar89- for taking the time to give me pointers on how to build from source
Dark Nightmare- for making a how-to video on setting up the android kitchen
Hasoon- for having an epic toolkit
Everyone else who has to put up with me
Click to expand...
Click to collapse
has anyone try to build there own kernel yet?
It's fantastic, thanks man.
I'm youtube! Great guide by the way ziggy, +1.
This is awesome. I really appreciate this, but I feel like I'm just following instructions and not really learning anything. Even with the compile cm9 from source I felt the same way. I guess I just need to play around
Sent from my HTC_Amaze_4G using Tapatalk 2
EDIT: Is there a way to do the second part without Windows, still in ubuntu? I'd have to swap hard drives to get back on Windows.....long story.
Nshih422 said:
This is awesome. I really appreciate this, but I feel like I'm just following instructions and not really learning anything. Even with the compile cm9 from source I felt the same way. I guess I just need to play around
Sent from my HTC_Amaze_4G using Tapatalk 2
EDIT: Is there a way to do the second part without Windows, still in ubuntu? I'd have to swap hard drives to get back on Windows.....long story.
Click to expand...
Click to collapse
yea, just look up how to use the kitchen in linux.
Nshih422 said:
This is awesome. I really appreciate this, but I feel like I'm just following instructions and not really learning anything. Even with the compile cm9 from source I felt the same way. I guess I just need to play around
Sent from my HTC_Amaze_4G using Tapatalk 2
EDIT: Is there a way to do the second part without Windows, still in ubuntu? I'd have to swap hard drives to get back on Windows.....long story.
Click to expand...
Click to collapse
I was wondering why he switched to windows for that part.. for me cygwin install didn't work properly, but i MADE IT WORK.. just look up dsixda kitchen and follow the instructions for the ubuntu setup.
And note to anyone: installing ubuntu itself can be a *****, building a kernel is not nearly as intensive as compiling a whole rom from source - you can install ubuntu in a virtual machine and build in that, it will take a little longer, but it works just fine..
And to anyone who wants to learn, actually building the kernel isn't going to teach you as much as looking at the git commits and doing some Googling.. if you look in any of the threads where kernel discussion has been had, you can see a lot of useful info.
I suggest that the OP add a couple of notes about changes that can be made before the make command.. how to make those changes will be more educational that the process itself(tho it is helpful as hell, very well written!)
Sent from my HTC_Amaze_4G using xda app-developers app
Silentbtdeadly said:
I was wondering why he switched to windows for that part.. for me cygwin install didn't work properly, but i MADE IT WORK.. just look up dsixda kitchen and follow the instructions for the ubuntu setup.
And note to anyone: installing ubuntu itself can be a *****, building a kernel is not nearly as intensive as compiling a whole rom from source - you can install ubuntu in a virtual machine and build in that, it will take a little longer, but it works just fine..
And to anyone who wants to learn, actually building the kernel isn't going to teach you as much as looking at the git commits and doing some Googling.. if you look in any of the threads where kernel discussion has been had, you can see a lot of useful info.
I suggest that the OP add a couple of notes about changes that can be made before the make command.. how to make those changes will be more educational that the process itself(tho it is helpful as hell, very well written!)
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
yea i planned on expanding the guide to have the different mods you can do in it.
Ziggy nice write up...
Nshih422 said:
I'd have to swap hard drives to get back on Windows.
Click to expand...
Click to collapse
If you're swapping hard drives (have only one machine), perhaps you should look into using VMware Player or VirtualBox.
For the free VMware Player, you can use http://www.easyvmx.com/ to build empty VMXs to get you started.
brainbone said:
If you're swapping hard drives (have only one machine), perhaps you should look into using VMware Player or VirtualBox.
For the free VMware Player, you can use http://www.easyvmx.com/ to build empty VMXs to get you started.
Click to expand...
Click to collapse
I know about vm, I'm a certified computer tech. It's something about my old drive not playing nice with ubuntu. I swapped this hard drive only installed ubuntu and have been using it as my main machine. It's just my laziness that's preventing me from having Windows and Linux.
Sent from my HTC_Amaze_4G using Tapatalk 2
Nshih422 said:
I know about vm, I'm a certified computer tech. It's something about my old drive not playing nice with ubuntu. I swapped this hard drive only installed ubuntu and have been using it as my main machine. It's just my laziness that's preventing me from having Windows and Linux.
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
yea, the main reason i made the guide go from linux to windows is because the kitchen it so much easier to get setup in windows. (so it makes this easier for the new folk) but yea, the kitchen works perfectly in linux as well. you could also make a vm box of windows within your linux machine.
ziggy46 said:
yea, the main reason i made the guide go from linux to windows is because the kitchen it so much easier to get setup in windows. (so it makes this easier for the new folk) but yea, the kitchen works perfectly in linux as well. you could also make a vm box of windows within your linux machine.
Click to expand...
Click to collapse
Somethings don't play nicely in Windows. When I try to build up ROMs from the kitchen, it tells me Cygwin may have an issue doing some parts. When I see that, I finish it off my other laptop that has Ubuntu on it.
Guess I'll be doing a video on how to set it up on linux this weekend.
Thanks Ziggy, as always. You were a great developer for the Triumph and glad to see you're active for the Amaze.
Sent from HTC Amaze
Dark Nightmare said:
Guess I'll be doing a video on how to set it up on linux this weekend.
Click to expand...
Click to collapse
Nightmare, you are awesome.. you guys taking the time to try to get the community involved more is awesome, so all of you keep up the great work. I have a feeling these threads will help members in other forums as well as they get found in random searches..
And to all the peeps reading this stuff, don't forget to hit their thanks button, it is the least you can do to show you want stuff like this!
Sent from my HTC_Amaze_4G using xda app-developers app
Silentbtdeadly said:
Nightmare, you are awesome.. you guys taking the time to try to get the community involved more is awesome, so all of you keep up the great work. I have a feeling these threads will help members in other forums as well as they get found in random searches..
And to all the peeps reading this stuff, don't forget to hit their thanks button, it is the least you can do to show you want stuff like this!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks, I wanna get involved in your little advanced wiki as well, . I'm finally back on linux, wanna make it my permanent OS, but I need windows for some of my progs, plus it's been a while, lol.
What's a good screen capture with audio client on ubuntu? I've recorded the set up video like 5 times already but the video keeps moving faster than the audio, any clues?
I have noticed that many people have had issues rooting their phone, especially recently. And i have also gotten tired of typing or copying the root method over and over after flashng in RSD and loosing root.
In response to that i have taken it upon myself to write a script for automating a majority of the process for all of us, making the process swifter than before. However this is not a one click root there are many steps nessecary to root our device. All i have done is wiritten a script to automate a majority of the process.
I will only test one version of the script, the ubuntu 12.10 version, because thats the only operating system i run and its easiest to test this one. i will leave the other versions to other people and to post issues with them as they arise so i may fix them
there are several versions of the script
*Ubuntu - 12.10 and up
*Ubuntu generic - 10.04-12.04
*Linux generic - any version of linux
*Windows bat file - Must download Motorola drivers
*Android - NEW ALPHA!! can actually be run from another rooted phone or tablet!! Scripts for general use coming soon! Testers are welcome! Check out the second post for details.
each version has the nessecary files to root your phone and including the script
These are not flash able scripts these must be uncompressed and run on a computer
Oh and feed back is more than welcome im not an expert at writing scripts or any sort of write up but i will do my best to fix any flaws or add suggestions.
Post 2: Change Log & Unstable Versions
Post 3: Instructions
Motorola USB drivers
Motorola website
MyGoogle Drive
Change log and unstables
Change log:
Version 4 - for windoze only:
Cleaned up script and readme
tested script runs into an issue because of the way windoze command prompt works
will update the instructions to inclued a sepereate method meant for windoze
Version 3:
Changed initial reboot command to adb reboot
broke script into to parts to fix adb shell /preinstall/su issue
Version 2:
Not published
would not get past adb shell /preinstall/su
Version 1:
First version made
BETAS:not for the faint of heart
To use you agree to contact me via pm upon downloading to obtain the password. This is because I REQUIRE all who use unstable versions to provide details and information on what does and does not work and what I can do to improve the experience.
MX2-arm-root:
Version alpha 0.1
Initial creation
No scripts
Root must be applied manually
Will need USB otg cable or micro USB to micro USB cable for fastboot command use (required cannot be fixed to run any other way)
Otg cable can be purchased for a few dollars from Amazon or other electronic retailer
MX2_arm_root_alpha0.1.zip
broken beyond android 4.1.2
Instructions:
*Download the zip file for your computers operating system from post one
*decompress with your favorite arcive manager i prefer 7zip
*READ THE README!!!!
*run initial script aka MX2-2.3.6-something-root
*follow instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*while your still in the adb shell as root run the following
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Windoze Instructions:
*decompress the zip and place somewhere easilly accessable by both windows explorer and command prompt
*READ THE README!!!!
*make sure drivers are installed- if at any point while the first script is running that drivers need to be installed(aka first time windoze has seen fastboot ect) wait for the drivers to finish installing before continuing.
*double click the initial script MX2-2.3.6-windows-root.bat
*follow the instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*close the script command prompt when finished
*open a new command prompt and do the following
*cd(to the directory where you uncompressed the zip
*adb shell
*/preinstall/su
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
there aren't any roms based on 2.3.6, doubt we will see any soon
Sent from my Milestone X2 using xda app-developers app
PotentChili said:
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
Click to expand...
Click to collapse
Try eclipse its not 2.3.6 based but it runs wonderfully on the mx2. As for the script its mostly an untested product. I've runt the Ubuntu 12.10 one once with little issue but the rest I haven't tried. Just remember its a two part script that requires the running of both pieces to work.
As to having a rom 2.3.6 based there really is no point we have fully functional roms that run beautiful with what we have not to mention that there's no real point in going back if we get a kexec or second boot working as further versions are going to be based off of a newer kernel and version of android.
Sent from my Nexus 7 using XDA Premium HD app
I'm now rooted thanks to this script by Lrs121! I strongly recommend those new to the process of root to use this script because it works!
Sent from my Milestone X2 using xda premium
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
DonInKansas said:
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
Click to expand...
Click to collapse
I'm glad it was able to help. I tried to make certain things more autonomous but unfortunately it does have to be specific, and handled as such. So there's not a lot of flexability in how the process is done by the user and by the script itself.
Sent from my Nexus 7
I've tested some superuser managing apps and so far the only one that works for our device is chainsdd's app. Clockworkmod's and chainfires supersu do not work well or at all. Please use the chainsdds app from the market or keep the one that the script installs as they work best.
Sent from my Milestone X2 using xda premium
A new script is coming soon. It will be an android to android script where you can root your phone using another phone or an android tablet. Thanks will go to the guys who have developed the p2p-abd tools. If the fast boot binarys are included
Sent from my Nexus 7 using XDA Premium HD app
Alpha for the arm aka android script is up. Testers are welcome to play with it. This is a very very basic build. Nothing is automatic, will be worked on as I go. The download, requirements and minor change log of what's included can be found on the second post. that post is now change log and unstable versions. Read what's included on the the log before trying. If you want to try but don't have and otg cable flash the preinstall img using a computer and play around with the arm adb binaries. Credit for the arm versions of the adb and fastboot binaries go to the original developers, they will be listed as I find the correct threads and sites I pulled them from are found.
Sent from my Nexus 7 using XDA Premium HD app
not working :|
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
zaq_37 said:
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
Click to expand...
Click to collapse
which pack did you use, each script is a little different
Lrs121 said:
which pack did you use, each script is a little different
Click to expand...
Click to collapse
Sorry I should have specified. It's the windows Pack.
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Lrs121 said:
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
zaq_37 said:
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
Click to expand...
Click to collapse
Hum I wonder what broke the windows script. Um really its up to you I can try to tear it apart and see if what's wrong but I'd need specific information from you in what's happening. But I'm a better Linux script writer so the Linux scripts are a bit more stable. Ubuntu 12.04 and up is best because the repositories have adb and fastboot included and can be installed. Both of which the script requires to run but any of the linux ones should work.
Sent from my SCH-I535 using XDA Premium 4 mobile app
On a side note I think I I figured out what's wrong. If I'm right correct me if I'm wrong, you tried to run the android-script.sh script from windows. If I'm wrong then I think the issue may be due to permissions
Sent from my SCH-I535 using XDA Premium 4 mobile app
Please help.
I recently received my Motorola Milestone X2 running 2.3.6. I have followed your method to a T. After the adb shell cmd, I receive no Superuser prompt. Then, after typing in the /preinstall/su cmd, it says: file not found, or file does not exist. I cannot remember. Can you help?
Thanks,
Jeremy
Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3