Hi everyone,
Unless someone has any idea, I've given up on this. I have tried every version of the installations for an old HP Pavillion PC (32bit). I either get the OS not being detected, blinking light of doom, infinite search for the OS, splash screen of doom and I'm sure more that I don't recall.
I even tried installing it using the INSTALL=1 DEBUG= to install it on a drive all by itself, but it only detects the USB slots and not the hard drive! I've already provided feedback to the Jide team that I'd like to see a true LiveCD to hard drive installation process like every version of Windows and the Linux distros where you can just boot to a stick and either run it in a guest mode with option to install or just an installer process that can install it to a clean drive.
Of all the systems (64 bit and 32 bit / laptops vs desktops), I can get it running from one stick consistently. I'd rather install it a drive and be done that way. Hopefully a future version will do it simply.
This might be a long stretch, but you might check and see if the disk is still reading as "active". I've tried installing Remix OS on a flash drive using their Windows tool via Windows 10, but noticed the USB drive would just disappear. Going to Disk Management/Partition Manager shows the USB drive as inactive, and works no problem when it's active again when I restart the system. If you're using the entire hard drive, try using a tool like GParted Live CD/USB and see if your disk drive is active.
Ya, I've tried that too because initially that did happen and I figured once I solved it that would sort the problem out but no dice.
BladeMaverick said:
This might be a long stretch, but you might check and see if the disk is still reading as "active". I've tried installing Remix OS on a flash drive using their Windows tool via Windows 10, but noticed the USB drive would just disappear. Going to Disk Management/Partition Manager shows the USB drive as inactive, and works no problem when it's active again when I restart the system. If you're using the entire hard drive, try using a tool like GParted Live CD/USB and see if your disk drive is active.
Click to expand...
Click to collapse
this is one way I can revive my Acer Aspire One AOA110 with 8GB SSD. up for interest and attention
Related
I think I've made a huge mistake.
I just wiped my device in TWRP because the last CM Nightly I installed was acting up.
I went into TWRP, wiped and factory reset. I then rebooted and went into TWRP again.
I wanted to install CM 9.1, which I copied onto my 64GB SanDisk Ultra, and I was thinking to just flash it from the external sd.
I read somewhere on xda that I needed to maybe use a smaller SD card and have the format in FAT32, which I did, but TWRP still does not recognize them.
I am currently stuck with TWRP v2.3.1.0, no way to flash a new rom from a blank internal memory or an external memory.
I tried updating SDK and the most updated drivers for the device through the Device Manager and use "adb push" or "adb sideload" but the device is not recognized.
Can someone give me some kind of suggestion to solve this situation.
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
squidlr said:
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
kgal said:
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
Click to expand...
Click to collapse
Windows 8 is a bugger to get drivers working properly.
Try and use a windows 7 machine or a friends laptop or try the following instructions.
Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Ubuntu is a linux based Operating System, and can be used to do most things Windows 8 does, sometimes worse, sometimes better. So in this case, it's less trouble to connect an android device to a linux OS such as Ubuntu, as it can recognize a telephone without having to install drivers.
If you want to give it a go, you can install Ubuntu alongside Windows 8.
http://www.makeuseof.com/tag/tired-of-windows-8-how-to-dual-boot-windows-ubuntu/
And then install Fastboot and ADB:
http://putokaz.wordpress.com/2012/08/29/install-adb-and-fastboot-android-tools-in-ubuntu-via-ppa/
But, I'd stick to Windows and follow the advice of Flumpster if you're not too confident installing a second operating system.
I can and have knowledge of installing another OS to run alongside Windows.
I use VirtualBox to run Mac OSX and Android. Can I run Linux on VirtualBox and do the process through that?
I am not quite sure what I should do after disabling Driver Signature Enforcement on Windows 8...
Yes, you can install Linux in a virtual machine - give it a try. If the device is still not recognized via OS running in the virtual machine, you can then always install to your hard disk and try that route.
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
jamesthedisciple said:
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
Click to expand...
Click to collapse
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
kgal said:
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
Click to expand...
Click to collapse
Just a quick thought after re-reading your first post, I'd try a smaller sd card (16 or 32GB). I have heard of the larger faster cards giving some people problems.
Solved!
After trying to install Linux using Ubuntu 13.04 and getting more errors (something with the UEFI vs Legacy Boot installation), I decided to retry and find the original Windows drivers for the TF201.
I found one through Softpedia, downloaded it, used the "Have Disk" option when installing the yielded "Transformer" device in the Device Manager and sideloading the new CM 10.1 Nightly onto it.
Works like a charm!
Thanks everyone for the support!
I installed Remix 2.0 (32-bit) onto my Dell Mini 10 (1012) netbook. So far, everything seems to be detecting perfectly, except for one thing. The touchpad is supposed to be multi-touch but it doesn't function as such. It is worth mentioning that, on Windows, I required special driver software to be able to utilize the multi-touch capability. Considering I've seen some Chromebooks automatically have their multi-touch touchpads detected, I figured Remix would do the same for my Dell. That doesn't seem to be the case.
Anyway, if any of the Jide developers are reading this, I have the driver software available for you. Follow this link. The software was developed for Windows 7 by Elantech (ELAN Microelectronics Corp.) but is being supplied by Dell. The one the Dell Mini 10 has is a Capacitive Touchpad (Smart Pad).
Hi
I can't get passed the splash screen on my Dell mini. Was your install straight forward?
Janoflan said:
Hi
I can't get passed the splash screen on my Dell mini. Was your install straight forward?
Click to expand...
Click to collapse
Are you trying to run off USB, or install onto the internal hard drive? Make sure you're using the 32-bit version, as the 64-bit wouldn't boot for me.
FYI, as you may know, the Mini doesn't like any HD video, so unfortunately very few Android games will run properly.
Thanks for getting back to me. I tried installing on hard drive via Linux using the most recent beta. I've upgraded the ram to 2gig and installed an ssd but not sure if that would cause issue.
Janoflan said:
Thanks for getting back to me. I tried installing on hard drive via Linux using the most recent beta. I've upgraded the ram to 2gig and installed an ssd but not sure if that would cause issue.
Click to expand...
Click to collapse
I used 2GB RAM and an SSD as well. So that shouldn't be an issue. But the procedure I used was different than simply installing it onto the hard drive with another computer.
Don't install using a separate operating system. It doesn't seem to work that way. You need to load it onto a USB and install onto the hard drive using the Mini. The procedure for this is, when you come to the Guest/Resident mode screen, you press TAB, then add "INSTALL=1" to the end of the grub command. This will bring up the android-x86 install menu, which will allow you to install the OS onto the hard drive the same way as using another computer. Make sure the SSD is formatted to NFTS and is completely empty prior to doing this. You can alternatively try formatting it to EX4 instead.
When prompted, install GRUB, do not install GRUB2, install debug (wont work w/o idk why). Unfortunately, you will be left with the maximum internal storage after the install, so you need to go back and use the IMGTools procedure to enlarge data.img to whatever size you want your internal storage to be.
Thats what worked for me, anyway.
That worked brilliantly, thanks very much. Have you had any success with dual boot after intalling Remix first?
Janoflan said:
That worked brilliantly, thanks very much. Have you had any success with dual boot after intalling Remix first?
Click to expand...
Click to collapse
Haven't tried it. But if you use a NTFS format, you should easily be able to shrink the partition after install. You would also need to edit the GRUB menu to choose which OS you want to boot with, which I have no experience doing. However, I know the new beta version of Remix does have an install tool that does this for you. So if you were intending to dual boot Remix/Windows, then it is possible to install Windows first.
First the issues. I was not able to figure out how to set it up to where I can install Remix OS on my chromebook's SSD instead of having to use a USB stick. I also wasn't able to figure out why running the ISO installer tool that comes with the most recent download (yesterday) didn't work. I used it on a 32GB PNY USB flash drive, but after going into the legacy boot menu on my Chromebook, and selecting my USB stick to boot from, it was not able to find an operating system. Instead, I used Linux Live USB Creator (LiLi). I manually selected the Remix OS ISO that came with the download, and installed it to my USB stick. My chromebook recognized it immediately as a bootable OS. It even gave me the options for guest mode, and write mode. I chose write mode. The only downside to this is not being able to choose how large the partitions should be. Either way, it installed successfully.
The awesome parts. It recognized and works uniformly with my chromebook's touch screen and touch pad. Zero issues. It even recognizes some touch-pad short cuts like two-finger scrolling, etc. It doesn't recognize some of my keys on the keyboard itself, like volume up/down, and brightness up/down, but this is easily managed at the task bar. I also tested Star Wars: Galaxy of Heroes to see if games would be sluggish running on a USB stick. I don't know about all games, but that one in particular ran as though it was on my Nexus 7. Super smoothly, with no issues. Aside from it being a bit sluggish running apps for the first time, (it frequently asked if I wanted to wait, or to force close Facebook and others - hitting wait works), I am very impressed with the experience. It's everything I could hope for in a beta android desktop OS! :good: :good:
PS, I'm actually running it right now as I type this.
I got it to install on my Acer R14 with a triple boot, windows 10, ubuntu, remix os. If you use universal usb installer and install directly to a NTFS partition on your hard drive you can use RMXtools to make the data .img whatever size you want. I did it for 50GB and have installed alot of apps and i still have 48GB left. I really like this OS.
Well I tried ubuntu on my chromebook for a while, but wasn't feeling it. I would have to put it on in order to install Remix OS to a hard drive no?
No just use universal usb installer and select non-linux installation and install directly to your ntfs drive. The expand the data file with RMXTools to whatever size you want.
rsktkr1 said:
No just use universal usb installer and select non-linux installation and install directly to your ntfs drive. The expand the data file with RMXTools to whatever size you want.
Click to expand...
Click to collapse
How do I run Universal USB installer from Chrome OS then?
ryfly65 said:
How do I run Universal USB installer from Chrome OS then?
Click to expand...
Click to collapse
Make your usb bootable with Rufus.
Been using it from USB for weeks now I'll try the Linux USB tool, would be amazing to get this running on the hdd. Does you're touchpad work??
Edit: just read it does work but hasn't for me, been needing my wireless mouse
Sent from my Nexus 9 using Tapatalk
Is it possible to boot a linux live usb and install remix os on the ssd with Gnome disks?
There has got to be some variation in components with revisions of the C720P, because no OS I have tried to boot on mine has supported the mouse other than Gallium. If I install the GalliumOS kernel on Debian it works fine, but no idea how I would do that with Android. Your touchpad really just worked huh? Not for me, not in the version of RemixOS I downloaded from the Jide site last night, nor in the hacked edition or whatever it's called here on XDA.
My laptop Asus X8AIJ very old since 2005.....
settup on HDD,,,non USB
Win10 64bit + Remix os 2.0.0.205 with rooted ,,,,very good...but i can not settup display for as well
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.
is have asked in many forums but didn't got anything working.
so the whole story is, I own a Windows tablet from 2015 or something. recently I tried to install android x86 on it just for fun. I installed the BlissOS 14 x86 version and it ran great only that the tablet is overheating a lot and reboots. Now I want to go back to windows but what's going on is that the tablet is not detecting the windows bootable USB drive, it is only detecting the android bootable USB drives. every time I try to boot a windows USB it goes back to bios. i tried dozens of windows bootable tools and even changed between a bunch of drives nothing is working. please guys help me, I want my windows tablet back.
Update: I'm sorry to all who brainstormed on this, I am an IDIOT. I was trying to boot 64-bit windows into the 32-bit processor. Now everything works fine, Sorry Again.
What tablet is it?
amitrahi04 said:
is have asked in many forums but didn't got anything working.
so the whole story is, I own a Windows tablet from 2015 or something. recently I tried to install android x86 on it just for fun. I installed the BlissOS 14 x86 version and it ran great only that the tablet is overheating a lot and reboots. Now I want to go back to windows but what's going on is that the tablet is not detecting the windows bootable USB drive, it is only detecting the android bootable USB drives. every time I try to boot a windows USB it goes back to bios. i tried dozens of windows bootable tools and even changed between a bunch of drives nothing is working. please guys help me, I want my windows tablet back.
Click to expand...
Click to collapse
Use Rufus software(https://rufus.ie/) to create bootable USB.
Bro,
Try Rescartux !
Burn it into a USB drive, then booting it!
Find a menu that "fix boot-stuff for windows"
Try every menu related to fixing windows Boot!
If that didnt give a Budge, U could try HirenBoot .