Hi,
i was dying to try RemixOS 3.0.
Running a Surface Pro 3 the mere thought of booting out of secure boot mode and imposing the bright orange screen to my eyes every time i started the thing was discouraging any attempts to installing RemixOs.
Using another machine i installed RemixOS on a flash drive and notied it used the ubuntu grub2, which is signed and doesn't require secure boot disabled in order to start, and to my surprise i could boot remixOS from the flash drive without disableing secure boot on my surface pro 3.
Then booting on a flash drive on a tablet with only one USB port... not good enough for me so if i could boot to USB with secure boot maybe i can do it from hard drive, to be honest my first attempt wasn't successful using a NTFS partition to install Remix, so i tried to install it to a FAT32 partition and was surprised when the OS actually booted in secure boot mode despite two errors :
secure boot forbid loading /efi/RemixOS/exfat64.mod
secure boot forbid loading /efi/RemixOS/ntfs64.mod
i don't know what are those modules used for, as of now the OS runs fine except for the fact that double clicking on desktop icons crashes and resets the OS but this behaviour happens on all the machines i tested (surface pro 3 and my desktop computer).
[EDIT] This only happens if the icon moves when double clicking probably comes from touchpad sensitivity and the way they handle rearranging the desktop [EDIT]
TL;DR:
Found out i could boot RemixOS with secure boot ON from a USB flash drive.
Tried to do the same from hard drive.
Didn't work using NTFS.
Worked using FAT32 despite not being able to load exfat64.mod and ntfs64.mod
Questions:
Did someone actually found a way to install and run RemixOS without errors in a Secure Boot environment ?
What are exfat64.mod and ntfs64.mod used for ?
PS : touch and multitouch works fine here (i've seen people complaining about it not working, maybe for an older version)
First of all, why do you need secure boot?
Sent from [email protected] 4
I don't need secure boot but as mentionned it just disgusts me when my surface pro boots up to an agressive orange screen with a black square in its center for the Surface logo which is what happens if i disable secure boot.
So yeah it's just cosmetic, you can also call this personnal research on secure boot.
When i was using Manjaro Linux on this same computer i learned how to sign my bootloader just so i could boot in secure boot mode.
Related
I don't really know what's going on here. I think it's maybe UEFI related. I own an Asus Zenbook Pro (model UX501VW in case if that matters). I can't get Remix OS 2.0 Beta urnning on my SSD. I've already disabled Secure Boot and Fast Boot but I always get stuck on "Detecting Android x86.............." infinite bootloop.
Installed it with the official tool in the original partition (C
Installed it in a secondary partition (D:, FAT32)
Used EasyBCD
Used Unetbootin
Used Grub2Win (interestingly, It leads to a blackscreen instead of the other error)
In fact. I'm not able to run it. I know that the ISO isn't corrupted because I can run it in VMWare Workstation.
Any thoughts?
Same here
In which field its stuck on booting or on build the rom
It doesn't even build the partition to install the ROM on it. Even if I create the partition by myself, it will show the same problem.
In the screen where you have to select boot RemixOS or Windows, just press c and go to grub> prompt. Type ls and see what is your HDD partition structure. You can also press e and go to check actual install command. You may have to make changes to /efi/boot/grub.cfg. I can help.
I've tried usb install and other methods to install remixos but I can't boot up to remix installer. I've disabled secure boot but easy bcd still sees the secure boot?
Danno5150 said:
I've tried usb install and other methods to install remixos but I can't boot up to remix installer. I've disabled secure boot but easy bcd still sees the secure boot?
Click to expand...
Click to collapse
What Model your Asus ???? Asus X8AIJ my very life bulbs (Core Duo chipset),,, installed on HDD RemixOS good run very smooth ....
** Set default Duoboot admitted .. (My Menu Boot: Win10 + Ghost + RemixOS) works well, no need to install BCD!!!!
Got it to work, the 3 different partition threw me off a bit
Danno5150 said:
Got it to work, the 3 different partition threw me off a bit
Click to expand...
Click to collapse
First I installed Win10 64 bit before,,, then create a menu with a line 2rd Ghost and more recently I RemixOS 64 natural,, and boot it add 3rd line ...... I have no more use software other than default settings as directed
Specifically attempting to install it on an HP Envy Note 8 with an Atom x5 processor and 2GB of RAM. It originally had Windows 10 on it but I've pretty much wiped it out (formatted the entire SSD including recovery partitions).
I have an 8GB flashdrive formatted to FAT32. I run the 32 bit Remix OS installer and once it finishes I use a micro USB to USB adapter to insert the flash drive. When running the 64 bit installer the Flash Drive shows up as a bootable device and up on selecting I get an error with a memory location (ex)0x8XXXXXX something.
I tried the 32 bit installer (probably should have used that in the first place) I do the same steps use the Remix OS installer Tool and start up the tablet. However this time the tablet does not recognize the flash drive as a bootable device (literally just does not show up in the list of bootable devices have re-run the installer 3-4 times with no change). I have tried it with and without virtualization enabled and with and without secure boot enabled and get the same problem.
Any help would be greatly appreciated.
update: I got it to boot 64 with secure boot disabled. How do actually install the files to the local drive?
Update 2: Was able to install to the local hard drive by hitting e on the selection screen (Guest or Resident) and adding INSTALL=1 DEBUG= to the end of the parameters section but above the existing new line.
It's working and running well however the touchscreen is unresponsive any way to get that working? Right now I'm using a micro USB splitter and a keyboard/mouse plugged into the USB ports.
Im in, I'll recieve my mi Pad 2 soon (same cpu) I'll try to get it working too when I rcieve it is there a working Android solution for ur envy?
bomblord said:
Update 2: Was able to install to the local hard drive by hitting e on the selection screen (Guest or Resident) and adding INSTALL=1 DEBUG= to the end of the parameters section but above the existing new line.
It's working and running well however the touchscreen is unresponsive any way to get that working? Right now I'm using a micro USB splitter and a keyboard/mouse plugged into the USB ports.
Click to expand...
Click to collapse
Check if reloading the modules helps.
Either #rmmod i2c_hid && modprobe i2c_hid
Or start RemixOS from fully off i.e. don't reboot from Windows
Nailyouh said:
Im in, I'll recieve my mi Pad 2 soon (same cpu) I'll try to get it working too when I rcieve it is there a working Android solution for ur envy?
Click to expand...
Click to collapse
I was able to get it installed however it doesn't appear to have touchscreen support
bomblord said:
I was able to get it installed however it doesn't appear to have touchscreen support
Click to expand...
Click to collapse
That sucks! I hope we will be able to use another Kernel compiled with tsdrivers im really looking forward to recieve my tablet
HypoTurtle said:
Check if reloading the modules helps.
Either #rmmod i2c_hid && modprobe i2c_hid
Or start RemixOS from fully off i.e. don't reboot from Windows
Click to expand...
Click to collapse
Remix OS is the only OS on my tab I did a complete re-install and disconnected the Keyboard and Mouse before boot (didn't actually do that intentionally as a troubleshooting tip I just needed to attach the charger). It's working now!
One issue after the next~ but im excited so far. Touch screen is working OS is installed.
Now I can't get the screen to rotate though. I double checked auto rotate is on and I also attempted to double tap F11 to get it to manually rotate but neither seems to work
Edit: On top of that I get stuck at a flashing Remix OS screen after reboot now that doesn't go away even after around 20 minutes of waiting.
bomblord said:
One issue after the next~ but im excited so far. Touch screen is working OS is installed.
Now I can't get the screen to rotate though. I double checked auto rotate is on and I also attempted to double tap F11 to get it to manually rotate but neither seems to work
Click to expand...
Click to collapse
Yes it's force locked by default (think of it in terms of a PC and that makes sense)
Have a look at one of my threads; either Overlay Apps, etc.. Or systemless root
Personally I'd try the systemless root (if you are running 64bit which I guess you are); it has rotation enabled and has that touchscreen 'fix' as a su.d (init.d) script.
So after restarting the system I'm stuck at a flashing Remix OS (Remix OS is installed to my hard drive after using the installer I removed the USB drive and my initial boot was from the hard drive not a USB) any way to get around this?! Persists even after multiple reboots. I've let it sit for around 20 minutes on this one now.
HypoTurtle said:
Yes it's force locked by default (think of it in terms of a PC and that makes sense)
Have a look at one of my threads; either Overlay Apps etc. Or systemless root.
Personally I'd try the systemless root (if you are running 64bit which I guess you are); it has rotation enabled and has that touchscreen 'fix' as a su.d (init.d) script.
Click to expand...
Click to collapse
Thanks I'll look into it once I figure out how to get back into the OS...
bomblord said:
So after restarting the system I'm stuck at a flashing Remix OS (Remix OS is installed to my hard drive after using the installer I removed the USB drive and my initial boot was from the hard drive not a USB) any way to get around this?! Persists even after multiple reboots. I've let it sit for around 20 minutes on this one now.
Click to expand...
Click to collapse
Can you press ALT&F1 and check logcat?
Or tried removing quiet from grub and seeing what is 'looping'
HypoTurtle said:
Can you press ALT&F1 and check logcat?
Or tried removing quiet from grub and seeing what is 'looping'
Click to expand...
Click to collapse
logcat says installid fs upgrade not yet complete Waiting...
Failed to read /data/ .layout_version: No such file or directory followed by skipping tombstone a bunch of gibberish and it then repeats
bomblord said:
logcat says installid fs upgrade not yet complete Waiting...
Failed to read /data/ .layout_version: No such file or directory followed by skipping tombstone a bunch of gibberish and it then repeats
Click to expand...
Click to collapse
Does mount show that /data is mounted? It could be that data.img has corrupted like from a bad unmount. Not sure if you have access to it; but to confirm modify grub to use guest mode (data in ram) by adding/changing DATA_IN_MEM=1
I tried add DATA_IN_MEM=1 to the boot but it didn't seem to make a difference (although it did notably restart on it's own instead of just staying at the flashing screen) where do I need to type "mount"?
bomblord said:
I tried add DATA_IN_MEM=1 to the boot but it didn't seem to make a difference (although it did notably restart on it's own instead of just staying at the flashing screen) where do I need to type "mount"?
Click to expand...
Click to collapse
mount from same place as 'logcat' (ALT&F1)
just to check; you added the the DATA_... to the same line as linux... if so also add a DATA=
please help to fix CH tablet wifi problem
http://forum.xda-developers.com/remix/supported-devices/remix-os-v820w-ch-wifibt-t3382047
So after an attempted reinstall i get the same issue anytime I shut down and restart. The only way i can boot is from the installer screen by choosing "Run Android x86" the grub boot doesn't work
edit: using the data_in_mem and data= parameters it launches in guest mode
edit 2: guest mode keeps restarting itself and doesnt respond to keyboard input
edit 3: i had plugged in a flash drive unplugging it made it go back to the remixos logo and not boot
bomblord said:
So after an attempted reinstall i get the same issue anytime I shut down and restart. The only way i can boot is from the installer screen by choosing "Run Android x86" the grub boot doesn't work
edit: using the data_in_mem and data= parameters it launches in guest mode
edit 2: guest mode keeps restarting itself and doesnt respond to keyboard input
edit 3: i had plugged in a flash drive unplugging it made it go back to the remixos logo and not boot
Click to expand...
Click to collapse
Can you run through your install procedure, as your installing from a wiped SSD right?
HypoTurtle said:
Can you run through your install procedure, as your installing from a wiped SSD right?
Click to expand...
Click to collapse
Sure
I run the "Remix OS for PC Installation Tool" from a separate windows PC and use the "USB DRIVE" option to put the 64 bit remix os files on my flash drive
I then use a powered USB HUB and a Micro USB to USB converter to plug in a keyboard and the flash drive. I hold down the volume down key on my tablet to get the boot options and then choose the flash drive as the boot drive
From there I'm given the option of "resident mode" and "guest mode" I hit "e" on the resident mode and add the lines INSTALL=1 and DEBUG= to the second from last line in the grub commands.
I then get a blue screen I choose my hard drive as the install location and choose to format it to ext4, I allow grub and grub 2 to install, and install it as "read/write". It then says "expecting to write" and then runs from 0 to 100% and says syncing to disk. From there I have the option to "Boot to Android X86" or "Restart" and I remove the flash drive.
If I choose "Boot to Android X86" it boots into remix OS and I can use it until I restart. After restart I get the flashing white Remix OS logo and it never finishes booting (just to be certain it wasn't an issue with it taking a while I literally let it sit over night for about 10 hours to see if it ever finished and it did not).
If I choose "Restart" I get the flashing white Remix OS logo after the grub screen and it never loads.
I think that should cover it.
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on have about the same power as old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Fallingwater said:
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on *have* about the same power of old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Click to expand...
Click to collapse
Try flashing it to another hard drive, insert both drives into the computer, and and at the grub menu press alt, and add "install=1 debug=" (without the quotes of course, and debug should have no character whatsoever afer the equals.
After installing from the second hard drive to the first, turn off the computer, remove the second hard drive, and boot up the conputer.
I hope this works for you.
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Flemischguy said:
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Click to expand...
Click to collapse
No need for windows, however it makes things easier for flashing it on the flash drive.
My recommendation, though, is to use the flash drive as an installer: according to what I had written above, install Remix OS to a hard drive from the flash drive.
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Fallingwater said:
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Click to expand...
Click to collapse
Not much, unfortunately.
However, perhaps a BIOS update will help.
It's already updated to the newest revision.
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Fallingwater said:
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Click to expand...
Click to collapse
Alright, I hope it'll work then.
RCA Cambio Model w101 V2
I managed to get it Installed to a hard drive partition, I had all kinds of issues with that but I've had issues with the 32bit efi on most linux distros. The boot up is still a bit buggy.
I copied the USB to the hard drive after installing to the USB the live ISO. I booted the partition through the bios (might have changed some grub option to get it to boot). I then changed the Grub option to load the install. I installed to the same drive and left it NTFS made a 3gb data.img. After messing around with the file system and grub, I got that booting. Install/updates apps but not the system update, that hangs at 20%.
I've had nothing but problems with this 32bit EFI/64bit systems. I'm trying to get some Linux running fairly nice so I can remove Win 10 , I don't see that happening
I've had luck with Ubuntu Zesty Linuxium build but only to the point of it being a Laptop.
On Remix the screen stays in Portrait and it don't fill the screen, its centered. No Bluetooth, No sound but I did see a link here for possible fix for that. No touch Screen. No battery ready, stays at 100%.
On the plus side the Docking keyboard works and wifi.
It looks like a nice GUI, its the first time I've looked at it.
I assume I'm missing a lot Kernel modules and firmware? Most of what I read looks like old info on these X86 Tablets. Is there anything new to help set them up, what works on them and what don't? I'd like to start with display and sound. Move to touch. Mostly all I care about and a working battery meter.
Thanks PS still boots Windows 10
Remix OS
elizabeth1701 said:
RCA Cambio Model w101 V2
I managed to get it Installed to a hard drive partition, I had all kinds of issues with that but I've had issues with the 32bit efi on most linux distros. The boot up is still a bit buggy.
I copied the USB to the hard drive after installing to the USB the live ISO. I booted the partition through the bios (might have changed some grub option to get it to boot). I then changed the Grub option to load the install. I installed to the same drive and left it NTFS made a 3gb data.img. After messing around with the file system and grub, I got that booting. Install/updates apps but not the system update, that hangs at 20%.
I've had nothing but problems with this 32bit EFI/64bit systems. I'm trying to get some Linux running fairly nice so I can remove Win 10 , I don't see that happening
I've had luck with Ubuntu Zesty Linuxium build but only to the point of it being a Laptop.
On Remix the screen stays in Portrait and it don't fill the screen, its centered. No Bluetooth, No sound but I did see a link here for possible fix for that. No touch Screen. No battery ready, stays at 100%.
On the plus side the Docking keyboard works and wifi.
It looks like a nice GUI, its the first time I've looked at it.
I assume I'm missing a lot Kernel modules and firmware? Most of what I read looks like old info on these X86 Tablets. Is there anything new to help set them up, what works on them and what don't? I'd like to start with display and sound. Move to touch. Mostly all I care about and a working battery meter.
Thanks PS still boots Windows 10
Click to expand...
Click to collapse
I managed to boot 32 bit legacy install on a baytrail 2-in-1 tablet with intel atom z37355 ( Notion Ink Cain 10) alongside windows 10. Though the processor supports x64 as it says, the installation always failed, but 32 bit installation succeeded ( to my surprise). I booted up with fully functional touchscreen, wifi, detachable keyboard,wireless usb mouse etc.
Bugs:
No autorotate ( a third party seems to allow me to manually rotate though).
Power and volume hardware buttons dont work ( no volume either).
System seems to freeze if left alone after a while ( however, playstore downloads that were stuck are resumable after force shutdown are start).
Battery indicator stuck at 100% ( am trying to calibrate using some random battery app, but i really doubt it would work)
I'm gonna install kernel aduitor and check if the system freeze after a while can be fixed ( some guy said changing kernel governer to interactive would fix it) later.
All above bugs are known i guess. Just putting it in here so someone with baytrail tablet googles it can see it in one place