tag:blogger.com,1999:blog-3120033476543048164.post5737290280204285777..comments2024-03-17T03:12:34.984-04:00Comments on Google and Android tips tricks and hacks: How to install Dual Boot Android x86 on PC KitKat 4.4 RC2 without USB or CDElizabeth Perriginhttp://www.blogger.com/profile/07635798318612958021noreply@blogger.comBlogger18125tag:blogger.com,1999:blog-3120033476543048164.post-64999173603005936752016-11-21T01:15:18.850-05:002016-11-21T01:15:18.850-05:00what are commands for android 6.0 cm version. i am...what are commands for android 6.0 cm version. i am getting errors<br /><br />Generating grub configuration file ...<br />Found linux image: /boot/vmlinuz-4.4.0-47-generic<br />Found initrd image: /boot/initrd.img-4.4.0-47-generic<br />Found linux image: /boot/vmlinuz-4.4.0-45-generic<br />Found initrd image: /boot/initrd.img-4.4.0-45-generic<br />Found linux image: /boot/vmlinuz-4.4.0-21-generic<br />Found initrd image: /boot/initrd.img-4.4.0-21-generic<br />Found memtest86+ image: /boot/memtest86+.elf<br />Found memtest86+ image: /boot/memtest86+.bin<br />Found Kali GNU/Linux 2.0 (2.0) on /dev/sda1<br />/etc/grub.d/40_custom.save: 1: /etc/grub.d/40_custom.save: in/sh: not found<br />error: out of memory.<br />error: syntax error.<br />error: Incorrect command.<br />error: syntax error.<br />Syntax error at line 440<br />Syntax errors are detected in generated GRUB config file.<br />Ensure that there are no errors in /etc/default/grub<br />and /etc/grub.d/* files or please file a bug report with<br />/boot/grub/grub.cfg.new file attached.<br />done<br />Anonymoushttps://www.blogger.com/profile/02040283238939610957noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-49168860094956106782016-05-24T04:00:50.939-04:002016-05-24T04:00:50.939-04:00How do I get Android to show up first in the GRUB ...How do I get Android to show up first in the GRUB menu?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-47603532772992803642016-02-02T14:36:02.720-05:002016-02-02T14:36:02.720-05:00A week ago decided to do the dual boot again. Wa...A week ago decided to do the dual boot again. Was having problems with the dual boot myself.. Had installed Android to a USB stick. When I restarted the PC with the USB inserted, Android booted from my partition.<br /><br />Another words, if Android is installed on a partition of 80gb and a without grub, and a USB stick with grub, android will boot from the USB stick and load off the partition. Elizabeth Perriginhttps://www.blogger.com/profile/07635798318612958021noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-27877989864763868862016-02-02T08:58:54.414-05:002016-02-02T08:58:54.414-05:00I am getting the same error as EI-Asad. Linux comm...I am getting the same error as EI-Asad. Linux command not found. Does this has anything to do with my partition not bieng in /etc/fstabAditya Chaudhryhttps://www.blogger.com/profile/01011887921313692346noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-7119609119219701822015-10-29T15:04:21.966-04:002015-10-29T15:04:21.966-04:00Same here. Did you fix it ?Same here. Did you fix it ?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-47044397072606780922015-06-30T17:14:28.989-04:002015-06-30T17:14:28.989-04:00Currently, my USB is in /dev/sdd
I want to install...Currently, my USB is in /dev/sdd<br />I want to install it in /dev/sde<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-65316274337894181042015-06-30T17:10:34.738-04:002015-06-30T17:10:34.738-04:00Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 he...Disk /dev/sda: 160.0 GB, 160041885696 bytes<br />255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors<br />Units = sectors of 1 * 512 = 512 bytes<br />Sector size (logical/physical): 512 bytes / 512 bytes<br />I/O size (minimum/optimal): 512 bytes / 512 bytes<br />Disk identifier: 0x0007e202<br /><br /> Device Boot Start End Blocks Id System<br />/dev/sda1 * 2048 310503423 155250688 83 Linux<br />/dev/sda2 310505470 312580095 1037313 5 Extended<br />/dev/sda5 310505472 312580095 1037312 82 Linux swap / Solaris<br /><br />Disk /dev/sdb: 160.0 GB, 160041885696 bytes<br />255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors<br />Units = sectors of 1 * 512 = 512 bytes<br />Sector size (logical/physical): 512 bytes / 512 bytes<br />I/O size (minimum/optimal): 512 bytes / 512 bytes<br />Disk identifier: 0x0004eadc<br /><br /> Device Boot Start End Blocks Id System<br />/dev/sdb1 2048 295806975 147902464 83 Linux<br />/dev/sdb2 295809022 312580095 8385537 5 Extended<br />/dev/sdb5 295809024 312580095 8385536 82 Linux swap / Solaris<br /><br />Disk /dev/sdc: 80.0 GB, 80026361856 bytes<br />255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors<br />Units = sectors of 1 * 512 = 512 bytes<br />Sector size (logical/physical): 512 bytes / 512 bytes<br />I/O size (minimum/optimal): 512 bytes / 512 bytes<br />Disk identifier: 0x00034998<br /><br /> Device Boot Start End Blocks Id System<br />/dev/sdc1 * 2048 156301311 78149632 83 Linux<br /><br />Disk /dev/sdd: 8011 MB, 8011120640 bytes<br />246 heads, 40 sectors/track, 1590 cylinders, total 15646720 sectors<br />Units = sectors of 1 * 512 = 512 bytes<br />Sector size (logical/physical): 512 bytes / 512 bytes<br />I/O size (minimum/optimal): 512 bytes / 512 bytes<br />Disk identifier: 0x0006e4bd<br /><br /> Device Boot Start End Blocks Id System<br />/dev/sdd1 * 2048 15646719 7822336 b W95 FAT32<br /><br />Disk /dev/sde: 20.0 GB, 20003880960 bytes<br />255 heads, 63 sectors/track, 2432 cylinders, total 39070080 sectors<br />Units = sectors of 1 * 512 = 512 bytes<br />Sector size (logical/physical): 512 bytes / 512 bytes<br />I/O size (minimum/optimal): 512 bytes / 512 bytes<br />Disk identifier: 0x00087109<br /><br /> Device Boot Start End Blocks Id System<br />/dev/sde1 63 39070079 19535008+ 7 HPFS/NTFS/exFAT<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-88437071165533405482015-06-30T17:07:54.997-04:002015-06-30T17:07:54.997-04:00This comment has been removed by the author.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-86465891824774186452015-06-24T20:29:22.918-04:002015-06-24T20:29:22.918-04:00I'm thinking it's in the hd3,1, HDD addres...I'm thinking it's in the hd3,1, HDD address? Not knowing your configuration I can't pinpoint. In terminal shell do<br /><br />sudo fdisk -l<br /><br />Paste the results.Elizabeth Perriginhttps://www.blogger.com/profile/07635798318612958021noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-42013598878290227392015-06-24T20:10:17.774-04:002015-06-24T20:10:17.774-04:00Silly me, "code" is a HTML tag or someth...Silly me, "code" is a HTML tag or something :D<br />I deleted those tags and got this;<br />error: can't find command 'Linux'.<br />alloc magic is broken at 0xcfef8a60: 0<br />Aborted. Press any key to exit._<br />Any Ideas on how to solve this?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-79877940203841078652015-06-24T19:48:06.745-04:002015-06-24T19:48:06.745-04:00My BIOS is corrupted, I can't save any setting...My BIOS is corrupted, I can't save any settings, so I can't boot from USB or CD, and everytime I need to login to my Ubuntu-MATE 14.04 I need to reset the CMOS with the jumper and all that. <br />Anyway, I want to install Android on another HDD (/dev/sde) and I put the Android folder with the data and the .img .sfs and kernel files in a USB (/dev/sdd) so I could load it and then install it. I followed your instructions, my /etc/grub.d/40_custom looks like this:<br />#!/bin/sh<br />exec tail -n +3 $0<br /># This file provides an easy way to add custom menu entries. Simply type the<br /># menu entries you want to add after this comment. Be careful not to change<br /># the 'exec tail' line above.<br />code menuentry "Android-x86" {<br />set root='(hd3,1)'<br />Linux /Android/kernel quiet root=/dev/ram0 androidboot.hardware=generic_x86 acpi_sleep=s3_bios,s3_mode SRC=/Android<br />initrd /Android/initrd.img}<br />code<br />(I had to delete the " symbols for this post)<br />But when I get to GRUB menu, if I select Android it will take me to a blank screen with a message: "Press any key"<br />I press any key and takes me back to GRUB's menu. What did I did wrong, can you please help me?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-73521515323681641682015-05-31T12:01:17.369-04:002015-05-31T12:01:17.369-04:00Hi. Very good write up. Please restore images. Man...Hi. Very good write up. Please restore images. Many thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-78532437780047281942015-03-27T15:09:46.796-04:002015-03-27T15:09:46.796-04:00Does this work for UEFI systems?Does this work for UEFI systems?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-25700739289188886872015-03-23T11:26:35.617-04:002015-03-23T11:26:35.617-04:00..thanks...it's work for my pc....thanks...it's work for my pc..o9dey8https://www.blogger.com/profile/18295333390717752271noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-24885337984115254932015-01-11T08:26:14.427-05:002015-01-11T08:26:14.427-05:00/etc/grub.d/40_custom.save: 1: /etc/grub.d/40_cust.../etc/grub.d/40_custom.save: 1: /etc/grub.d/40_custom.save: Û!/bin/sh: not foundPereirahttps://www.blogger.com/profile/17577065785275113003noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-3100506017421140172014-11-30T05:02:17.621-05:002014-11-30T05:02:17.621-05:00everything is working but in android it says syste...everything is working but in android it says system is read only. is there a way to make it read-write.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-56864167450857257742014-09-18T19:56:21.545-04:002014-09-18T19:56:21.545-04:00Sorry for the late reply, you are right, it was a ...Sorry for the late reply, you are right, it was a misspelling on my part, it has been corrected. Should be system.sfs. <br /><br />Lets say you partition off 20gb of your hard disk just for Android-x86. Then in ubuntu you open up that partition in your file manager. Just create a folder called android-x86 and inside that folder make another folder named data, leave it empty. Outside that folder put the four files, system.sfs, kernel, initrd.img and ramdisk.img.<br /><br />In the post also update a picture how it should look.Elizabeth Perriginhttps://www.blogger.com/profile/07635798318612958021noreply@blogger.comtag:blogger.com,1999:blog-3120033476543048164.post-63807618747783526452014-09-15T15:57:56.621-04:002014-09-15T15:57:56.621-04:00I don't understand the part 2:
system.cfg miss...I don't understand the part 2:<br />system.cfg missed, i have system.sfs.<br />what do we do with ramdisk.img?<br /><br />Thanks a lot.<br />Anonymousnoreply@blogger.com