This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download Sebanc's Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
Code:
sudo apt install pv:
sudo apt install cgpt;
sudo apt install tar;
I then run the following from inside the extracted Brunch directory (making my img file 20 gb):
Code:
mkdir -p ~/tmpmount;
sudo mount /dev/sda4 ~/tmpmount/;
sudo bash chromeos-install.sh -src chromeos*.bin -dst ~/tmpmount/chromeos.img -s 20;
sudo umount ~/tmpmount;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer;
sudo apt update;
sudo apt install grub-customizer;
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
Code:
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap quiet splash loglevel=7 disablevmx=off \
cros_secure cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
I then reboot, and I will see the Chrome OS option in the grub2 boot menu.
I hope this is helpful to someone.
From Project Croissant thread
https://forum.xda-developers.com/ha...ide-installing-official-chrome-os-pc-t3865697
I thougth this project might be better discussed in it's own thread...
corvek97 said:
Spent some days reading through this thread and trying everything I could find to get mine to install properly but it all ended in the same "Missing OS" error or something else.
Thankfully it all did lead me discover Sebanc's Brunch Framework which worked perfectly for me... aside from having some issues with the installation as some of the documentation wasn't as newbie-friendly regarding some stuff and their Telegram group is private but that aside, as a complete noob I imanaged to get it running in hours and every function related to the OS itself is working perfectly on my dual-boot PC and laptop.
Just sharing in case anyone else is going through the same thing here.
Click to expand...
Click to collapse
djuroganovic said:
+1 - I also have much better success with sebanc brunch on github than with chromefy script. Everything works great on r80, only downside is that it only works with UEFI bios, no legacy bios support.
Click to expand...
Click to collapse
ralphwiggum1 said:
Thanks for the information. The sebanc brunch tool worked great. It seems to have taken the best of various methods, but made it simpler without having the manage various partitions. Even better news is that I had issues with my Dell Venue 11 Pro not working with any method for a while. Arnold after R56 or something stopped showing video and other issues with all other builds, including Fyde, that I tried . Using brunch with just the recommended recovery (rammus), which is a more generic build, everything works. The grub/boot it comes with also seems to be a bit more generic and better than I had with Arnold.
Instructions and downloads are here: www.github.com/sebanc/brunch
Some clarification, particularly for dual-boot, is that it brunch documentation doesn't seem to mention that everything, once installed, resides inside of an image file (.img) on one partition (ntfs or ext4) on your drive. It also doesn't tell you to copy the boot files anywhere, but rather to boot from a USB/SD then it will boot up the img. I got around this by loading the boot files onto my main boot partition where I'm triple booting Windows 10, Ubuntu (I used ubuntu to do this), and Chrome OS. I don't think that matters too much since I'm using rEFInd (www.rodsbooks.com/refind/) as the main bootloader and I think it has modules to chainload from any partition, not just FAT like most BIOS need (I could be wrong, since all mines on the the main FAT boot partition). I'm using the minimal theme on the refind site with some custom icons. I modify these files in Ubuntu with a sudo bash shell.
Another note is you may be able to secure boot with brunch since they include a certificate you could theoretically load to your system's key for secure boot.
Click to expand...
Click to collapse
@ralphwiggum1: Can you share how you got reFind to work? I have updated manual.conf with the following, but it gives me an error:
Starting (null)
Using load options 'initrd=(loop'
Error: Not Found uhile loading (null)
* Hit any key to continue *
Here is what I have in my refind manual.conf file - which matches what I have in my Linux Mint grub2 (which boots up great):
Code:
menuentry "ChromeOS (boot from disk image)" {
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap loglevel=7 disablevmx=off \
cros_secure options=enable_updates cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
}
Any idea what I could be doing wrong?
TheMCNerd2021 said:
Tried using the script after I discovered it a few days ago, and it worked perfectly inside of an Ubuntu VM I created. Overall, everything built successfully when using the Croissant script to create a Chrome OS image (I used ATB R80 Special chromium image, Eve R80 recovery image, and swtpm.tar) and I was able to write it to an old USB drive and boot off of it on my old laptop. Most things worked fine except for the Play Store, which would give the generic "Something went wrong" error. I tried again, this time not enforcing SELinux when asked by the script, and the same exact error came up when using the new image. The chrome://flags page was also completely empty.
I eventually tried using Sebanc's Brunch Framework since other people on here have used it, and the resulting image file that I wrote to the USB drive worked great with my old laptop. Every function including the Play Store was working, albeit sluggish due to the flash drive I was using being slow.
Not sure why the Play Store wouldn't work when I used the image created with the Croissant script, yet worked when I used the image created with the Sebanc's Brunch Framework. I guess it's because my laptop (Acer Aspire E5-571-563B) is simply too old for the Eve recovery image. Either way, big thanks to the developers of both the projects for allowing us to run official Chrome OS on normal laptops.
Click to expand...
Click to collapse
ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
jhedfors said:
@ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
Click to expand...
Click to collapse
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
Copy the GRUB configuration which appears in the terminal at the end of the process (between lines with stars) to either:
your hard disk GRUB install if you have one (refer to you distro's online resources).
the USB flash drive / SD card GRUB config file (then boot from USB flash drive / SD card and choose "boot from disk image" in the GRUB menu),
Click to expand...
Click to collapse
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
ralphwiggum1 said:
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
Click to expand...
Click to collapse
Thank you for the suggestion - I will probably give it a try. Right now I have successfully added it to the Linux Mint grub menu. But I can't resist tinkering.
jhedfors said:
Where are you trying to install it? It looks like you are missing arguments that are required with the installation, for example:
https://github.com/sebanc/brunch/blob/master/README.md
Click to expand...
Click to collapse
Shawnashley said:
The hard drive of a windows laptop. Linux cmds aren't my strong suit. Sorry for the inconvenience.
Click to expand...
Click to collapse
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
jhedfors said:
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
Click to expand...
Click to collapse
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Forgot the screenshot.
Shawnashley said:
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Click to expand...
Click to collapse
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
Thanks, I've followed those already. The incomplete entry is the exact same way it is done in the YouTube video. I'll work it out. Thanks though.
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
keweminer said:
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
Click to expand...
Click to collapse
Mine errors and says path to Cheomeos can't be found. Strange since it's in the file I'm running in a terminal. It's quite screwy, Fyde OS is looking like the greener grass from over here. :laugh:
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
keweminer said:
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
Click to expand...
Click to collapse
Thanks for the info. I'll check there. I used the Linux mint method and created the folder and the IMG file but I could ever get it to install to disk. I tried various methods from the brunch page and no luck. Thanks though.
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
keweminer said:
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
Click to expand...
Click to collapse
That's cool. I had Fyde working pretty well, but battery life was awful and there were some glitches and flickering. I tried using Ubuntu in Windows to create a Cheomeos img but it tells me recovery image can't be found and all I have is a folder of files. Gonna go back to Fyde while I try to figure it out. Thanks for the input it's much appreciated.
I have updated the OP with my steps -
I hope this is helpful to someone.
Tag: @Shawnashley
jhedfors said:
This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download the Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
I then run the following (making my img file 20 gb):
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
I then reboot, and I will see this option in the grub2 boot menu.
I hope this is helpful to someone.
Tag: @Shawnashley
Click to expand...
Click to collapse
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Shawnashley said:
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Click to expand...
Click to collapse
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
jhedfors said:
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
Click to expand...
Click to collapse
Do you edit the recovery name or copy as is? Just double checking. Thanks for the help by the way.
Related
--- copied with permission from nathanpfry.com ---
Builduntu is a custom branch of the Ubuntu operating system, based on my guide here for preparing Ubuntu 16.04 to compile Android ROMs from source. It includes everything you need to sync with the repository of your choice (Cyanogenmod, AOKP, AOSP, etc) and start building.
I am not responsible for any damage you may cause to your system/files while trying to install Builduntu. This has been tested and verified working by me, so if you break Windows or your system won't boot, it's your fault.
This thread is not the place to ask how to install Linux or Dual Boot!!! These topics are well documented elsewhere and can be easily found in a few seconds on Google.
Thanks to Canonical, Google and me.
Features:
- Xubuntu 16.04 LTS base system
- Installed all necessary packages for compiling (list available in the guide link above)
- Unnecessary junk removed (media players, games etc.)
All you have to do is download the source!
The only requirement is that your host machine supports a 64 bit OS. 32 bit systems will not work!
Instructions:
1. Use your favorite image burning software to write the builduntu ISO to a blank DVD. Will not fit on a CD
2. Boot the disc. When the graphical installer starts, click "Install Xubuntu"
3. Follow the on-screen instructions to select language, username, etc. * Note * When setting up partitions, I recommend doing it yourself if you know how. If not, that's fine, let Ubuntu decide for you.
4. When the installation finishes, reboot and eject the installation media.
5. Sync the Android source locally:
~ A program called "repo" lets you communicate with git repositories and download source code. The following command will install it:
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
~ Use nano to edit ~/.bashrc
Code:
sudo nano ~/.bashrc
~ At the very bottom (use the Page Down key) paste this code to a new (empty) line:
Code:
export PATH=~/bin:$PATH
~ Save it. In nano that would be Ctrl-O and then Enter. Then Ctrl-X to exit back to a prompt. Restart bash:
Code:
source ~/.bashrc
~ In the terminal, navigate to where you would like to download the Android source code. The command below will make it in your home folder, but if you have limited space you may want to create it somewhere else. Faster is better, i.e. SSD would be best, USB external is basically unusable.
Code:
mkdir ~/android
cd ~/android
~ Now to initialize the repo. Decide the flavor of Android to build, i.e. AOKP, CyanogenMod, AOSP etc.
For the purposes of the tutorial, here's the command for CyanogenMod 13:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0
repo sync
When that is finished downloading, you're ready to start compiling ROMs!
Download Builduntu ISO:
Click here for mirrors!
Let me know how it works for you!
Feel free to buy me a Zico (donate) if you like my work. It would be greatly appreciated!
Please hit the "Thanks" button if this project helps you out!
Code:
[U][B]Changelog:[/B][/U]
v1.0 - First Release Mar 05 2014
v1.1 - Rebuilt from scratch the hard way
v1.2 - 4/20 Release - Update to 14.04 LTS Official
v2.0 - Update to 16.04 LTS with OpenJDK 8 for Android M builds
This is just awesome +1
This is Xubuntu 13.10...
I burned image on DVD using Brasero (ubuntu program) and run installation process from that DVD.
And before the end of installation I got this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Of course "buildbuntu" doesn't boot, some errors with reading/writing sda partition.
Luckly I installed it on my test drive so my workspace isn't damaged.
lozohcum said:
This is Xubuntu 13.10...
I burned image on DVD using Brasero (ubuntu program) and run installation process from that DVD.
Click to expand...
Click to collapse
I installed it to a fresh system just fine yesterday, not sure what your issue could be from. Could you post an installation log? Did you verify the md5sum of your downloaded file?
It is in fact Xubuntu 14.04. Canonical hasn't bothered changing the initial splash screen yet because it's still in beta. If you run the Live instance and check the version of ubuntu it correctly identifies as Trusty Tahr.
sylentprofet said:
I installed it to a fresh system just fine yesterday, not sure what your issue could be from. Could you post an installation log? Did you verify the md5sum of your downloaded file?
It is in fact Xubuntu 14.04. Canonical hasn't bothered changing the initial splash screen yet because it's still in beta. If you run the Live instance and check the version of ubuntu it correctly identifies as Trusty Tahr.
Click to expand...
Click to collapse
How to take installation log?
lozohcum said:
How to take installation log?
Click to expand...
Click to collapse
After the error appears it should load you into a live desktop session. The install log will be located there, perhaps in /var/log, /var/log/installer or the guest session home directory. Look around for .log files
edit : delete
I was hoping for a ubuntu base same as your virtual os..xubuntu ui is different and difficult
Ccahe error
Im trying to compile tihe ccache and when i set it up i recieve this error
bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
any ideas on how i can fix this would be appreciated
thanks
perfectpitch said:
Im trying to compile tihe ccache and when i set it up i recieve this error
bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
any ideas on how i can fix this would be appreciated
thanks
Click to expand...
Click to collapse
First, make sure ccache is installed (I'm reasonably sure it is out of the box)
Code:
sudo apt-get install ccache
If that's ok, check this link below and scroll down to Step 4a (optional).
http://forum.xda-developers.com/showthread.php?t=2506695
Ccache is not necessary and not ideal for all systems, so you may just want to disable it in your build process. Hope this helps.
Thanks I'll check it out
Sent from my Nexus 4 using XDA Premium 4 mobile app
so i dual booted ubuntu 13.10 on my laptop... but i couldn't build on it due to some stupidity... anyway, if someone could answer me some questions, maybe I'll uninstall ubuntu and switch to this since it's way easier for me.
1) did anyone successfully dual boot it? even with UEFI on?
2) can we transfer the source codes from an OS to another by packaging them and then extracting them in the new xubuntu? will it work that way?
Sent from my Nexus 4
lozohcum said:
This is Xubuntu 13.10...
I burned image on DVD using Brasero (ubuntu program) and run installation process from that DVD.
And before the end of installation I got this error:
Of course "buildbuntu" doesn't boot, some errors with reading/writing sda partition.
Luckly I installed it on my test drive so my workspace isn't damaged.
Click to expand...
Click to collapse
Hello, have you already solved that problem? Because since hours, even days I try to install builduntu on my notebook, but always got that error too!. I have usb legacy enabled, raid disabled and uefi boot enabled. I have a small ssd and a normal hdd. What am I doing wrong. I cannot get it to work, neither with manual editing the moint points, nor with automatically install through the system.
Many thanks!!
rodman01 said:
Hello, have you already solved that problem? Because since hours, even days I try to install builduntu on my notebook, but always got that error too!. I have usb legacy enabled, raid disabled and uefi boot enabled. I have a small ssd and a normal hdd. What am I doing wrong. I cannot get it to work, neither with manual editing the moint points, nor with automatically install through the system.
Many thanks!!
Click to expand...
Click to collapse
I never received an installation log from anyone so I have no way to start to figure out what went wrong.
It seems like many users have installed successfully, but a few are encountering errors like the one mentioned above.
I don't know how to help you without more information about the problem and your system. It could be a million things with how vague the descriptions are.
rodman01 said:
Hello, have you already solved that problem? Because since hours, even days I try to install builduntu on my notebook, but always got that error too!. I have usb legacy enabled, raid disabled and uefi boot enabled. I have a small ssd and a normal hdd. What am I doing wrong. I cannot get it to work, neither with manual editing the moint points, nor with automatically install through the system.
Many thanks!!
Click to expand...
Click to collapse
I haven't fixed it. I installed xubuntu and ocnfigured it on my own.
I wasted two DVDs for that Builduntu :/
i installed xubuntu today, it boots without a CD (just to confirm it's installed)
inside settings there's a button called "Install RELEASE", should i? i mean... it's already installed :S
Sent from my Nexus 4
sylentprofet said:
I never received an installation log from anyone so I have no way to start to figure out what went wrong.
It seems like many users have installed successfully, but a few are encountering errors like the one mentioned above.
I don't know how to help you without more information about the problem and your system. It could be a million things with how vague the descriptions are.
Click to expand...
Click to collapse
Yes sure can be many things....but here attached are some log files one/two from my try a couple of minutes ago. Problem is, that I already tried so many things and absolutely not sure whether it is my fault, my hardware or perhaps a bad download, in short where I have to look for the solution? Perhaps the log files give some useful information to you :fingers-crossed:
lozohcum said:
I haven't fixed it. I installed xubuntu and ocnfigured it on my own.
I wasted two DVDs for that Builduntu :/
Click to expand...
Click to collapse
Thanks for the info...can you pass me the download link? Haven't found it after a first and quick search ...
Edit: found it in the meantime....
update
In the meantime, I have also downloaded the "pure" Xubuntu and got it installed with the very first try. Exact with the same settings as last tries with builduntu. Dev environment is installed and source codes downloaded. At the moment I am building my first rom with this software. Hopefully it finishes without errors :fingers-crossed: .
i downloaded the sources on a VM, but couldn't make it work on my secondary OS after compression, tranfser, and extraction of the sources...
now redownloading from scratch on a 1Mbps (that's 128KB/s max) speed
Sent from my Nexus 4
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Mind the noobness, I just compiled my first kernel(ever) and stuck it in someones image and it worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(worked untill i enabled the builtin wifi, lol)
After i bought one of these tablets I can't say I'm not a bit dissapointed about the amount of dev work on the GT-5210, (words go unspoken for DutchDanny, Angel_666, trevd)
It's an x86 device, anything should be compileable and runable without any arm mods (i'm looking at you kali linux) this thing should be owning the Nexus 7.
Tested with TWRP 2.7 recovery
Its built using builduntu, and from the P5210UEUAMI8 source, with the toolchain recommended in the Kernel Readme.
I followed this tutorial to enable driver support
And this detailed guide to compile the kernel and create a proper boot.img
Replaced the boot.img in Mod57's rom with my modified one. (god fed up with fastboot and usb issues on Win 8.1 and just flashed it, it worked. Thats my testing)
Mod57 said:
This is built using the Samsung GT-P5210 P5210UEUAMI8 [4.2.2] Jelly Bean base.
ORIGINAL THREAD
This is not debloated it's fat and sassy like Samsung intended it.
If you would like to debloat I highly recommend using DutchDanny's debloater which can be found here:
http://forum.xda-developers.com/showthread.php?t=2482582
Jelly Bean P5210UEUAMI8
Fully Deodexed
Rooted
BusyBox
Zipaligned
Extended Power Menu (Wanam Xposed)
Will Not Delete Internal SD
Thanks to:
DutchDanny
Angel_666
Zidkijah
and everyone else who has contributed to this device.
Download:
http://www.androidfilehost.com/?fid=23189362627838229
MD5: 79f732fefbaf7882bc7c814d3ac1e998
Click to expand...
Click to collapse
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
You must have a rooted device (I used TWRP 2.7, http://nasirtech.blogspot.dk/2014/03/root-p5210xxuanb4-android-422-stock.html)
Code:
Put the modified rom onto the sdcard
Go to recovery
Wipe Cache and dalvik-cache
Install the ROM
Reboot and enjoy
Once you have installed the kernel and it boots up, you must follow these steps to chroot into an ubuntu image and compile / install aircrack.
Code:
Download this image: ubuntu-13.10.LARGE.x86.ext2.v1.zip
from [url]http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/13.10/x86/[/url]
and copy it to your sdcard
Thanks to jorgen_gustavsson for his excellent work [url]http://forum.xda-developers.com/showthread.php?t=2573441[/url]
1. Install busybox [url]https://play.google.com/store/apps/details?id=stericson.busybox[/url]
2. Install a vnc viewer [url]https://play.google.com/store/apps/details?id=android.androidVNC[/url]
3. Install [url]https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid[/url]
(Not sure, but open and close it once to be safe)
4. Copy bootscript.sh [url=http://forum.xda-developers.com/showthread.php?t=2573441]link to bootscript thread[/url] to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
bootscript.sh
(Thanks to xdadev: jorgen_gustavsson)
5. Unpack and Copy the ubuntu-13.10.LARGE.x86.ext2.img and .md5 to a place of your choosing on either internal or external sdcard.
6. Make a Linux on Android widget and point it to the img file you copied to your sdcard (ubuntu-13.10.LARGE.x86.ext2.v1.img).
7. Now click on the LOA widget you made in 6 and let linux ”bootup”
8. Press 'y' to check MD5 checksum
9. Connect vnc to localhost:5900 password ubuntu
Now to install Aircrack
# Libraries
sudo updatedb
sudo apt-get install build-essential
sudo apt-get install gcc
sudo apt-get install zlibg-dev
sudo apt-get install libssl-dev (or libssl-dev depending on your distribution)
#airolib-ng optional sqlite=true
sudo apt-get install libsqlite3-devel
#libnl optional libnl=true
sudo apt-get install libnl-genl-3-dev libnl-3-dev
#Required Extras
sudo apt-get install wireless-tools
sudo apt-get install net-tools
sudo apt-get install wicd-curses (or wicd-cli)
sudo apt-get install usbutils
sudo apt-get install wpasupplicant
sudo apt-get install dbus
# Download & unpack (or replace link with latest trunk)
wget [url]http://download.aircrack-ng.org/aircrack-ng-1.2-beta3.tar.gz[/url]
tar -zxvf aircrack-ng-1.2-beta3.tar.gz
cd aircrack-ng-1.2-beta3
# Make
sudo make libnl=false sqlite=false
sudo make install libnl=false sqlite=false
# or
make libnl=true;make libnl=true install
make install libnl=true;make libnl=true install
# or Airolib-ng support
make sqlite=true;make sqlite=true install
make install sqlite=true;make sqlite=true install
# Add binaries to path
export PATH=$PATH:/usr/local/sbin
# add the above line to below file for include path on startup
vim /home/ubuntu/.bashrc
# Update MAC OUI
airodump-ng-oui-update
Reboot and disable your internal wifi, connect your dongle, and get cracking.
This is what I spent my easter (and then some) doing, I hope someone can make good use of it. I can
Maybe someone can come along and add bcmon for the bcm4334 chipset
(Just maybe https://code.google.com/p/bcmon/source/browse/trunk/bcm4330/driver/src/bcmdhd/Kconfig?r=4 )
Any feedback and questions are welcome:
why didn't you use the latest source? -couldn't find it
Will this kernel work with xx rom? -probably not
Why aren't more roms including this? -dno, its in the menuconfig, should be easy
I've tried to give thanks where ever possible, let me know if you feel left out.
Ill come back tomorrow and clean up my post.
Best Regards
You my dear friend are a LEGEND
I'm also yoing to build an own kernel... And I think I'll add this feature too...
Sent from my GT-P5210 using Tapatalk
Keep having error while compiling kernel :"(
Daniel-TAz00 said:
Once you have downloaded and verified Mod57's rom
Click to expand...
Click to collapse
Thank your for your work. This is what I've been looking a long time for.
Please, would you provide a flashable zip of the rom with your kernel? It looks like I'm doing something wrong.
After flashing the modified rom my P5210 just keeps showing the wird boot logo and wont boot up at all.
Thanks in regard!
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
Click to expand...
Click to collapse
Well it have been a long story, I posted a thread about my error, here : http://forum.xda-developers.com/general/help/question-error-2-error-compiling-x86-t3047439 but in the end i found out i used the wrong toolchain. So i redownloaded the correct version and try again. It works but another error popup, its about some Broadcom error. I can successfully compile it after i disabled it in menuconfig. But instead of getting a Zimage i got a Bzimage. So Idk what to do with it. I googled a tones of information but still have no idea what to do with that bzimage. I used Kali Linux to compile and those kernel files are from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p5220 GT-P5220_SEA_KK_Opensource. Now i am trying to install builduntu and try to compile it again. Any tips or helps? especially with that bzimage
Daniel-TAz00 said:
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
[...]
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
Click to expand...
Click to collapse
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
Click to expand...
Click to collapse
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel.
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Max4000 said:
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Click to expand...
Click to collapse
I'll upload a complete zip for you, it's just gonna take a little while ....
OHH BOY!
This is Daniel-TAz00 thread, so he know what he is finally offering you when he said.
Daniel-TAz00 said:
I'll upload a complete zip for you, it's just gonna take a little while ....
Click to expand...
Click to collapse
Now what will be this "complete zip" he is offering! I hope is your desired kernel.
Max4000 said:
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel...
Click to expand...
Click to collapse
Max4000 In your quote
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
You are just looking in "This kernel/rom" at the beginning. While I am trying to tell you to look at the end "through Linux on Android."
So yes that kernel may have the "external RT8187 USB Wifi adapter driver" but in order to run "aircrack-ng/airmon-ng/airodump-ng" you need to run it through Linux....
Clearly the best approach is to use our internal wifi and some how run "aircrack-ng/airmon-ng/airodump-ng" without the need of "Linux" chrooted on Android.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/showpost.php?p=59310924&postcount=2
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB
It's what has been running on my tablet since I made the topic. If your tablet turns into a magic mushroom, it wasnt my fault
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/show...24&postcount=2
Click to expand...
Click to collapse
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Jacker31 said:
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
Click to expand...
Click to collapse
I did it with 7zip, open zip, replace boot.img, save zip, flash zip
Jacker31 said:
[MENTION=5688554]r2d23cpo[/MENTION
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
I compiled my zimage, and that was pretty much it i think
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Is it possible to make a update.zip? If so how?
Daniel-TAz00 said:
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB...
Click to expand...
Click to collapse
@Daniel-TAz00 First thanks. Nice work. But can you tell us if your "942MB" file is just the same
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
In particular it is VNC Linux on Android
Now I think @Jacker31 is here for the fun of learning kernel compile and finding a way to implement "aircrack-ng/airmon-ng/airodump-ng" with TAB3 10.1 own Wifi and without Linux VNC. That is what I guess from his post.
Jacker31 said:
... it was helpful for that Android Kitchen part...
Click to expand...
Click to collapse
Thanks goes to the Greatest creator @osm0sis. Last time he complains on me for saying it was another Kitchen. So NOOOO It is the best Kitchen in xda. I know all this nice applications get hidden on so many post. @moonbutt74 was the one to point me to use AIK.
Jacker31 said:
... How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded. ...
Click to expand...
Click to collapse
I will answer down
Jacker31 said:
... Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
You see Jacker31 is trying to include the needed driver in a kernel. But that is only a step.
So, which modules Tab3 10.1 own wifi? If so you need to recall that first we need to modify our driver bcmdhd to allow promiscuous communication!
Jacker31 said:
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Click to expand...
Click to collapse
So I guess once you read this is going to be late, I was going you suggest to backup your own boot.img first! I do still you are a bit confuse it is not just ZIP!! see below
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img bs=4096
Jacker31 said:
Is it possible to make a update.zip? If so how?
Click to expand...
Click to collapse
Yes, you see it is not just zip. In fact you need to make your own update.zip.
@Jacker31
1) So here is what you need to read. In this forum just search for "Edify", "updater script" and see how the script is build.
2) Please keep in mind that every device is different, in particular the partitions are in different places and in our case we are nor ARM but x86 or more technical we belong to the i686 family.
So if you unpack recovery.img an look inside the ramdiskfs you can find "/etc/recovery.fstab". By doing "cat /etc/recovery.fstab"
you will see
Code:
# mount point fstype device [device2]
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p10
/external_sd vfat /dev/block/mmcblk1p1
This tells you that "boot" is at partition "/dev/block/mmcblk0p10" and "recovery" at "/dev/block/mmcblk0p11".
So a valid script to introduce your new boot.img may read
Code:
ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p52xx ");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("[COLOR="Blue"]boot.img[/COLOR]", "[COLOR="Blue"]/dev/block/mmcblk0p10[/COLOR]");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");
Now I am attaching a update.zip skeleton. The needed part is in "update.zip\META-INF\com\google\android". There you will find "update-binary" valid for our x86 device. Observe how it is about 521KB. The ARM one is just around 125KB! Easily to distinguish. This "update-binary" is the program that will interpret the Edify commands that are store in "updater-script". So the "updater-script" holds the instructions.
In it you will find also "update.zip\META-INF\com\android". With "metadata" holds signature information when signed. And "otacert" with in fact holds the signature for ota validation. This files are only required when the update.zip is signed!! But that another process meant for distribution that I am not going to explain. In general when we test we do not sign the updtate.zip instead we disable that in the recovery menu, so that recovery accepts update.zip packages that are not signed. So I had include those for you knowledge but you can delete them if you want.
So the last file is "update.zip\boot.img". This is the file you are going to substitute and that you want to program.
And yes making the package is as simple of zipping all. Here is the important detail. When you zip the file you need to be in the same directory as the boot.img file is. So that the update.zip created do not contain an extra folder. In other words, when you double click a good update.zip you find quickly boot.img and META-INF folder. No extra folders.
Now waitttttt. That is just for your general knowledge. If you do use this info it is at your own risk. It is easily to do something wrong and break the device.
Example, Make sure you have a FULL battery before doing any firmware programing. The Charging mechanism is in boot image. If you have a bad boot image programing, then your device will not charge and if you get out of juice then you end up with a nonchargeable devices. It will feel that the device is dead, since you only way to charge will be to open the device and charge the battery separately!!!
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
r2d23cpo said:
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
Click to expand...
Click to collapse
@r2d23cpo
thanks for that answer, i am akinda into the linux, but there is plentyof stuff to get confused because of this x86 device and limited support from google. You are right, thats what i am going to research next, implement aircrack into the device it self and trying to find out that i can use the usb wifi dongle without turn off the build in wifi. Maybe you can surf facebook while attacking your neighbor network *joking* *its illegal anyways*
Well, Everything work well (I meant the script, I made some minor changes), except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why... I am trying to get a stock Boot.img and compile it again, since I used boot.img from philz back up...ANNNNNNNNNNNNND great bricked my device... not the first time though.
Jacker31 said:
Well, Everything work well, except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why...
Click to expand...
Click to collapse
I've got still the same problem.
This thread is about how to install RemixOS on HDD without data.img or any size restriction. No need to for any tools to increase RemixOS size.
Update: The more I spend time on this the more I learn new things. We dont need ubuntu to edit grub.cfg. It can be done using Diskpart within Windows.
So the only thing we need Ubuntu right now is to copy the RemixOS files to ext4 partition before we begin installation.
Update 2:If you can boot using gparted (http://gparted.org) then you can directly copy the files to new partition. So no need for Ubuntu. Just copy the Remix ISO files to a subfolder in gparted USB. Once gparted is loaded, open terminal, reformat new partition to ext4, mount it and copy Remix ISO files from USB to partition. Now you can boot from Remix USB and install to this new ext4 partition.
Code:
sudo mkdir /home/user/RemixDir
suod mount -t ext4 /dev/mmcblk0p5 /home/user/RemixDir
sudo cp -r /lib/live/mount/medium/Remix32/* /home/user/RemixDir
/dev/mmcblk0p5 is the partition as seen from gparted.
/lib/live/mount/medium/ is the mount point of gparted USB drive as seen in gparted.
Original:
This is a long thread make sure you read it once before you actually do it. This is long because I documented every step.
Have 2 speedy SD USB3 cards. I am using Sandisk Ultra 64GB & 32GB. You can get away with one but you have to keep reloading Ubuntu and Remix.
Download and install EasyUEFI on Asus T100 from http://easyuefi.com/index-us.html
Download Universal-USB-Installer from http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Download Rufus 2.7 Portable from http://rufus.akeo.ie/
Download latest Ubuntu ISO and create bootable USB using Universal-USB-Installer. I am using Ubuntu 15.10. Also, Rufus cannot create persistent Ubuntu.
a. Make the USB persistent. We will need Ubuntu often.
Get the bootia32.efi for your device from anywhere as Ubuntu does not provide it in their Amd64 ISO. The bootia32.efi from RemixOS did not work for me. For my ASUS T100, I got it from http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and place under /EFI/Boot folder in Ubuntu USB.
Download RemixOS 32-bit zip and extract it somewhere. Use Rufus to load Remix32 ISO to SD card. Universal-USB-Installer created USB will not boot.
Open the Remix OS SD card. Go to efi/boot and edit grub.cfg. We don’t need to put Windows entry here as we will do it later after everything is done.
Code:
menuentry 'RemixOS' --class android-x86 {
search --file --no-floppy --set=root /kernel
set root='hd1,gpt5'
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive INSTALL=1
initrdefi /initrd.img
}
Extract Remix ISO as well. Create a folder in Ubuntu USB called Remix32 and copy contents of Remix ISO to Remix32 folder in Ubuntu USB.
Start Windows on ASUS T100 and create new partition using Disk Management. Label it RemixOS. I would rather do it here than from Ubuntu so I don’t mess up Windows. Does not matter what filesystem you use here as you will format again from Ubuntu.
Connect Ubuntu USB to ASUS
Now boot Asus T100 and hit delete key like crazy to get into boot setup. If you see ASUS logo you are too late.
Disable secure boot and make Ubuntu USB first boot option. Save changes and restart.
When you see Try Ubuntu screen press CTRL+ALT+DEL, screen should resize to native resolution. Then select Try Ubuntu and let Ubuntu load.
Open Files, you should see RemixOS partition. Right click and select format.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select Custom typeName: RemixOSFilesystem: ext3 (I tried ext4 before but had lot of problems running RemixOS so changed to ext3. You can use ext4 if you have problem with ext3.)
After format complete, select Computer -> cdrom. This is the Ubuntu USB folder. You should have RemixOS folder here. Copy the content from this folder to RemixOS partition you created above.
Shutdown Ubuntu, plug Remix32 USB and get to boot from it.
You will see only RemixOS option here. You can press C and go to grub> prompt. Type ls to see all your partitions and make sure RemixOS partition has files are at ls (hd1,gpt5)/
If you see this message, something was not copied over from Remix32 ISO to new partition.
Android-x86 installer is not available
Press RETURN to run live version
After you answer/choose following options, Choose to Run Android-x86 not Reboot. You will be at RemixOS logo and install will continue and complete.
If you are reinstalling RemixOS after say changing partition from ext3 to ext4 or updating/upgrading RemixOS, skip Grub and Grub2 install.
But do over-write system.
Once reboot, you will not see RemixOS/Windows yet. It is still Windows only.
[*]Now we will boot Ubuntu again.
[*]This is where Linux purists are gonna kill me. I don’t know any other way to show Windows + RemixOS boot option, so if you know please let me know and I will update my post.
[*]Open Disks application in Ubuntu.
[*]Select EFI partition and mount it.
Lets boot Windows, open Admin Command Prompt and type Diskpart. Once in, type List Volume to see all partitions on disk. Select volume and then assign a drive letter to it. You can now edit grub.cfg.
Open grub.cfg from efi/boot and add Windows 10 entry as follows. This is a one time process, you dont have to redo this if you upgrade RemixOS, but if you over-write grub, this is needed.
Code:
set timeout=30
set gfxmode=1024x768
terminal_output gfxterm
menuentry "Remix OS" {
search --set=root --file /android-2016-03-01/kernel
linuxefi /android-2016-03-01/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive
initrdefi /android-2016-03-01/initrd.img
}
menuentry "Windows 10" {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
We are not done yet . Now lets go back into Windows and open EasyUEFI
Create a new Linux or Other OS entry and select bootia32.efi from EFI partition. Make this first boot option as we will load Windows too from this. You should already have Windows entry pointing to right efi,
Second partition should just have Microsoft related files. If you see something that does not belong here, use Diskpart in Windows or Disks in Ubuntu to delete them.
Finally after 30 steps, restart and you have your RemixOS. Go ahead and install Google Play and if you get any error installing apps from play store, just remove your account from the device and add it again.
Enjoy....
Dude thanks I have a t100 that I could install the alpha on and this one nothing. I also have a Minix that run windows and I could never get the alpha working. The beta couldn't work on anything. What I did after a lot of tries was just copy all the files to a USB stick and use your grub file but I removed the 0,5 part for the HD. What happen was that when it loaded resident mode, it just formated the stick by itself and now it works !
Thanks you so much
Thanks bro, finally my VivoTab M81C its working with your method. Do you have all yours sensors working? (WiFi, bluetooth, gyroscope and GPS) I can just makeit work WiFi.
Still doesn't help those of us on Dell Venue 8 Pro.......
Glad it worked for you.
-Dante- said:
Thanks bro, finally my VivoTab M81C its working with your method. Do you have all yours sensors working? (WiFi, bluetooth, gyroscope and GPS) I can just makeit work WiFi.
Click to expand...
Click to collapse
Lets list the things that DON'T work: Camera (The light is always on but no video in Skype), Bluetooth (Can see a MISC device in my phone but cannot pair), Screen rotation, audio works but crashes often (I just restart the device). Hey, I can atleast run MS Word on it and play android games on it, so no complaints.
Take it step-by-step
meebner said:
Still doesn't help those of us on Dell Venue 8 Pro.......
Click to expand...
Click to collapse
I know how frustrating it is when everyone in the world can install it except us, all I can say is take it in steps. If your device does not even boot when you select Recovery or Guest mode, just press c and go to grub> prompt. From there try playing with grub commands as listed at http://www.gnu.org/software/grub/manual/grub.html#Commands. It might or might not work but you will learn something about grub
<Edit> Wanted to to add, when at grub> prompt type ls. It will list out your partitions, then if you try ls (hd0, gptN) where N is your partition, you will know what file system it is. You can they enter that info in grub.cfg or reboot and command edit (e) and add it there.
Depending on how much time you are ready to spend on getting RemixOS installed, you can search askubuntu. Usually you will get an idea about what is involved in getting ISO to boot in 32 bit EFI. See http://askubuntu.com/questions/392719/32-bit-uefi-boot-support.
Good luck.
Thanks for sharing your grub.cfg. I was already on the right track, but since I didn't know the syntax or the path to the Windows bootloader I couldn't do much more than make a Windows entry in the boot menu that didn't actually do anything. I was going nuts trying to find the proper grub entry for Windows. Now my Toshiba Encore 2 is dual booting perfectly. If only there was a way to install Remix on a NTFS partition, instead, so I could have more than 4gb of data... Just FYI, the 64-bit Remix works just fine; just point grub to the 64-bit file instead of the 32-bit file in your cfg.
Nice share
I tried almost everything, but nothing worked for 32-bit UEFI Windows users, because my system is legacy only and I couldn't test any of the methods myself but you can help them. Can I post a link to your post on my post?
Sent from my Moto G using XDA Labs
Sure, no problem
SalarX said:
Nice share
I tried almost everything, but nothing worked for 32-bit UEFI Windows users, because my system is legacy only and I couldn't test any of the methods myself but you can help them. Can I post a link to your post on my post?
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Sure you can. More people helped the better.
I feel lot of people have these great budget ultrabooks/netbooks which for any corporate reason never got software that the hardware deserved.
I modified this to run on my 64-bit T100HA, but just changing the 32-bit references to 64. It boots, but I am stuck with the same black screen I had when I used the bundled in Installer. I guess it just doesn't work for me. I'm giving it to my wife, and buying a Nook or Kindle Fire for comics. Kinda bummed.
Does it sleep properly?
Shanesgc said:
Does it sleep properly?
Click to expand...
Click to collapse
No it does not. The screen goes dim but does not go off completely.
TP4LG said:
No it does not. The screen goes dim but does not go off completely.
Click to expand...
Click to collapse
I don't think any version of android sleeps properly on this thing. Super frustrating.
Hurray! This worked for me - at least Remix OS is creating data right now. i just had to do one more thing:
- add the bootia32.efi from remix os volume into the efi trusted file and put remix os at the top of boot list directly from efi setup
- everything works. Clearly for Play store to work decently you need to remove unknown source AND set good time zone.
- now i was wondering if there is a way to change the size of the data.img to use most of my 16gb partition for remix os
lilins said:
Hurray! This worked for me - at least Remix OS is creating data right now. i just had to do one more thing:
- add the bootia32.efi from remix os volume into the efi trusted file and put remix os at the top of boot list directly from efi setup
- everything works. Clearly for Play store to work decently you need to remove unknown source AND set good time zone.
- now i was wondering if there is a way to change the size of the data.img to use most of my 16gb partition for remix os
Click to expand...
Click to collapse
Try RMXtools by @imadlatch
Sent from my Moto G using XDA Labs
SalarX said:
Try RMXtools by @imadlatch
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks. that worked but as an internal drive can only be ntfs or fat32 i assume it is not possible to boot the remix pc from ntfs... so is there a way to tell android x 86 base boot files to look for data.img on my sdcard reader or use the whole sdcard as data disc ?
it would be the best way to have enought space to enjoy
lilins said:
Thanks. that worked but as an internal drive can only be ntfs or fat32 i assume it is not possible to boot the remix pc from ntfs... so is there a way to tell android x 86 base boot files to look for data.img on my sdcard reader or use the whole sdcard as data disc ?
it would be the best way to have enought space to enjoy
Click to expand...
Click to collapse
What format is your SD card?
I've not tried it, but maybe, you can keep your boot files (efi or isolinux) to the fat32 drive and move your all other files such as kernel, data.img, system.img, etc to an NTFS drive, overcoming the size limitation.
Sent from my Moto G using XDA Labs
---------- Post added at 04:32 PM ---------- Previous post was at 04:07 PM ----------
TP4LG said:
7. Added a new entry for Other OS and selected partition E and pointed to efi file at E:\efi\boot\bootia32.efi
Click to expand...
Click to collapse
If you could try one thing that would great. This might help many to achieve a data size partition greater than 4 gb
1. Moving all the files to an NTFS drive (keeping the EFI and isolinux folders in your current FAT32).
2. If that doesn't work, moving the kernel file back to your FAT32 drive.
3. If that fails too, moving initrd.img back to your FAT32 drive too.
4. If that fails, moving system.img back to your FAT32 partition too. (means in the end just leaving data.img on an NTFS partition)
Share your finding, by hit n trial
Sent from my Moto G using XDA Labs
I already tried something similar. I tried to install RemixOS on ext4 partition. It uses the entire partition size for OS, no data.img needed at all. But the downside is it does not turn WIFI ON. I can see lot of "intent" errors in logcat when I switch to prompt window by pressing ALT+F1 in RemixOS and typing logcat at the prompt.
I will try your suggestion later today and post results to this thread.
SalarX said:
What format is your SD card?
I've not tried it, but maybe, you can keep your boot files (efi or isolinux) to the fat32 drive and move your all other files such as kernel, data.img, system.img, etc to an NTFS drive, overcoming the size limitation.
Sent from my Moto G using XDA Labs
---------- Post added at 04:32 PM ---------- Previous post was at 04:07 PM ----------
If you could try one thing that would great. This might help many to achieve a data size partition greater than 4 gb
1. Moving all the files to an NTFS drive (keeping the EFI and isolinux folders in your current FAT32).
2. If that doesn't work, moving the kernel file back to your FAT32 drive.
3. If that fails too, moving initrd.img back to your FAT32 drive too.
4. If that fails, moving system.img back to your FAT32 partition too. (means in the end just leaving data.img on an NTFS partition)
Share your finding, by hit n trial
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
I agree to test, but which file holds the args to look for the "ntfs drive" files instead of the fat32 drive where boot.efi file is?
Envoyé de mon SM-A510F en utilisant Tapatalk
lilins said:
I agree to test, but which file holds the args to look for the "ntfs drive" files instead of the fat32 drive where boot.efi file is?
Envoy�© de mon SM-A510F en utilisant Tapatalk
Click to expand...
Click to collapse
set root='(hd0,gpt5)'
This tells the boot manager to look for the kernel file to boot and initrd.img.
Regarding to look for boot.efi, that you already specify in your bios settings.
Now the question is, do we need to specify an argument to detect system.img and data.img or is that automatically done?
Sent from my Moto G using XDA Labs
Hello everyone!
After a long day yesterday trying to install Remix OS alongside my already existing Windows 10 and Fedora 24 installations, managed by GRUB2, I finally completed the task.
I decided that I'm going to save other people wanting to do this some trouble, and post the updated guide, since personally I couldn't find it anywhere. It's mainly based on this guide and other similar ones (including the one by @remixtester here on XDA), and since RemixOS changed the install process a little bit, now it's actually done in 10 easy steps.
Recommended system requirements:
2 GHz dual core processor or better
2 GB system memory
Minimum 8 GB of free hard drive space
Internet access is helpful
1. Download the official latest Remix OS 3.0
2. Install Remix OS to a flash drive, using the provided Windows tool. If you don't have Windows, use Rufus or similar piece of software for your OS.
3. Create an at least 8 GB ext4 partition, and disable secure boot. Remember the partition number you are assigned
4. Boot from the flash drive, from the menu that follows click "e" on Resident Mode.
5. Delete > DATA= USB_DATA_PARTIOTION=1 and replace it with > INSTALL=1
6. Select your partition number, format it to ext4
7. Skip GRUB2, skip EFI GRUB and skip Write/Read Access
8. Reboot back to your Linux distro and open the Terminal
9. Log in as superuser and input: > gedit /etc/grub.d/40_custom
Add (do not remove the existing text in the file) the following text to the file. Replace the "X" in set root='(hd0,gptX)' with your partition number. Also paste the text exactly as is, the formatting is crucial for it to work:
HTML:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gptX)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1920x1080 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
10. Rebuild your GRUB:
For Fedora distribution:
grub2-mkconfig -o /boot/efi/EFI/Fedora/grub.cfg
For other Linux distributions:
grub2-mkconfig -o /boot/grub2/grub.cfg
Alternatively:
update-grub
Upon reboot you'll see Remix OS added to your OS entries and you should be able to boot up and use it just fine.
@engmia Great guide! Although I prefer Grub-Customiser!
The GUI makes everything so easy!
Just to be sure...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?
7. SKIP GRUB2, EFI GRUB and Write/Read Access
Click to expand...
Click to collapse
So thats skip Grub2, skip EFI grub and Yes to W/R Access?
set root='(hd0,gptX)'
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9L5kBcmfDqVbWxRU29CbDh4S00
This means it will read set root='hd2,gpt4)'?
Another thing is it cant find /RemixOS/kernel
any ideas?
Ok followed each step by step and i end up with
something (hd2,gpt4) something
must load kernel first
Click to expand...
Click to collapse
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"
Vodkanakas said:
Ok followed each step by step and i end up with
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"
Click to expand...
Click to collapse
In Ubuntu you can just do
Code:
sudo update-grub
Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error
Is it possible to install grub/theme using Windows?
Wryth said:
Just to be sure...
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?
Click to expand...
Click to collapse
Yes, correct.
Vodkanakas said:
Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error
Click to expand...
Click to collapse
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?
engmia said:
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?
Click to expand...
Click to collapse
Yes three seperate hdd in computer and set root='(hd2,gpt3)'
Vodkanakas said:
Yes three seperate hdd in computer and set root='(hd2,gpt3)'
Click to expand...
Click to collapse
Sorry for the late reply. Frankly I don't know how to help you, I can only repeat that to me it looks an error in the partition path. Try double checking what number has your distribution been assigned to terminal.
Guys, FYI we are reworking the INSTALL=1 installer. It should be done within 2-3 weeks. Initial release might be unofficial.
i clicked remix os on the grub and this messages shows up
error: cant find command `linuxefi';
error: cant find command `initrdefi'.
Press any key to continue.....
Click to expand...
Click to collapse
what should i do now? my resolution is 1366x768, http://imgur.com/a/yz4xs
@Ravagioli in grub customizer change linuxefi to linux and initrdefi to initrd.
Can I set the data partition to a specific partiorion on my hdd ??
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!
Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa
This can only be done when install Remix to flash drive? What about hard drive?
uttarayan21 said:
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!
Click to expand...
Click to collapse
pipyakas said:
This can only be done when install Remix to flash drive? What about hard drive?
Click to expand...
Click to collapse
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
lisa107b said:
Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa
Click to expand...
Click to collapse
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.
engmia said:
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.
Click to expand...
Click to collapse
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891
lisa107b said:
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891
Click to expand...
Click to collapse
Awesome, happy to hear you worked it out.
LuneOS for the HP Touchpad
Edited: January 30 of 2022 ( Update links for the LuneOS builds )
For information about LuneOS:
https://pivotce.com/2019/10/24/luneos-october-stable-release-eggnog-latte/
For the WebOS Nation Forum:
https://forums.webosnation.com/luneos/
How to flash:
LuneOS is flash onto it's own 2GB partition /luneos.
It shares the same swap partition from Android, same as WebOS does.
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
This guide and files will make it a dual boot of Android and LuneOS.
The only thing to do is download and flash as always.
All process will WIPE ALL the data from the Tablet.
Back up all data to PC, before doing any of the following.
To set up Tablet:
WebOS only: novacom driver must be on PC or use the following:
Click HERE for Linux OS with Novacom driver
If the Tablet only has WebOS or Android
One a PC with the novacom driver, place the Tablet in WebOS Recovery mode.
Download: uImage.wipe_all_create_Android_Luneos
Click HERE to Download uImage.wipe_all_create_Android_Luneos
open a command prompt where the file was saved and enter:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
( All data will be wipe, erase and formatted. Android volumes and LuneOS partition with a 1GB swap will be created.)
TWRP Recovery 3.2.1 modified to mount the LuneOS partition is flash in /boot
To flash any new test-build or stable version, only download, rename and flash.
There is no need to flash any WIPE_ALL
Main project Page:
https://github.com/webOS-ports
Testing releases to download
https://github.com/webOS-ports/luneos-testing/releases
20220125 LuneOS Testing BuildsExpand Assets: The following files are listed.
1. Download luneos-dev-image-tenderloin-20220125.rootfs.tar.gz file , renamed it to luneos.tar.gz and copy it to the Micro SD card of the Tablet.
Flash the following files in TWRP Recovery:
2. Download: The uImage-tenderloin-20220125 file , renamed it to luneos and copy it to the Micro SD card of the Tablet.
https://www.mediafire.com/folder/7hi6v6t8j092h/LuneOS
3. Download: Flash_boot_uImage_LuneOS.zip
4. Download: Flash_LuneOS.zip
If the Tablet has any version of Android or recovery:
Flash the following file with any recovery:
Download: Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
Click HERE to Download Automatic_Wipe_All_Create_Android_and_LuneOS_1GB_Swap_Partition.zip
Follow steps 1,2 and 4 from above.
The file: FLINTMAN-TWRP-3.2.1-0-03-15-2018_LuneOS.zip
Is the modified Recovery to flash LuneOS and is already flash onto /boot by the previous process.
Only flash this file, if is changed or damage in any way.
Click HERE to Download all the listed Files
LuneOS is constantly changing, the following link provide the luneos-testing files.
https://github.com/webOS-ports
LuneOS Eggnog Latte
After finish flashing there will be no animation or image while booting, only shows a dark active screen.
It will take a while and then the LuneOS logo will show to set up the Tablet.
Not working:
Camera
Home Button
Issues:
The screen will dim even is been use and will turn off.
Go to settings and change it to 3 minutes, but still will turn off.
There are more, but will be fix with the next release.
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
what are the steps?
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
3/ Flash Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
4/ Copy luneos.tar.gz to touchpad
5/ Flash Flash_LuneOS.zip
?
yeahman45 said:
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
The novacom is a driver that allows the PC to communicate with the Tablet when is place in the WebOS Recovery mode (Big USB Symbol)
There is no *.exe that can be executed to provide a graphical interface and interact with the Tablet.
All is done in a command prompt or terminal window.
The main use is to load any uImage into the Tablet's memory to boot with the following command:
novacom boot mem:// <
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
No, is not need it.
If the Tablet already has Android and any Recovery, then just flash:
Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
what are the steps?
Correct.
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
3/ Copy luneos.tar.gz to touchpad ( download from the link and rename it )
4/ Flash Flash_LuneOS.zip
5. Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
?
Click to expand...
Click to collapse
The Automatic_Wipe ( creates the LuneOS partition of 2GB plus all the standard Android volumes )
It also flash a modified version of TWRP that allows to mount the LuneOS partition.
Flash_LuneOS.zip is a script that will decompress luneos.tar.gz into the /luneos partition.
Flash_boot_uImage_LuneOS_Eggnog_Latte.zip is the uImage, to boot into LuneOS.
LuneOS is a work in progress, but once the Tablet is set up then future releases can be flash in the same way as Android ROMs, download and flash in TWRP Recovery.
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
yeahman45 said:
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
Click to expand...
Click to collapse
Thanks for the feedback, great to know the instructions can be replicated.
I am trying to apply the same optimizations that I did to all the Android ROMs and then it should work just as fast. Is using the Android Lollipop Kernel. The Web browser experience is different, allows for playback in the background and with the screen off, all native with no changes or modifications.
HP_TOUCHPAD said:
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
Click to expand...
Click to collapse
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Eearslya said:
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Click to expand...
Click to collapse
I did not provided the link to the file that will create the partitions for LuneOS, I will update the guide now.
Here is the file to download and flash. It will erase everything, format the storage and create the partitions:
For Android and LuneOS, it will be a Dual boot.
Click HERE to download the zip file to create Android and LuneOS partition
This is the link from the guide that allows to download all the files:
Click HERE to Download all the LuneOS and Android files
Select the best depending on your current set up.
That will do a Dual boot
For a Triple Boot to keep WebOS, Taylor a webOS APP must be use inside WebOS to create the LuneOS partitions.
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
0423TP said:
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
Click to expand...
Click to collapse
This guide is for a DUAL boot of LuneOS and Android.
WebOS will be wipe, completely remove.
If the Tablet has TWRP Recovery install then the full automatic flash zip file can be use.
The Tablet can do a Triple boot, WebOS, Android and LuneOS.
For that to be done:
Stock WebOS
Then use the ToolBox to create Android partitions.
Flash Android
Now is dual boot with WebOS and Android.
Inside WebOS using Taylor a new LuneOS partition must be created, then flash LuneOS inside WebOS.
The uImage of either Android or LuneOS must be move to the USB storage as there is not enough space in boot.
If you want to keep WebOS do not use any of the posted files, it will completely remove it.
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
-downloaded uImage.wipe_all_create_Android_Luneos
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
This rocks! Thank you for all the work on this to you and the LuneOS team
Thank you! I was considering this but have not made the time to research...
Sent from my PH-1 using Tapatalk
Nillanic said:
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
You are very welcome, give it some time and it will come back!
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
The Tablet can be found anywhere, some users have found some in brand new un-open boxes in the trash bin.
Many can also be found on ebay, so there is no shortage.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
That is the reason that I created the Live Linux OS, to provide the novacom driver built in. It will assure access to it forever.
Click Here for hp-touchpad-novacom-repair-android
-downloaded uImage.wipe_all_create_Android_Luneos
This is how is created, partitioning the internal storage with LVM:
Click HERE for the most powerful-feature-hp-touchpad-lvm
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
That is the best way to do it !
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
That command loads any uImage onto the Tablet's memory to boot. Is the same method to load the ToolBox, it can be use to load any Recovery with no need to have it on /boot.
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
The internal storage gets wipe out and repartitions.
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
That is the ROM, same as Android zip files.
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
LuneOS gets unzip and copy to the Tablet.
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
This is the uImage, it can also be loaded to memory from PC if boot is full.
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
The black screen looks like is dead, but is actually installing the OS.
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
You did a great job following the guide !
This rocks! Thank you for all the work on this to you and the LuneOS team
Click to expand...
Click to collapse
Thanks for verifying that all the steps are correct to get it working.
The WebOS HP Touchpad was way ahead of it's time when introduced in 2011. The flexibility of using LVM makes it possible for endless configurations.
It can be set up:
WebOS, LuneOS and any version of Android.
Or
Android, LuneOS, Sailfish and different versions of Linux as chroot.
Click Here for setting up Linux as chroot
Click HERE for the youtube channel
Work in progress by the LuneOS team on the possible next release:
https://forums.webosnation.com/webos-events/331758-webos-user-s-online-meet-up-12.html#post3456921
There is also work on porting Android 10, if it happens we will know some time next year or sooner!
Does anyone have the latest LuneOS uImage? It seems that the download page is down.
I would also like the "image" that is referenced in this step of installing LuneOS on their website:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
M.A. HP Touchpad said:
I would also like the "image" that is referenced in this step of installing LuneOS on their website:View attachment 5476941
Click to expand...
Click to collapse
It looks like everything is getting an update and the new version will be available soon, read this post:
https://forums.webosnation.com/luneos/332696-new-release-coming.html#post3457875
The new LuneOS test-builds are available.
At setup, it will show that WiFi is not available, finish the settings and then to enable it enter the following code:
Go to Apps then open QML TERM and enter this code
Code:
rmmod ath6kl ; modprobe ath6kl
systemctl mask systemd-udev-settle.service
Go to Prefs --> Wi-Fi turn ON and connect to your network.
Solution provided by:
https://forums.webosnation.com/luneos/332829-building-luneos.html#post3457972
Follow the guide and download the current files to get it working.
Any Android version can be use with LuneOS as dual boot.
LuneOS is also sharing the same swap partition with Android ( same as with WebOS )
Attached are (low quality pictures taken as there is no way to do screenshots at the moment.
Boot menu With Android (9) and LuneOS
After selecting LuneOS a blue screen will be display for about 3 minutes and 40 seconds.
After 3 minutes and 40 seconds the screen will turn black for a moment, then the LuneOS Logo will show.
There will be a setup and then the home screen will show.
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz)
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Touchpad_DMR said:
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file ( This file must be flash first )
After the Tablet reboot, copy the files to be flash.
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz) (WRONG FILE, read the file name, is for an emulator to be run on a PC)
Click to expand...
Click to collapse
The correct file name is : luneos-dev-image-tenderloin-20220125.rootfs.tar.gz
The kernel file is : uImage-tenderloin-20220125
The files are located at:
20220125 LuneOS Testing BuildsThen Expand Assets:
Touchpad_DMR said:
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Click to expand...
Click to collapse
Try with the correct file names, there is no need to do the Automatic_Wipe_All.
Made correction to the guide to properly find the files.
Many thanks for your help!
It works like a charm!
Please keep up with the good work.
It is deeply appreciated.
In the meantime, I'll play with my Touchpad and see what it does now!