Bootloop on the 2nd start - Remix OS for PC

I installed Remix OS 3.0 on my HP 17G105NL without creating a separate partition of C. The first boot was successful end: I set my personal account, enabled the Play Store, downloaded a few apps... The day after, ROS goes bootloop on the animated logo. Then I restarted the PC, start Windows, delete the installation using the exe in RemixOS folder and tried with a new installation. When this was finished, I try to start it, but it makes me the same trick with bootloop. The strange thing is that if I try to run it from USB in Resident or Guest mode there is no prob (but I will not start it from USB because the drive is 2.0). The write speed of my HDD is over 100 MB / s. If you have any ideas, I would be happy to hear them. Thank you all guys.
(Sorry for my bad english)

Related

Remix OS on a Cherry Trail Tablet?

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.

Installing on a PIII-1000

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.

[UPDATE] Remix OS for PC update 3.0.102

The first update for Remix OS for PC (Android Marshmallow) has been released. It's available for download here.
After this update, future updates will be available through OTA.
Your feedback was instrumental in guiding our work.
Check out the release notes below.
Release notes
Remix OS for PC version: 3.0.102
Release date: August 2, 2016
Fixed more Wi-Fi issues related to Broadcom wireless chipsets
Support hard disk partition mount allows you to access other files and folders
Support for future updates via OTA
Added feature where recent apps will be shown on the top line of apps in the App Drawer
Added “App Store” to Remix OS
RemixOS_Jason said:
The first update for Remix OS for PC (Android Marshmallow) has been released. It's available for download here.
After this update, future updates will be available through OTA.
Your feedback was instrumental in guiding our work.
Check out the release notes below.
Release notes
Remix OS for PC version: 3.0.102
Release date: August 2, 2016
Fixed more Wi-Fi issues related to Broadcom wireless chipsets
Support hard disk partition mount allows you to access other files and folders
Support for future updates via OTA
Added feature where recent apps will be shown on the top line of apps in the App Drawer
Added â??App Storeâ? to Remix OS
Click to expand...
Click to collapse
Thank you my good sir. Will this keep our data?
Sent from my on Z00A using XDA Labs
Good news! I hope this update solve my problems with my Broadcom BCM43142 chipset!
edgerch said:
Good news! I hope this update solve my problems with my Broadcom BCM43142 chipset!
Click to expand...
Click to collapse
It did solve my wifi problems
Will this retain our data or has to be fresh install?
This is great! The only problem I was having was the WiFi problem with the 3.0.101 (I was using the Ethernet, which worked great) and after upgrading it to the 3.0.102 version, the WiFi is working great. I will mention that I am running it on my HP Mini 110-3135DX from a 16GB USB 2.0 Flash drive and so far everything works pretty good and smooth. Thanks.
Still can't get play store working at all on this version...
Edit: Also still can't handle my gtx 560ti by default but seems to be slightly better. Still freezes after a few screen transitions though.
Edit 2: System time is still getting knocked out by an hour when booting back in to Windows 10. I had this on Lollipop too.
Others are getting the play issue. Any way I can help?
can't wait to try this update
stayloa said:
Still can't get play store working at all on this version...
Click to expand...
Click to collapse
I never use the app.
This method only works if you haven't already used the app to activate the Play Store
Instead go to settings/experimental features and enable debug terminal console. Then I use ALT&F1 to open debug command line and type :
pm disable com.jide.apppolicy
pm enable com.google.android.syncadapters.contacts
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.partnersetup
pm enable com.google.android.feedback
pm enable com.google.android.syncadapters.calendar
pm enable com.google.android.gsf.login
pm enable com.google.android.backuptransport
After type pm list packages -d
You should see only the one you disabled
Press ALT&F7 zto exit terminal
IMMEDIATELY REBOOT
Hi,
I require URGENT help.
Originally i had a 64GB e-mmc on my windows tablet, which had a single partition of 57GB named C:\ & Windows 8 came pre-installed on it. Rest 5GB disk was kept as Recovery by OEM.
I updated to Windows 10 last year.
Now, a month back in order to run Remix OS beta, on my laptop.
i used Windows in-built disk management tool, to shrink the C:\ drive, & took 15GB from it & set it as a new partition, & named it E:\ drive.
& disabled Secureboot in BIOS, & then installed the beta Remix OS on the E:\.
As the Remix OS beta, would not load from Windows boot menu from BIOS, i booted Windows 10 & formatted the E:\.
Today, I downloaded the "Remix OS 3.0 for PC", & through it's installation file installed the Remix OS.iso on the (E:\) 15GB partition.
After the setup of remix os (running in windows) was complete, it asked for reboot.
After reboot,
It immediately shows me a screen:
showing: GNU GRUB version 2.02~beta2.
& listing RemixOS as the only option to boot.
[Windows 10 was nowhere to be found.
Apparently Windows Boot Manager had be over-written by GNU GRUB.]
Anyways, After selecting the remix os option, it kept loading till, it shows the language setup screen.
Then i'm unable to select the English language (keyboard doesn't work).
I have to force reboot, after clicking power button for 10 seconds.
But again GNU GRUB screen comes, & only shows RemixOS as an option to boot.
I created a bootable usb drive of Partition Magic Free .iso, & tried loading it from the BIOS menu, where it showed me two options:
1. Windows Boot Manager
2. UEFI: USB USB hard drive (# pendrive)
Upon selecting the 2nd option, nothing happened. it showed the same BIOS screen.
I then created the Windows Recovery flash drive, from another Windows tablet, on the same Pen drive (after formatting it).
Now surprisingly, the laptop succesfully booted from the Windows Recovery pendrive.
But the repair tool, did not solve my problem.
So i went into command prompt (which is built-in on the Windows Recovery drive)
went into DISKPART>list disk> selected disk 0> list partition> #selected the E: partition.
gave CLEAN command,
Which apparently cleaned the whole 64GB disk, rather than cleaning the E:\ partition.
So now, i require your HELP, in getting back my important files which were in my C:\
So that after recovering them, to my external drive.
I can load a fresh Windows 10 on this 64GB e-mmc card.
Kindly tell me, which software can i use to recover data from my CLEANED disk ?
Sweeeeeeeet. Wifi is now working. and it has already mounted all my drives :good::laugh:
lollyjay said:
I never use the app.
This method only works if you haven't already used the app to activate the Play Store
Instead go to settings/experimental features and enable debug terminal console. Then I use ALT&F1 to open debug command line and type :
pm disable com.jide.apppolicy
pm enable com.google.android.syncadapters.contacts
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.partnersetup
pm enable com.google.android.feedback
pm enable com.google.android.syncadapters.calendar
pm enable com.google.android.gsf.login
pm enable com.google.android.backuptransport
After type pm list packages -d
You should see only the one you disabled
Press ALT&F7 zto exit terminal
IMMEDIATELY REBOOT
Click to expand...
Click to collapse
The problem is bigger than using a standard method unfortunately. Something fundamentally isn't working with a few peoples' installs. We've all tried that method (which is my default go to) but nothing works...
Yup, just tried the 102 version hoping my WiFi will work...still nothing. It seems I don't have the lucky chipset. I have a RTL8192CU.
Oh well...maybe with the next update.
Hi. I'm new here. So pls bear with me. I downloaded remix os yesterday in India.
I want to know how to check the version. Because wifi is still not working for me. Ethernet is.
It's showing that the version 3.0.102 has solved the wifi issue. I have a Broadcom wifi adapter. Please help.
osr.arora said:
Hi,
I require URGENT help.
Originally i had a 64GB e-mmc on my windows tablet, which had a single partition of 57GB named C:\ & Windows 8 came pre-installed on it. Rest 5GB disk was kept as Recovery by OEM.
I updated to Windows 10 last year.
Now, a month back in order to run Remix OS beta, on my laptop.
i used Windows in-built disk management tool, to shrink the C:\ drive, & took 15GB from it & set it as a new partition, & named it E:\ drive.
& disabled Secureboot in BIOS, & then installed the beta Remix OS on the E:\.
As the Remix OS beta, would not load from Windows boot menu from BIOS, i booted Windows 10 & formatted the E:\.
Today, I downloaded the "Remix OS 3.0 for PC", & through it's installation file installed the Remix OS.iso on the (E:\) 15GB partition.
After the setup of remix os (running in windows) was complete, it asked for reboot.
After reboot,
It immediately shows me a screen:
showing: GNU GRUB version 2.02~beta2.
& listing RemixOS as the only option to boot.
[Windows 10 was nowhere to be found.
Apparently Windows Boot Manager had be over-written by GNU GRUB.]
Anyways, After selecting the remix os option, it kept loading till, it shows the language setup screen.
Then i'm unable to select the English language (keyboard doesn't work).
I have to force reboot, after clicking power button for 10 seconds.
But again GNU GRUB screen comes, & only shows RemixOS as an option to boot.
I created a bootable usb drive of Partition Magic Free .iso, & tried loading it from the BIOS menu, where it showed me two options:
1. Windows Boot Manager
2. UEFI: USB USB hard drive (# pendrive)
Upon selecting the 2nd option, nothing happened. it showed the same BIOS screen.
I then created the Windows Recovery flash drive, from another Windows tablet, on the same Pen drive (after formatting it).
Now surprisingly, the laptop succesfully booted from the Windows Recovery pendrive.
But the repair tool, did not solve my problem.
So i went into command prompt (which is built-in on the Windows Recovery drive)
went into DISKPART>list disk> selected disk 0> list partition> #selected the E: partition.
gave CLEAN command,
Which apparently cleaned the whole 64GB disk, rather than cleaning the E:\ partition.
So now, i require your HELP, in getting back my important files which were in my C:\
So that after recovering them, to my external drive.
I can load a fresh Windows 10 on this 64GB e-mmc card.
Kindly tell me, which software can i use to recover data from my CLEANED disk ?
Click to expand...
Click to collapse
this is so sad ...
i suggest that you install a files recovery app to your usb
if you install anything to your drive your files may be overwritten ...
so be careful .
GOOD LUCK
salimtn said:
this is so sad ...
i suggest that you install a files recovery app to your usb
if you install anything to your drive your files may be overwritten ...
so be careful .
GOOD LUCK
Click to expand...
Click to collapse
Sadly, my Samsung ATIV 500T's BIOS doesn't let me boot from any USB recovery drive, other than the Windows Recovery USB drive (created from another Windows 10 installation)
My Solution
osr.arora said:
Sadly, my Samsung ATIV 500T's BIOS doesn't let me boot from any USB recovery drive, other than the Windows Recovery USB drive (created from another Windows 10 installation)
Click to expand...
Click to collapse
I had the same problem. Windows wasn't deleted, it just didn't have a grub2 entry.
To reboot into Windows, I pressed "c" to access the grub2 bash command-line, and then I typed exit, which loaded me into the bios menu for my Nextbook Flexx 10.1 Windows tablet. In the bios menu, I was able to select the Windows EFI Boot Manager, and continue into Windows.
Hopefully, this solution works for you.
When you boot back into Windows, if you are like me and are unfamiliar with editing grub.cfg files to add a Windows entry, grub2win is a fairly simple UI for setting up a grub2 bootloader. And from within the grub2win UI, you can change the EFI Firmware Boot Order.
Sorry, I'm new on RemixOS. Is there any app or settings to get the update via OTA? I enabled the unstable system option, but I can't get any message. Or should I update downloading the zip from Jide?
hello I have a tablet lenovo miix 3 and I wanted to install in hard top. I have already removed Windows. But when I moved over Remix OS , boot the first he said: you need to load the kernel first...
How do ?
how can I update from 2.0.402 to 3.0.102.
I couldn't find any OTA updates in settings.....

[Need Help] Blinking Cursor after install.

Hello, I was trying to install Remix OS (i686 version) on my Acer aspire one without dualboot by booting from USB drive and installing with a INSTALL=1 key.
After the 'reboot to android-x86' at the end of the installer Remix OS boots up and everything works as far as I checked.
But after rebooting the system only thing I get after BIOS is blinking underscore cursor.
I have tried to install Remix OS with different file systems (fat, ext4), with and without GRUB but still I get only the blinking cursor.
Is it something I am doing wrong or is it a bug with the installer?
Sorry to drag this thread up, but did you ever manage to solve this? I'm having a right nightmare trying to get this installed... Constantly a flashing cursor after install - doesn't seem to matter what way I create the boot disk.
It runs fine stand alone off the USB, or running it after the install has finished... but never after a reboot.
Blinking cursor
I was tryed run remix OS from flashdrive on Chuwi Hi10 tablet with same result, flashing cursor. I was then try run remixOS with log mode and then look into logfile. There was some information about missing drivers for MMC internal storage. I actualy didn't get over that problem. Maybe it is same problem with your PC.

Need Help With Remix OS Dual Booting

So basically I did the dual boot thing where I had to partition my hard drive and install Remix OS in there, just that stuff. So after restarting my laptop, the dual boot screen came up, I was given the option of Windows 10 or Remix OS so I clicked Remix OS. After that it loaded up everything was working, I signed into my gmail account and all that good stuff. Basically, everything was working as it should. So then something came up in real life and I shut my laptop. I come back and hour later and open my laptop and I'm greeted to the regular Windows 10 user login screen, but I just guessed that Remix OS used the same lock screen. However when I logged in, my regular windows home screen came up. Now it's just like Remix OS has disappeared from my laptop even though it's installed. I have tried to fix it for 2 days now and can't find any fixes. So here are my questions: 1. How come when I opened my laptop was I back on Windows 10 and where did Remix OS go? 2. How can I fix this?
Anyway, if there's any information you need to help me out, just ask and I will answer you.
Thanks!
Possibly an issue with the way you shut it down ? Do a reinstall which will also prompt you to uninstall the previous version 1st. Should not be a major issue. My dual boot shows up every time.
I reinstalled mine probably 3-4 times to see how it worked on external HDD and the main computer.
My only issue is tethering. Doesn't connect when I'm in RemixOS. That's my only internet access for about 3 years now.
By the way, I did not install it on a separate partition. Try to install as a computer app on the same partition as your windows. It will create all the files needed and also delete all of them when you uninstall. Just make sure you put the .iso file somewhere you can get to easy. I extracted mine into the download folder where the zip was also. Seems to work just fine.

Categories

Resources