for the past couple of days i have been trying to install Ubuntu 13.04 on my nexus 7 but unfortunately, i keep running into problems. i have a laptop with Ubuntu 13.04 installed on it, but when i run the desktop installer it gives mean error for checksum validation. then i found a way that you could do it on a windows PC however when i go to download the cd images it bring me to a 404 (page not found) website. i would give the link but i am not allowed due to my account restrictions. if anyone could call me via Skype or team-viewer and could help me or perhaps provide an alternate way of installing Ubuntu or even tell me what i am doing wrong it would be much appreciated.
thanks in advanced, Kevin.
http://cdimage.ubuntu.com/releases/...3.04-preinstalled-desktop-armhf+nexus7.img.gz
dont i also need the boot img?
kevinperyea said:
dont i also need the boot img?
Click to expand...
Click to collapse
If you are installing it as the lone system, than yes, you will need the boot image. If you are using multirom to multiboot, than no, you wont need the boot image.
Sent from my Nexus 7 using xda premium
Its not very hard actually..First decide that do you want to remove android and replace it with android or yoou want to keep android untouched while multibooting ubuntu on your device as a secondary OPERATING system...
If you want me to I can write a full guide describing both procedures....I RECOMMEND MULTIBOOTING....
I need some help too
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
Thank's in advance,
GGgamer16
* one more thing ,i saw someting about multibooting, does it work like in windows(when you boot up it's asking you which os to run) or how does it work, and tell me hwo do i do it.
Ubuntu 13.04 on Nexus 7 2012
Posting in wrong spot... couldn't delete :/
attached is the fulll log from srart to finish of my build
Hi, for the last 2 days I have been trying to compile OmniROM for the Samsung Galaxy Note GT-N7000. The problem is that even after my second attempt (starting from scratch) it still won't compile. I followed these instructions (I know they're for the i9300):
http://docs.omnirom.org/Build_for_i9300
I did not however do the step "Add Device Repos to Local Manifest" due to it being for the i9300, instead I created a folder ~/android/omni/.repo/local_manifests/ and created a file wtf.xml according to @chasmodo instructions
Pastebin: http://pastebin.com/S8Fh7DqA
I'm compiling it on Linux Mint 16 "Petra" Cinnamon 64bit but I also tried the other day on Linux Mint 15 but had to reinstal due to windows which messed up my laptop.
Java version: javac 1.6.0_27
Anyone got any ideas? I'm particularly worried that I may have messed up this Local Manifest.
OK, I fixed it. For some reason it was using openjdk 1.7 :/ had to install an app to change which one it was using.
Hi All,
so this is my first post in this forum! Sorry for posting in the wrong sub-forum, but it doesn't let me post in the "Android Development" one unless I have 10 posts
I'm trying to get started with building Android ROMs for my trusty GT540, and while trying to build the kernel for my first ROM, this error came up:
Code:
LD .tmp_vmlinux1
arm-eabi-ld: error: no machine record defined
arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function get_nand_partitions:nand_partitions.c(.text+0xd308): error: undefined reference to 'msm_nand_data'
arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function parse_tag_msm_partition:nand_partitions.c(.init.text+0x1914): error: undefined reference to 'msm_nand_data'
arm-eabi-ld: drivers/built-in.o: in function mdp_refresh_screen:lowmemorykiller.c(.text+0x1e078): error: undefined reference to 'mddi_ss_driveric_innotek_position'
arm-eabi-ld: drivers/built-in.o: in function mdp_dma2_update:lowmemorykiller.c(.text+0x1e37c): error: undefined reference to 'mddi_ss_driveric_innotek_position'
arm-eabi-ld: drivers/built-in.o: in function flash_onfi_probe:lowmemorykiller.c(.text+0x6c424): error: undefined reference to 'msm_nand_data'
make: *** [.tmp_vmlinux1] Fehler 1
Do you have an idea how to solve this? I guess the first error ("no machine record defined") is the cause for the further errors?
So far, I tried to build an Android 2.3 Gingerbread ROM (using Cyanogenmod sources) for LG GT540; trying Gingerbread first because several other people have built it successfully already. So I checked out Cyanogenmod sources and pretty much followed the instructions from https://github.com/pcfighter/android_device_lge_swift-CM/blob/master/README ; then checked out the kernel from https://github.com/pcfighter/2.6.35 and tried to build it. There was no .config file so I extracted one from the boot.img from xda-cm-7.2.0-SDSL-12082012.zip. Then started the build with "make -j2 ARCH=arm CROSS_COMPILE=arm-eabi-". It asked for some more config options which I answered so-so, then started building, and after quite a while ran into that "no machine record defined".
Building is done on Ubuntu 14.04 x86-64 in Virtualbox.
Google hasn't given much specific help for this problem, but it looks like wrong .config parameters can cause this. Is there an existing "good" config for building 2.6.35 for Swift phone? Or can I generate a good config somehow? Or is the problem somewhere else completely?
Just a little follow-up: the magic command is "make swift_defconfig" - when run in the Linux kernel source directory this will create a .config file which should have correct options set for building a GT540 kernel.
Apart from this I'm still struggling to build a kernel that actually boots... Some of the kernels I've built have worked but many just fail to boot (at least when using fastboot). I've built with lots of slightly different configs now and still don't see a pattern. And I've now used
- the guide from https://source.android.com/source/building-kernels.html#building
- and the sources from https://un.poivron.org/~jimpulse/swift-squeeze-0.2.tar.gz
- and the toolchain from https://github.com/yath/android_prebuilts_gcc_linux-x86-32_arm_arm-linux-androideabi-4.6
- and a config based on the one from swift-squeeze-0.2.tar.gz
to build a working kernel under Ubuntu 12.04 (32bit, native system); but the exact same .config and toolchain and kernel source results in a non-booting kernel when built under Ubuntu 14.04 64-bit in Virtualbox!
Has anyone else ever seen such problems? Is this a known issue? So far I'm willing to just blame it on a hardware problem on my computer; but if anyone has an idea what else might cause this I'm interested!
Also: is there a way to get really early boot messages on GT540? With the failing kernels it just stays at the blue fastboot screen, and I'd really like to know what happens at that point
I'm currently trying to build a rom on my PC running Ubuntu. I have synced the repo and I am using LineageOS device tree and kernel tree.
The text doesn't seem to have appeared on the main post.
I have to post it on pastebin
https://pastebin.com/h3TtmEHe