So, I done this again, I was trying to install remix os. Since my pen drive was full of documents and the spare one was not at home, I tried installing it on my hdd and now I'm ****ed. I did it the "unofficial" was using easybcd 2.3 .
The whole process is given below. 1 - made a 18 gb partition. 2 - copied content of the iso into the drive. 3 - made a new entry in easybcd. 4 - rebooted pc and the problem started,
The problem is that I don't get the option to choose between Windows or remix os. I can't boot from my windows disk because the keyboard is not recognized by the system. Can't choose between guest or resident mode. Since my keyboArd is not working, it boots into residence more after 20-30 seconds. It gets struck on the remix os logo. Been there since then.
Don't known what to do, maybe have to take my system to an engineer.
Any help will be appreciated. Thanks !
Hmm..
Thats wierd... I tried the easybcd options ones or twice..
If you add boot ISO.. then your first default boot should still be Windows
Perhaps a different Keyboard? its win8... So a mouse should work if you have the metro bootloader
Anyway... If you have Windows Install Disk... you can use Recovery console..
https://neosmart.net/wiki/recovering-windows-bootloader/
A better/quicker? solution.. Hirens Bootcd.. Mini WinXP... then edit BCEdit
But whats your hardware?
Can you access grub? When you get option quest/resisdend Try hitting keyboard : Tab (try adding DEBUG=1 to boot parameter)
Goodluck..
Thanks but
Thanks for the reply. But the problem is that I can't access grub. My keyboard doesn't work when I'm at choosing whether I want to use best mode or residence mode. I wait for 30 seconds and then it automatically boots into residence mode. When the remix os logo appears my keyboard starts working. I can turn on caps and num lock. But what's the use of it ? Also, I have a p/s 2 keyboard. I have asked my father to bring a usb keyboard. If that works , I would boot into guest mode that seems to be working for other people. I would also try changing the default boot system to Windows.
Related
Hello Ive got a bit of a problem actualy a few with my pipo U1 Pro
I installed CWM V6.o.3.1 and rebooted fine, pipo boot image was normal, then i installed from ext SD card Decontaminat V3.1
after install the screen was Split at 2/3 and touch orintation was off with buttons in wrong corners
so i read alot found change in build.prop (ro.sf.hwrotation=270) from 270 to 0 and reinstalled form ext sd card
all it fixed was position of touch screen the image of ui was still split 2/3 and out of rotation.
i reinstalled CWM fron ext sd card reboot ant the cwm recovery is straigt on the vertical and the android shows in center of screen, but ther is a fine line showing where the screen was split in the os.
after reboot the os is still split 2/3 image i have to us the show touch function to navigat the touch field to make thins work
i had TNT pipo u1 pro.img installed before and was rooted worked fine but latly had a few minor problems with it so i desided to chand up a bit.
second problem is i cant get ADB , android studio or rkbatch tools to find my tablet, usb debugging is on, tried the load from adb sideload function in cwm
im running linux mint 17 added udev.rules rebooted every thing many time s swapped usb plugs cords you name it.
as it is the tablet works but the ui is buggered up and touch is off
any help would be verry appricated
mike
May be bricked now ?
I have the pipo stuck in what might be a boot loop?
just says decontaminate with a split screen on bootup shows pipo image then goes to decontaminate screen and nothing.
lsusb shows device { Bus 002 Device 009: ID 2207:0006 }
shows Android device in file manager But Error unable to mount android unable to open mtp device
pushing the buttons '' esc, +vol then power gets nothing.
pushing +vol, power gets nothing
incerting usb and pushing +vol gets nothing
only thing gets anything is push and hold power, CWM is not working cant boot to cwm
tried a bootable sdcard still no boot
was a nice Tablet till decontaminat screwd the screen up
got recovery yeah !!!!
found a way into the cwm recovery through adb.
i added a line into the file here.
/yourusername/.android/adb_usb.ini
its a hidden file added a simple line as root user
0x2207
saved file and rebooted computer.
will post again if i can recover the pipo.
buggered
had total access to the pipo.
i used flash_image to install freaktbs ryley rom for the pipo u1 pro.
now im stuck in a worse position. the kernal.img was not for the pipo.
he was playing with a another tablet and left its kernel.img as kernel.img and had pipo kernel as 1kernel.img
so im stuck with no touch support on the screen and its not defaulted to usb debug mode.
i can see the button acking to allow debug when i connect to usb on linux but no access to touch.
also the rom didnt have any tools for adb installed in recovery /system/bin.
no adb shell support.
only access is adb ls /
to read files and push pull commands.
any ideas on how to edit the default.prob make it stick through reboot and get it to debugg after reboot ?
this sucks MR.RYLEY built a bad rom I was almost into my pipo again.
my guess is the decontaminat rom was using a similar kernel to ryley to get the screen all buggered up.
Hello there,
I was trying to boot up Remix OS but was facing some problems.
When I try to install Resident Mode or Guest Mode, it says -
Code:
Checking Data Partition....
ANDROID
And it gets stuck there.
I am running Windows 10 Pro 64-bit at the moment. Anyway I can install?
Check Your PC Legacy Or EFi, Choose ISO according to your PC.
Disable secure boot in bios setting.
If you boot via pendrive so format pendrive format 32
Also Check :-
check this link : https://www.youtube.com/watch?v=aYWY7NadNzU (Dual Boot Method )
Ash110 said:
Hello there,
I was trying to boot up Remix OS but was facing some problems.
When I try to install Resident Mode or Guest Mode, it says -
Code:
Checking Data Partition....
ANDROID
And it gets stuck there.
I am running Windows 10 Pro 64-bit at the moment. Anyway I can install?
Click to expand...
Click to collapse
Can you boot in to guest mode? If successfull, when you boot in Resident mode, the Os have to create a data file which contains apps and setting. Please wait for 5 min, after that you will boot into Remix Os.
android os takes a lot of time in the first boot and this os some kind of big so you'll need to wait buddy
tamkien said:
Can you boot in to guest mode? If successfull, when you boot in Resident mode, the Os have to create a data file which contains apps and setting. Please wait for 5 min, after that you will boot into Remix Os.
Click to expand...
Click to collapse
No, neither Resident nor Guest are working. Both get stuck there
Moonitta121 said:
android os takes a lot of time in the first boot and this os some kind of big so you'll need to wait buddy
Click to expand...
Click to collapse
Oh, I've been waiting for 30 hrs xD
I have the same issue. I run a computer with intel i5 and a nvidia 970. I read somewhere that remix OS has hard time with nvidia graphic cards at the moment
Same here with a AMD E350 Netbook
Hey guys! Got it running by using this guide
http://forum.xda-developers.com/showthread.php?t=3328350
Hi All,
Just rooted the android portion of this dual boot device but upon booting to the window os I was presented with a blue screen, a sad face and text
"your pc ran into a problem and needs to restart. We'll restart it for you.
...error: Inaccessible Boot Device"
Anyone come across this before and able to fix it?
upon reboot it does go into a repair mode but have tried everything but still cannot get it to go into windows.
Any help appreciated.
Should I reinstall the windows partition. A link to good online tutorial would be great?
Thanks
I have a Dell Laptop running windows 10 and boots via UEFI. I have installed Remix OS beta (64 bit version) several times on the HDD using the Remix program available when downloading from their website. Apart from one occasion only, Remix usually hung and I remained patient, waiting for a version that would work. That happened with the latest version (2.0.403) i.e Remix finally works and the OS boots up normally. However (as is usually the case with life in general) whilst Remix works, when selecting windows from the Grub loader it says that it cannot find the path to windows and I cannot boot into windows. I appreciate that this is a Android forum but this problem is specific to Remix I think and some entry in the grub loader and as such I turn to this forum in case anyone has any ideas so that I can fix the grub loader or whatever and be able to boot into windows - I am of course happy that I can boot into Remix but I also still need my windows!
Thanks a lot in advance
Andrew
did you installed them in 2 separate hard drive?
and your computer use bios or uefi.
if it is uefi you should check if the old windows boot loader is still here.
and if it is 2hdd you should boot directly to windows hard drive. by changing your boot settings.
tailslol said:
did you installed them in 2 separate hard drive?
and your computer use bios or uefi.
if it is uefi you should check if the old windows boot loader is still here.
and if it is 2hdd you should boot directly to windows hard drive. by changing your boot settings.
Click to expand...
Click to collapse
Thanks. They are on 1 hdd and it is UEFI. I don't know how to check if old boot loader is there but I have tried the repair option on the windows CD/USB including repair MBR without any luck. So I think the old boot loader is gone and replaced by Grub.
Ajd34b said:
Thanks. They are on 1 hdd and it is UEFI. I don't know how to check if old boot loader is there but I have tried the repair option on the windows CD/USB including repair MBR without any luck. So I think the old boot loader is gone and replaced by Grub.
Click to expand...
Click to collapse
to see if the bootloader is still here you should go to your uefi and boot option.
it is generaly holding del while booting to acces it.
you should see in boot windows boot loader and grub.
you should be able to switch them
if your windows installation is not gone.
tailslol said:
to see if the bootloader is still here you should go to your uefi and boot option.
it is generaly holding del while booting to acces it.
you should see in boot windows boot loader and grub.
you should be able to switch them
if your windows installation is not gone.
Click to expand...
Click to collapse
Thanks. On the Dell laptop it is F12 and there is an option under UEFI BOOT to choose Windows Boot Manager but selecting this goes to the Grub Loader. I need somehow to edit the Grub loader to point it back to where windows is residing unless Remix has deleted the windows partition??
Ajd34b said:
Thanks. On the Dell laptop it is F12 and there is an option under UEFI BOOT to choose Windows Boot Manager but selecting this goes to the Grub Loader. I need somehow to edit the Grub loader to point it back to where windows is residing unless Remix has deleted the windows partition??
Click to expand...
Click to collapse
yes if you used command lines to install remix ,it can format the boot loader partition...
i hope this will help you.
http://www.howtogeek.com/howto/33433/restore-the-windows-boot-loader-after-an-ubuntu-update/
edit; here win 10
https://blog.d0zingcat.xyz/2015/09/28/Windows/How to repair the EFI Bootloader in Windows 10/
tailslol said:
yes if you used command lines to install remix ,it can format the boot loader partition...
i hope this will help you.
http://www.howtogeek.com/howto/33433/restore-the-windows-boot-loader-after-an-ubuntu-update/
edit; here win 10
https://blog.d0zingcat.xyz/2015/09/28/Windows/How to repair the EFI Bootloader in Windows 10/
Click to expand...
Click to collapse
Many thanks although this did not work. Clearly something went wrong when Remix was installed but I cannot understand what exactly. Anyway, I feel that I should not trouble this forum further since it seems like a problem now more to do with a corrupted Windows or Grub Boot loader issue than a Android issue. What I was hoping in particular was that someone had had the same issue after installing Remix and how therefore they dealt with it but it doesn't seem that this is the case. Looks like I am the only (un)lucky one!
Thanks again
Andrew
Ajd34b said:
Many thanks although this did not work. Clearly something went wrong when Remix was installed but I cannot understand what exactly. Anyway, I feel that I should not trouble this forum further since it seems like a problem now more to do with a corrupted Windows or Grub Boot loader issue than a Android issue. What I was hoping in particular was that someone had had the same issue after installing Remix and how therefore they dealt with it but it doesn't seem that this is the case. Looks like I am the only (un)lucky one!
Thanks again
Andrew
Click to expand...
Click to collapse
UPDATE: I placed a Windows 7 installation disk in the laptop and turned it on (as I had read that trying to use the bootfix from a USB may not work). The laptop then started to boot windows 10 normally and by-passed the Grub loader! I cannot explain how this is possible but once Windows booted I uninstalled Remix. I rebooted and the Grub loader was gone. I then installed Remix 3 (as I am a sucker for punishment) and the new Grub loader works fine - the laptop now boots into Windows & Remix!
Thanks for those who replied
Regards
Andrew
Hi,
I had my pc setup to dual boot with Win 10 and Remix on separate partitions on my HD for a month now.
HP Pavilion x2 12-b020nr
Intel Core M3,
4 GB RAM,
128GB SSD
I tried to install the OTA update yesterday and it repeatedly failed.
Booted into Windows and uninstalled Remix. Then reinstalled and everything went well. It asked to install the update - that worked and went well. Reinstalled all my Android apps etc.
Today - when the boot screen pops up - it won't boot into Windows. I get the option and I select it - but it boot loops back to the select screen. You can do this forever. But if you select remix - it boots into Remix just fine.
Did a windows recovery boot - tried a system restore (with little hope) and it fixed nothing. I have linux boot USB's but not sure what to look for or how to find/edit the boot loader. Familiar with grub 1 but know that is obsolete.
Any ideas other than wipe/reinstall?
Thanks in advance,
Wan
Okay - figured a way out...
I can boot into my Win10 by interrupting the boot with
Esc,
then F9 (Boot Device Option)
Boot from EFI File (Instead of the default OS Boot Manager)
Select File to Boot = EFI
Boot
Select a File = bootx64.efiOkay - so from there I used the Remix uninstall tool.
Then I deleted and reinstalled the partition for Remix
Then I reinstalled Remix.
Everything now is back to working.
Hope that helps anyone else.
Good Luck,
Wan