https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
most time we solve this by deleting recreating data.img
I hope that helps you
ecksdeeay said:
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
Click to expand...
Click to collapse
I did that. But this is all I could take a picture of. http://i.imgur.com/7rseNNe.jpg I have no clue what any of it means.
I opened it in guest mode.
imadlatch said:
most time we solve this by deleting recreating data.img
I hope that helps you
Click to expand...
Click to collapse
I dont know how to do that. I cant seem to be able to open the ISO that was in the zip file I downloaded. However, I formatted my flashdrive and used the included tool to reinstall Remix OS. It didnt help.
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
ecksdeeay said:
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
Click to expand...
Click to collapse
Here's what I got doing that. http://imgur.com/a/SL1rQ
I never got the second exit prompt. I just got the errors in this https://i.imgur.com/sGo2EQ5.jpg image over and over.
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
ecksdeeay said:
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
Click to expand...
Click to collapse
androidboot.selinux=permissive is present there by default. Im using a lenovo ideapad y510P with core i7 4700MQ, 8 Gigs of RAM and dual Nvidia GT 755M.
incognitonk said:
Nvidia GT 755M.
Click to expand...
Click to collapse
Nvidia is the problem then. ...
ecksdeeay said:
Nvidia is the problem then. ...
Click to expand...
Click to collapse
Really? Oh well, guess Im gonna be playing the waiting game then.
Thanks for everything up until now.
Search as I think there are work arounds @incognitonk
incognitonk said:
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
Click to expand...
Click to collapse
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Hit thanks if it help
mdezazrock said:
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Click to expand...
Click to collapse
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
incognitonk said:
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
Click to expand...
Click to collapse
I don't know the blinking error solution , my friend also have that same problem , but there is a easy solution for resolution -
Root remix os , open any rooted browser , go to system folder , then open build.prop , edit the file , just add a line at the end
"ro.sf.lcd_density=150"
Write that line without quote , save build.prop , and change the number between 140 to 210 , see which one looks better on your monitor , have fun exploring remix ☺
Related
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Conixcit said:
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Click to expand...
Click to collapse
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
HypoTurtle said:
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
Click to expand...
Click to collapse
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Conixcit said:
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Click to expand...
Click to collapse
I think I had what you're describing and toggling the autohide fixed it (i think there was a mismatch between the setting value and the right click value).
That being said it might be better to try the 32bit version on your device; it should be easier on resources.
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
ZiQn3zZ said:
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
Click to expand...
Click to collapse
I totally agree but 64 bit version is the only version that supports EFI ,
Conixcit said:
I totally agree but 64 bit version is the only version that supports EFI ,
Click to expand...
Click to collapse
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
HypoTurtle said:
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
Click to expand...
Click to collapse
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Conixcit said:
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Click to expand...
Click to collapse
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
updesh94 said:
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
Click to expand...
Click to collapse
where is exactly "build.prob" file.
I'm using Ubuntu
Conixcit said:
where is exactly "build.prob" file.
I'm using Ubuntu
Click to expand...
Click to collapse
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Already done that. Not helps
Letme try that file editing thing
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Can't find that build.prob file....
Conixcit said:
Can't find that build.prob file....
Click to expand...
Click to collapse
You're dual booting with ubuntu, right?
If so then just mount the system.img and you'll see it righg there.
mkdir rossystem && mount -t ext4 system.img rossystem
or if your using a system folder then it should be just in there.
I had the same problem, I fixed it by adding in build.prop
ro.remixos.no_wallpaper=true
I recently ordered an Onda obook10 dual booting tablet (Android 5.1 +Win10) from GearBest, and received it a week (and a half) ago. It is the V5 version (9th and 10th digits of S/N). Booted into Android at first, swiped around a little, and then left it alone for when I was free. Day before, I booted into Windows, and seeing that an account was already set up, hit the factory reset option (Options: remove all personal files, normal wipe (not thorough)). It rebooted, said it was resetting, then got stuck at 5% for a half hour. I then did a hard reboot, and it starting resetting again. I repeated this a few times, with different waiting periods, but it always got stuck at 5%. I wanted to see what was going on, so I opened the OS selector menu and tried to boot into Android, but that put the device into a bootloop, and it's stayed that way since. I downloaded the recovery WinPE from their website, and tried running it; all went well until the last step (installing the install.wim file), which succeeded, but when the batch file tried to set the boot options/flags, it threw an error about not being able to access D:, and failed. Tried making the recovery USB and installing multiple times, but it failed every time. I then tried Gandalf's WinPE image, which booted, and tried using imagex to install the .wim file to C: manually, as detailed here. This failed too.
I'm at my wits' end, honestly. I have no idea what else to try. There's another WinPE file available for download, but it's dated only a couple of weeks after the one I already have, so I'm hesitant to download it if there's any other option (I have very low bandwidth, it would take me at least two days). Also, it's hosted on Baidu, and the download times out after about an hour, and cannot resume. If anyone could give me any ideas, or point me towards a guide I haven't found yet (I've read all the relevant ones I could find on the Onda forums, but please post them anyway if you think they would be helpful), that would be great.
What would be perfect is if someone could upload, or point me toward a system dump/partition clone of at least the Windows partition and boot partition; I have the tools needed to flash those.
Thanks in advance.
EDIT: I managed to fix this a while ago, and have put the procedure somewhere in this thread, but since people keep popping up every now and then asking for it, I'm going to put this here so it's easier to find. Copied from later in the thread, here, and modified to be more general:
This uses slightly modified commands from the Onda firmware install script, and will result in a COMPLETE WIPE and reinstall of Windows - all the files on the Windows partition will be lost. This SHOULD work for anyone whose Android is working but Windows isn't, but I can't guarantee that. I can't even guarantee that this will work (though I am pretty sure it will) - I have not tested it completely. If you can, you should make a backup of anything files on the internal storage, just in case. As always, read the whole procedure before starting.
NOTE: If your Android isn't working, you need to install that first - get the Android file from the Onda Baidu page (look for the one for OBOOK 10 (not SE), with the appropriate V1, V2, V3, V5, or V7 code - you can find your code by checking the serial no. on the back of your device, the 9th and 10th characters), and follow the instructions in the document included in the zip - they are pretty straightforward, but you'll have to use Google Translate, as they're in Chinese. This MUST be done before the Windows procedure, because the Android installer wipes the entire disk.
If you want, you can make the procedure easier for yourself and save all the commands below to a text file, put it in the root folder of the USB before booting, and open it in Notepad by using:
Code:
notepad D:\textfile.txt
Or whatever name you give it. That way, you can copy paste them all easily.
Boot into the Windows installer, and when the command window appears, press Ctrl-C. After a few seconds, it will ask you if you want to terminate batch job, type 'y' and press enter. You now have a command prompt to work with.
You have to delete your Windows partitions first. The below partition numbers should be correct, but you should make sure first by running "list partition" and checking if it corresponds with the last 3 partitions, which should be your Windows partitions - their sizes are usually 128 MB, 35 GB, and around 800-1024 MB, and their types are Reserved, Primary, and Recovery (DO NOT delete the Primary partition at the beginning of the disk). DO NOT delete the Unknown partitions - those are Android's.
Code:
diskpart
sel disk 0
sel partition 14
delete partition
sel partition 13
delete partition
sel partition 12
delete partition
Your Windows partitions are now completely gone, so you'll have to recreate them first.
Change directory to the images folder.
Code:
cd D:\images
Get filesizes of .wim files to create partitions accordingly:
Code:
for %I in (Install.wim) do set INSTALL_SIZE=%~zI
set /a INSTALL_SIZE_MB=%INSTALL_SIZE:~0,-6%
for %I in (Winre.wim) do set RE_SIZE=%~zI
set /a RE_SIZE_MB=%RE_SIZE:~0,-6%
if %RE_SIZE_MB% LSS 430 (set /a RE_SIZE_MB=480
) else (
if %RE_SIZE_MB% GEQ 430 (
if %RE_SIZE_MB% LSS 680 (
set /a RE_SIZE_MB=%RE_SIZE_MB%+320
) else (
set /a RE_SIZE_MB=%RE_SIZE_MB%+1024
)
) )
Make sure to preserve all the spaces and brackets in the above code.
Enter diskpart, run the following:
Code:
sel disk 0
create partition msr size=128
create partition primary
shrink minimum=%RE_SIZE_MB%
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
You should now have 14 partitions when you do "list partition".
Exit diskpart.
Now for the actual installation:
Code:
md w:\recycler
md R:\recovery\windowsre
DISM /Apply-Image /ImageFile:"D:\images\Install.wim" /ApplyDir:w: /Index:1 /Compact /ScratchDir:w:\recycler
xcopy D:\images\Winre.wim r:\recovery\windowsre /y
Create boot entry:
Code:
bcdboot w:\WINDOWS
If that doesn't work, then:
w:\WINDOWS\SYSTEM32\BCDBOOT w:\WINDOWS
Set recovery environment:
Code:
w:\windows\system32\reagentc.exe /SetREImage /Path R:\recovery\windowsre /target w:\windows
And that's it! You should have both OSes operational now.
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
EDIT: I've put the guide in the first post.
Flashing Help
SirVer said:
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
Click to expand...
Click to collapse
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
[email protected] said:
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
Click to expand...
Click to collapse
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Widows swith icon
SirVer said:
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
[email protected] said:
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
Click to expand...
Click to collapse
Is the partition still there, or is that just free space you're seeing? For me, the partition was gone, with unallocated space in its place. If the partition is still there, then your job is relatively simple.
1. Make a WinPE recovery drive from another Windows machine, or just use a custom one (like Gandalf's WinPE, Google it).
2. Boot into it from the BIOS menu.
3. Load a command prompt.
4. Type "diskpart" (no quotes). Wait until you get a prompt like: DISKPART>
5. Enter the following commands:
a. select disk 0
b. list partition
c. select partition xx (where xx is the number of the Windows partition. If it's not labelled, it'll be the one about 36 gigs in size.
d. assign letter=c
e. exit
6. Now just run "bcdboot C:\Windows"
7. Reboot, and you should see Windows in your BIOS menu once more, and the button should pop up on Android as well.
If the Windows partition is not there, and it's just free space, things become more complicated. You'll need to get your hands on the Windows installer image. There is an older version on the Onda website (December 2015) that should do the job - or rather, there's a link to their Baidu account. You can find the more recent version in their account as well. The issue is that Baidu doesn't allow you to download files that large without installing their crapware. I got around it by registering an account and some URL-fu, but it's a PITA, especially if you have a slow connection. There's a Yandex mirror somewhere, but I'm not at home, so I don't have the link right now. I'll post it when I get back. EDIT: Here it is.
After you get the files, DON'T install it; it might wipe your Android install (did for me). There's an issue in their install script that made the command that hides the Android partitions from getting deleted not work. What I did was terminate the automatic install, and selectively apply the relevant portions of the script manually. You could probably do the same, but it could take you a while; took me two days and a bunch of background reading. If you're used to messing with Windows installs though, it'd probably be a cakewalk for you. I'd prepare some instructions for you, or even try and write a script myself using that one as a base, but I have exams right now, and I wouldn't have time for at least a week. If you haven't figured it out by then, just ask, and I'll do it.
Sent from my LG-D855 using Tapatalk
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Frezza said:
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Click to expand...
Click to collapse
You can enter the BIOS menu by connecting a keyboard and holding down ESC while booting up.
Sent from my LG-D855 using Tapatalk
Help
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
[email protected] said:
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
Click to expand...
Click to collapse
I don't remember exactly what it's called, but I think it was the second menu entry - Boot <Something>. In that menu, you should see your USB drive USB EFI device or something like that listed - it might also show the manufacturer name (it showed my USB as a Sandisk). If you don't see it, you may have made a mistake when making the bootable USB - try it again while reading the instructions on Gandalf's site carefully. If you used Rufus to make the bootable, maybe try Unetbootin this time - it worked fine for me.
P.S. In case you meant boot into the file - you can't. You have to write it to a USB drive first. Instructions are on the same site you downloaded it from.
Sent from my LG-D855 using Tapatalk
Can I install Windows 7 by Gandalf on this Tablet?
Frezza said:
Can I install Windows 7 by Gandalf on this Tablet?
Click to expand...
Click to collapse
Install? Maybe, but you wouldn't have any of the necessary drivers, so touch and WiFi and stuff wouldn't work. However, you can download the drivers and try installing them, which might work, though it probably won't since they're made for Windows 10.
Sent from my LG-D855 using Tapatalk
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Frezza said:
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Click to expand...
Click to collapse
Depending on certain things, you may be able to just run the installer without doing anything extra. Are you able to boot into Android? Open a CMD window, and run the following commands:
1. diskpart
2. sel disk 0
3. list partition
Post the output of these here. A screenshot will also be OK.
Sent from my LG-D855 using Tapatalk
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
betsesv said:
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
Click to expand...
Click to collapse
When you extract that, you'll get a bunch of files and a DOC in Chinese explaining the procedure to make the recovery disk. Once you've made that, a WARNING before you boot into it: it will automatically open a CMD and start a delay counter, after which it will start the install automatically. Since this might break the Android side, you'll have to cancel it with Control-C in that delay period, which will give you a normal CMD to work with. You can use this to run the commands from my last post. If you want to be extra safe, also download a different WinPE recovery file (like Gandalf - actually you should download this anyway, it has some useful tools you might need later on), and boot into that instead. Depending on the output of those commands, you may be able to just run the automatic installer without worries.
Sent from my LG-D855 using Tapatalk
obook20 crashed
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
alexander137 said:
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
Click to expand...
Click to collapse
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
SirVer said:
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
alexander137 said:
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
Click to expand...
Click to collapse
Just press it down for a long time, at least 10 seconds, that'll do it. For some reason it takes a really long time to force shutdown. If that doesn't work, then there might be an issue with your hardware. Also try typing the "exit" command - it should put you into the BIOS menu directly.
Sent from my LG-D855 using Tapatalk
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
ethansky said:
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Click to expand...
Click to collapse
Try to add "nomodeset" instead of "nouveau.modeset =".
nomodeset might work, but it's highly unlikely.
I've made a guide for these kind of problems today: http://forum.xda-developers.com/remix/remix-os/solution-problems-booting-remix-os-dual-t3466027
Vioner said:
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
Click to expand...
Click to collapse
I have looked for that option in my bios and I couldn't find it. I forgot to mention in my original posting that I had my Windows reinstalled with because the hard drive failed. I don't believe that I have the option to boot to the UEFI so I wonder if that has to do anything. I tried putting the "androidboot.swrast=1" code after the kernel line in the GRUB line editor thingy and I got it to boot. It's a bit unstable and the screen tends to tear when I move a large window around. The only problem now is how to make it permanent. I tried editing the file that was mentioned in some guides but it doesn't seem to stick.
tomekumb said:
Try to add "nomodeset" instead of "nouveau.modeset =".
Click to expand...
Click to collapse
I have tried both of the commands and it still hands at the Android root part. Are there any other commands or combination of commands that could work? I don't have an option in my bios to disable my gtx 960m and there isn't an option to boot to the UEFI. I wonder if the Windows reinstall due to a hard drive failure has something to do with it. Thanks in advance!
hi folks, thanks to @joesnose we can now enter the yoga book's bios/uefi. you might say 'thank you' to him for this!!!
more about his tries can be found here: https://forum.xda-developers.com/thi...ncept-t3565366
to do so just follow the following steps:
1. start adb shell
2. type the following commands
(alternatively you can also enter the commands in TWRP's terminal)
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
!!!as always, be very careful what you do in the bios - the chance for creating a stylish and expensive chopping board is quite high!!!
unfortunately, it seems like you always have to type those commands to enter the bios.
danjac said:
hi folks, thanks to @joesnose we can now enter the yoga book's bios/uefi. you might say 'thank you' to him for this!!!
more about his tries can be found here: https://forum.xda-developers.com/thi...ncept-t3565366
to do so just follow the following steps:
1. boot twrp
2. go to advanced and open the terminal
3. type the following commands
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
!!!as always, be very careful what you do in the bios - the chance for creating a stylish and expensive chopping board is quite high!!!
unfortunately, it seems like you always have to type those commands to enter the bios.
Click to expand...
Click to collapse
About entering the bios. On my YT3P after entering this command just once I am then able to boot bios from twrp reboot screen. This is not working for you danjac?
Also if you make the changes in the bios to get usb keyboard working you can also disable fast boot which allows you to press f7 at boot which allows entry to bios. gets you to boot device selection and pressing esc will take you to other bios options.
And everyone should give thanks to @danjac for trying this on the yogabook.
Sent from my Nexus 6P using Tapatalk
really tnx @danjac , helpful i will try this later
how ever did you flash twrp as your default recovey?
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
razielvamp said:
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
Click to expand...
Click to collapse
try entering commands from adb shell with tablet on android.
Then on your pc copy and paste
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Sent from my Nexus 6P using Tapatalk
razielvamp said:
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\[COLOR="Red"] x00[/COLOR]" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
Click to expand...
Click to collapse
no 'space'!!!!
there is/was one in the original thread (see the last x00) ...so it also was the reason why it didn't work for me from adb shell. presumably i just ignored the space when typing it manually in twrp...
now it also works from pc/adb...
I corrected the OP! thanks for reporting back!
Ok. I get BIOS but OTG keyboard not working. Halo keyboard too.
I can use only vol up, vol down and power buttons. But I need "ESC" button too, in other case I can not escape submenus.
I got!
long press VolUP = return.
But still do not understand how select usb device in boot order. It seems like BIOS not support OTG function, so how can I change for boot from USB drive when it not detected?
razielvamp said:
Ok. I get BIOS but OTG keyboard not working. Halo keyboard too.
I can use only vol up, vol down and power buttons. But I need "ESC" button too, in other case I can not escape submenus.
I got!
long press VolUP = return.
But still do not understand how select usb device in boot order. It seems like BIOS not support OTG function, so how can I change for boot from USB drive when it not detected?
Click to expand...
Click to collapse
Device manager......
System setup........
android.......
Uefi secure BOOT=disable.
South cluster configuration.......
Usb configuration.....
default drd CONFIG=hostmode
Usb VBUS=on.
that's it save changes and exit. Next time you boot to bios you can use keyboard connected via otg to use bios. You can also select next boot device in bios boot manager.
If you want to be able to interupt boot process to select boot device also disable fast boot under boot category in bios . This will mean you get a black screen with progress bar on power on but allows use f7 to select boot device.
After booting another os from usb it often takes 3 boots to get back to android, don't panic.
Sent from my Nexus 6P using Tapatalk
joesnose said:
Device manager......
System setup........
android.......
Uefi secure BOOT=disable.
South cluster configuration.......
Usb configuration.....
default drd CONFIG=hostmode
Usb VBUS=on.
that's it save changes and exit. Next time you boot to bios you can use keyboard connected via otg to use bios. You can also select next boot device in bios boot manager.
If you want to be able to interupt boot process to select boot device also disable fast boot under boot category in bios . This will mean you get a black screen with progress bar on power on but allows use f7 to select boot device.
After booting another os from usb it often takes 3 boots to get back to android, don't panic.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hello Guys and Girls,
Sorry for my english, which is not my mother tongue.
Just to say that after reading a lot in XDA folder (thanks to the people who provided how to root/use TWRP and access Bios)
I managed to boot from USB key but I have a acpi-bios-error ( no matter what I changed in the bios related to acpi) while intalling windows 10 32/64 bits.
I would like to know if someone met this issue and solved it somehow ?
By any chance, is there someone (who was able to boot to W10) who can tell which software they use to make their usb bootable ?
I gave up for the moment (I spent too much time on it, need to rest lol)
Thank you for reading my post,
Sweetgeex said:
Hello Guys and Girls,
Sorry for my english, which is not my mother tongue.
Just to say that after reading a lot in XDA folder (thanks to the people who provided how to root/use TWRP and access Bios)
I managed to boot from USB key but I have a acpi-bios-error ( no matter what I changed in the bios related to acpi) while intalling windows 10 32/64 bits.
I would like to know if someone met this issue and solved it somehow ?
By any chance, is there someone (who was able to boot to W10) who can tell which software they use to make their usb bootable ?
I gave up for the moment (I spent too much time on it, need to rest lol)
Thank you for reading my post,
Click to expand...
Click to collapse
With windows I always get the acpi bios error! I have tried many bios options but obviously with caution. Always the error. I keep trying with my "win to go" usb stick.
This error is also quite generic so its hard to know what is causing it.
Sent from my Nexus 6P using Tapatalk
Many Thanks for the answer,
I guess this will be a blocking issue for everyone.
I "heard" on other forums that we might need to upgrade the bios, I don't think it will be possible from Android side.
(I saw there is a tool on Lenovo support site)
Sweetgeex said:
Many Thanks for the answer,
I guess this will be a blocking issue for everyone.
I "heard" on other forums that we might need to upgrade the bios, I don't think it will be possible from Android side.
(I saw there is a tool on Lenovo support site)
Click to expand...
Click to collapse
Or possibly the current bios needs dumping and editing to allow "hidden options". I did see some pics during searching of a similar cherry view bios but there was a "select os" option that does not show in mine.
Sent from my Nexus 6P using Tapatalk
joesnose said:
Or possibly the current bios needs dumping and editing to allow "hidden options". I did see some pics during searching of a similar cherry view bios but there was a "select os" option that does not show in mine.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
---------- Post added 25th April 2017 at 12:09 AM ---------- Previous post was 24th April 2017 at 11:56 PM ----------
Sweetgeex said:
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
Click to expand...
Click to collapse
Just a check, did you go under system-setup >> south cluster configuration >> SCC configuration >> SCC eMMC Support & SCC SD Card Support (internal and SDcard)
here we can set ACPI mode/PCI Mode or disable
I'm afraid that it will remove android, but it might be a key issue.
Sweetgeex said:
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
---------- Post added 25th April 2017 at 12:09 AM ---------- Previous post was 24th April 2017 at 11:56 PM ----------
Just a check, did you go under system-setup >> south cluster configuration >> SCC configuration >> SCC eMMC Support & SCC SD Card Support (internal and SDcard)
here we can set ACPI mode/PCI Mode or disable
I'm afraid that it will remove android, but it might be a key issue.
Click to expand...
Click to collapse
Sorry missed your post there.
I have tried many things in bios so its hard to remember them all. I think i tried pci mode and also disabled.
Also it might be good if people post what they are trying which could be then added to the first post.
And, i was changing one option at a time then reverting the changes after failed boot, there is a possibility that multiple changes are needed.
Sent from my Lenovo YT3-X90F using Tapatalk
No worries,
Are we agreed that if the installation succeed, it will remove android, right ?
Sweetgeex said:
No worries,
Are we agreed that if the installation succeed, it will remove android, right ?
Click to expand...
Click to collapse
agreed.
Like I said I was mostly trying with my "win to go" usb drive. That is a complete win 10 os on a usb stick, boots just fine on other pc's I have.
I would not recommend full install at the moment for two reasons. 1) who knows what kind of driver issues/problems there will be. 2) would returning to android work if whole device was overwritten, losing bootloader etc.
Sent from my Nexus 6P using Tapatalk
Alright, thank for clearing this up.
I guess that for the moment, we need to set the issue with ACPI, I will keep looking to other topics and forums here and there.
If I found anything, I will post it here.
Many thanks for your answers.
Boot with linux??
Good morning, has anyone tried doing this but with any linux distro? i'm not sure which one is compatible with our device
joao1979 said:
Good morning, has anyone tried doing this but with any linux distro? i'm not sure which one is compatible with our device
Click to expand...
Click to collapse
I have booted several versions of linux and android x86 on my yogatab3pro.
Would like to hear your findings.
on yt3p all need the nomodeset flag in order to boot. This of course means no hardware accelleration.
for me no touch , no sound and no hardware accelleration but they will boot.
Oh and there is some cherrytrail targeted distros. One by linuxium and another called xjubutab.
For reference.
https://forum.xda-developers.com/th.../ubuntu-yoga-tab-3-pro-proof-concept-t3565366
Sent from my Nexus 6P using Tapatalk
unfortunately i didn't find anything useful for us but i´ll keep searching for a solution, i don´t know if it´s possible to update or downgrade an android bios (i´m not an expert on this matter)
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
xxXPANDER said:
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
Click to expand...
Click to collapse
GRUB bootloader installed?
Complete guide here.
jwoegerbauer said:
GRUB bootloader installed?
I saw the link. Followed the steps. Stuck after step 5 in the link and cant proceed to step 6. I dont think grub is the issue here?
Click to expand...
Click to collapse
I'm having the same/similar problem (no choice to install is presented)
Context: I use a USB stick with refind to find and boot an android-x86_64-9.0-r2.iso that I have already imaged onto /dev/sda8 (imaged using the linux dd command).
When I use refind and select to boot /dev/sda8, android-x86 boots to the console shell prompt, and then seconds later starts a live run GUI screen. The boot process never stops to present me with a choice of install versus live run, as it should do. And that is my problem.
I'm looking for a workaround. I can switch between console and live GUI using Ctrl-Alt-F1/F7, so I can do command line stuff as root . Anything I can do to kill the live GUI and start the disk installer mode from the console? Name of installer program? Name of GUI is not Xorg or X or anything usual, it seems .
PS: If I knew which distro is underlying android-x86_64-9.0-r2.iso , maybe I could look up some keyboard salute to select installer mode during the boot?
one workaround found
@xxXPANDER, the following may be of interest to you, and @jwoegerbauer, too:
I managed to get the installer going by booting the iso from refind with one trick applied. Details: From refind gui boot, select the iso partition, and then use the hit-key-F2-twice method to edit the refind command line and append the phrase INSTALL=1 and then hit ENTER to boot.
At that point the installer mode came up, rather than the android live GUI mode, and I selected to install according to my plan, onto the empty partition /dev/sda9 with ext4.
I had a surprise that the installer put the data section of the installation on sda6:/android-9.0-r2/data/ (about 180MB), but the rest of the installation on /dev/sda9. Not sure how the installer figured out that I had tried before to do an alien-rpm-based install onto an existing ub18 on sda6. The image I booted was on sda8, and the destination I set was sda9. But still /data ended up on sda6:/android-9.0-r2/data/ . Weird.
Upshot: you need to shoehorn INSTALL=1 into the boot recipe, one way or another. I think the whole problem we're having should be considered a bug, though. It is almost as if the iso checks whether it is being booted from grub2 or not, and if not, jumps straight into live mode. This certainly caused me at least two full days worth of trouble so far, and I see no documentation of this strange behavior. At the very minimum there ought to be some documented keyboard salute that prevents this behavior during a standalone (non-grub2) boot. Maybe someone will disagree, but AT LEAST there should be prominent documentation, say on page https://www.android-x86.org/installhowto.html