It works fine in Guest Mode, but if I choose Resident Model at the Remix OS boot screen, it just goes to a blank screen. I don't even get to the Remix OS splash or the "A N D R O I D".
I know there is nothing wrong with this boot media, because it works on my Dell PC and MacBook Air.
Do I need to change something in the boot options by hitting Tab on Resident Mode. It looks like I can tweak some options there.
Of course I have the Chromebook set up to boot from media. In fact, I run Linux in a partition via chrx on the device (seldom use Chrome OS),
Thanks.
Having real trouble with this actually. While I said the media works on my Dell PC and MacBook Air, it actually doesn't. They're both frozen on the Remix OS screen.
So maybe my media isn't good enough, but shouldn't it be fast enough:
https://primenow.amazon.com/dp/B00YFI1EBC?m=A9T23OKX5KJF0&psc=1&ref_=pn_spp_4_img_A9T23OKX5KJF0
I've tried writing the image with the Remix tool on a PC, the Gnome Startup Disk Creator on Linux, as well as Rufus on a PC. They all fail in the following manner:
On my Pixel 2: They either cause a reboot loop before the splash screen or sit on a blank screen before the splash screen.
On my Dell PC and MacBook Air: They are stuck on the splash screen.
This is only in Resident mode. They all start fine in Guest mode!
Anyone? Thanks!
I guess there's not a lot of activity here huh?
So I solved my own problem. The issue was the USB stick. I tried it on two more USB sticks and it installed in Resident Mode fine. The difference between the ones that worked and the one that didn't us that the one that didn't work was USB 3.0. The ones that worked were USB 2.0.
Go figure...
I'm having a similar problem. But my USB should be fine, it's a SanDisk Extreme Pro (one of the fastest available). It worked with previous versions of RemixOS, but since the Marshmallow release haven't been able to get past the pulsing RemixOS screen in Resident mode. Like you Guest mode works fine.
BenjaminNYC said:
Having real trouble with this actually. While I said the media works on my Dell PC and MacBook Air, it actually doesn't. They're both frozen on the Remix OS screen.
So maybe my media isn't good enough, but shouldn't it be fast enough:
https://primenow.amazon.com/dp/B00YFI1EBC?m=A9T23OKX5KJF0&psc=1&ref_=pn_spp_4_img_A9T23OKX5KJF0
I've tried writing the image with the Remix tool on a PC, the Gnome Startup Disk Creator on Linux, as well as Rufus on a PC. They all fail in the following manner:
On my Pixel 2: They either cause a reboot loop before the splash screen or sit on a blank screen before the splash screen.
On my Dell PC and MacBook Air: They are stuck on the splash screen.
This is only in Resident mode. They all start fine in Guest mode!
Anyone? Thanks!
Click to expand...
Click to collapse
Is the REMOUNT_RW=1 parameter included in the kernel line? If so, it will take time for the system.sfs file to extract itself into a file called system_dev.img! If this is not the case, the new Linux Kernel may not work with your setup...
Could I get the specs of your system?
@gregbacchus Could I get the specs of your system aswell?
@moman2000 I have tried on a number of different computers. It used to work on all of them: 2011 Macbook Pro, 2015 Macbook Pro, homemade pc.
Note, it runs fine in Guest mode, it's just resident mode that doesn't work. I have left it pulsing over night to see if it was just something slow.
Related
Sorry if this is in the wrong forum but I didn't find a Pipo subforum.
My Pipo W3F keeps rebooting exactly like this fellow's https://www.youtube.com/watch?v=Dz_qsKDAq3A
Can anyone help? Thank You.
Has no one seen any tablet reboot like this at all, so you could at least point me in some direction?
I found out some things that may help you guys to help me.
This unit is Dual Boot between Android 4.4 and Windows 8.1 and used an Intel Bay Trail processor. In the American Megatrends bios I can choose to override current default boot settings which are ( UEFI: Built in EFI Shell) to UEFI OS and then Android will boot normally with all my data. What I cannot get to boot is Windows 8.1 no matter which option I try. If your Pipo custom OS Boot manager does not load ( the screen that lets you choose between Android and Windows on startup) you are supposed to hold down the Volume Up (plus) button while booting and the boot manager will load. I've used this trick before this rebooting happened once when the boot manager did not load and it worked fine. Now this trick won't work at all. I believe perhaps somehow this boot manager or the bios function that loads it is in error. I could be wrong, just my best guess.
I even tried a copy of Windows 8.1 on USB and was able to tell the bios to load the USB from startup. My hope was that it would recreate me a Windows Boot Manager and allow me to get into Windows at least by booting through the ISO, or try to repair windows boot problems but all it does is give me a blue screen that says it ran into an error, is collecting some info and restarts only to go into this same loop. It nevers loads the ISO setup properly to even try to fix Windows boot problems.
Does this help you guys ?
Hi, I have a Lenovo flex 3-1130 and I created a UEFI USB stick with the regular creator with the latest version. I have turned off secure boot and legacy mode is NOT enabled. Whenever I try to boot the laptop off of the usb stick it gives me the normal grub menu (this problem happens with both Resident and Guest) and after I select one it will say:
mmc0: Unknown controller version (3). You may experience problems.
Detecting Android-x86.... found at /dev/sdb1
After this it changes to a backlit black screen (on resident) and on guest mode it gives me a screen with no backlight on (power still on) I really want remix OS to work so does anyone have any tips? Also removing the "quiet" option in grub shows a bunch of stuff before "Detecting Android-x86" but also goes to a black screen afterwards.
EDIT: Also I do not have a NVidia card I think it is intel hd.
chewyboy0 said:
Hi, I have a Lenovo flex 3-1130 and I created a UEFI USB stick with the regular creator with the latest version. I have turned off secure boot and legacy mode is NOT enabled. Whenever I try to boot the laptop off of the usb stick it gives me the normal grub menu (this problem happens with both Resident and Guest) and after I select one it will say:
mmc0: Unknown controller version (3). You may experience problems.
Detecting Android-x86.... found at /dev/sdb1
After this it changes to a backlit black screen (on resident) and on guest mode it gives me a screen with no backlight on (power still on) I really want remix OS to work so does anyone have any tips? Also removing the "quiet" option in grub shows a bunch of stuff before "Detecting Android-x86" but also goes to a black screen afterwards.
EDIT: Also I do not have a NVidia card I think it is intel hd.
Click to expand...
Click to collapse
Ive tried everything with no luck.. Im using a lenovo
Sent from my SM-N920T using Tapatalk
Hey community, after trying to install Remix OS (x86, x64 (original and rooted) on my USB pen drive, USB Harddisk and internal Harddisk, i'm always stuck in the screen where you can see the green Android mascot with the "Android-x86" text under it and the loading screen of Remix OS with the text "Upgrading...". The progressbar loads fully, goes to "starting" and then back again to the green android screen.
Got an old (~4 years) Asus Laptop without USB 3.0 support, tried enabling and disabling Legacy boot in BIOS.
Someone got the same problem or knows a solution?
bump for same problem.
Try boot remix is with nomodeset parameter in grub first and give it some time, reboot remix os again with default grub parameter and see if it works,
Hope that help
arts821 said:
Try boot remix is with nomodeset parameter in grub first and give it some time, reboot remix os again with default grub parameter and see if it works,
Hope that help
Click to expand...
Click to collapse
Didn't work
Did i do the folllwing instructions correct?
Reinstalled Remix OS on harddrive, got to the screen to select "resident mode", added "nomodeset" before "quiet" in the parameter, booted it up and waited ~8 hours (i'd gone to work). Still at bootloop. Forcefully shut down, removed parameter and waited a night long...
what u mean with install to harddrive and u can select resident mode?
are u sure u do the correct install method?
and try install 32 bit version remix os
arts821 said:
what u mean with install to harddrive and u can select resident mode?
are u sure u do the correct install method?
and try install 32 bit version remix os
Click to expand...
Click to collapse
I want to install Remix OS on my external HDD (WD Elements 2TB). After installing over Windows and booting to Remix OS, you can select between Resident and Guest mode (guest mode only on USB I think). Resident mode saves every changes you made and guest doesn't.
I only followed the normal installation method delivered by the installer exe.
I'm going to install now this newest version of Remix OS first trying the normal install procedure, then i'm going to look at these 3 (1, 2, 3) threads for more help.
I'll let you know if and how I did it.
I installed it on my Acer AOA110 with 8GB SSD inside, and still stuck on boot after nomodeset option, should I upgrade the drive or is there another way I can successfully boot it? ZIF drives are pretty rare these days. this isnt 2009.
After trying different possibilities I couldn't get my laptop run Remix OS. Installing on internal, external harddrive and usb, I get still stuck on bootloop...
I recently attempted to install in parallel Remix OS 3.0.101 64bits with Windows 10 on a Asus Tablet T100h (Intel atom). Everything worked fine during HDD installation (separate 30GB fat32 partition) , rebooted into Remix Os and the device screen went black after showing formatting data partition.
I tried everything possible to restart the tablet (including tearing it apart and manually disconnect the battery). Nothing worked. The current state is: fully charged, when long press power button the led blink three times amber and six times white. The camera led remains off.
Any idea for unbricking highly appreciated.
It's just RemixOS' stupid grub (bootloader) management. I don't understand why Jide would need to modify boot entries that much. Not only they set remix as first priority, but they screw up original Windows entry as well -.-
And to add more, remix screws up the Windows clock each time -.- When I installed Remix, it screwed up my Windows boot manager entry and I had to fiddle with it. (recommend EasyUEFI for that)
Now to solve your problem:
Turn your device on and keep pressing escape button on keyboard (if you have it). Boot menu will appear. Try to boot Windows from that menu. It might not start because Remix tends to screw that entry up (shame on you Jide).
If you can't access the boot menu, then enter bios and use boot override feature. I don't remember the key combo for BIOS on T100, but you should be able to enter it using just the tablet keys - google it.
When you finally manage to boot Windows, uninstall Remix, then reboot to check if Windows boots well again.
If it does, then install RemixOS again, but I recommend using Android-x86 Installer app for that (availible here on XDA, search).
This installer works everytime, nevee messes up existing boot entries and handles 32bit UEFI just fine.
If I helped you, hit the thanks button
AND DON'T USE FAT32 FILESYSTEM. It's obsolete and slower. You can install Android safely on NTFS partitions.
Sent from [email protected] 4
Thank for the ideas BUT the device does not even make it to POST. Literally a brick.
Sent from my ONE A2001 using XDA-Developers mobile app
Maybe it is caused by the strange EFI approach used with Baytrail tablets?
I own a Teclast tablet and read a lot about the necessity to use 32bit EFI even when using a 64bit OS while trying to install Ubuntu on my tablet. Some people created 64Bit Ubuntu versions with 32bit EFI.
Using 64bit EFI e.g. by trying to install 64bit Windows bricked the devices.
Have you tried to start the machine by pressing Power and Volume Down buttons on the tablet? It's for entering Boot Menu.
It's just hard to believe that this bricked the device. Installing an OS never bricks BIOS...
Using 64bit efi image on a 32bit efi machine will only render the installed system useless, but it don't do anything to the BIOS.
Also you can try pressing Power and Start buttons for 10 secs to hard reset the device.
Sent from [email protected] 4
Yes. Long pressing power button generate only a change in led blinking pattern. Nothing else.
Ventricle said:
Have you tried to start the machine by pressing Power and Volume Down buttons on the tablet? It's for entering Boot Menu.
It's just hard to believe that this bricked the device. Installing an OS never bricks BIOS...
Using 64bit efi image on a 32bit efi machine will only render the installed system useless, but it don't do anything to the BIOS.
Also you can try pressing Power and Start buttons for 10 secs to hard reset the device.
Sent from [email protected] 4
Click to expand...
Click to collapse
Sent from my ONE A2001 using XDA-Developers mobile app
mklmkl said:
Maybe it is caused by the strange EFI approach used with Baytrail tablets?
I own a Teclast tablet and read a lot about the necessity to use 32bit EFI even when using a 64bit OS while trying to install Ubuntu on my tablet. Some people created 64Bit Ubuntu versions with 32bit EFI.
Using 64bit EFI e.g. by trying to install 64bit Windows bricked the devices.
Click to expand...
Click to collapse
This might serve as an explanation! The question now is... How I rewrite the EFI?
Sent from my ONE A2001 using XDA-Developers mobile app
If you can't access bios nor boot menu, than you probably won't access anything.
@no_body one more question - is the screen lighting up at all when you try to power the device up?
Sent from [email protected] 4
Check e.g. this forum http://forum.xda-developers.com/showthread.php?t=2913035 post #13614
Last resort was reflashing the firmware with an external flasher.
Ventricle said:
If you can't access bios nor boot menu, than you probably won't access anything.
@no_body one more question - is the screen lighting up at all when you try to power the device up?
Sent from [email protected] 4
Click to expand...
Click to collapse
Nothing, not even flickering. During the POST the camera led should flash. Not happening.
Sent from my ONE A2001 using XDA-Developers mobile app
mklmkl said:
Check e.g. this forum http://forum.xda-developers.com/showthread.php?t=2913035 post #13614
Last resort was reflashing the firmware with an external flasher.
Click to expand...
Click to collapse
Intel manufacturing tool sounds like a god start. Now I need the firmware to flash with. One step closer. Thanks!
Sent from my ONE A2001 using XDA-Developers mobile app
@no_body if so, then I'd recommend service repair, because you probably won't be able to fix it yourself. I've had the same issue with mu Asus T100 and they replaced the whole power IC and battery.
Anyway, it's better to look for help on Transformerforums then here. They have much more users of your laptop.
Hi Guys!
The last day I wiped my ADB sideload cache and factory reset my device.
After that, my OPX keeps rebooting and I was only able to enter fastboot mode (but the device isn't listed when i type: fastboot devices).
I've tried following the guide for hard bricked OPX but couldn't do it because i'm running linux, so i installed W7 into a virtual box.
The tool didn't work becouse i cant seem to allow installation of unsigned drivers in a virtualbox and i am running out of ideas.
On top of all that, the battery is drained and now i can't even enter fastboot. It just says "the battery is too low, charge for a while before power on!" and I can't charge it because it keeps rebooting in an interval of 3-4 seconds.
I have CyanogenMod 13 installed and since i factory reset it, i assume that debugging is not enabled.
Up until now, i was always able to figure something out when i scerwed my device up, but this time i have no clue what to do.
Could anyone here help me?
All help appreciated!.
Will it charge if you leave it in fastboot mode? I'm not sure how virtual windows works but normally you can press F8 on startup and select allow unsigned drivers.
First of all, you should charge the device, otherwise worse things could happen.. Can't you just keep it in charge when switched off?
After you reach a reasonable level of battery, you should be able to fix it: if properly set up, fastboot works very well on Linux and Mac also, so you don't need VirtualBox etc.
Maybe check your installation with other phones.
If everything ok, you should then flash both bootloader and sys using fastboot: be sure to download proper images (this especially goes for OS), ie recovery ones.
dr.prodigy said:
First of all, you should charge the device, otherwise worse things could happen.. Can't you just keep it in charge when switched off?
After you reach a reasonable level of battery, you should be able to fix it: if properly set up, fastboot works very well on Linux and Mac also, so you don't need VirtualBox etc.
Maybe check your installation with other phones.
If everything ok, you should then flash both bootloader and sys using fastboot: be sure to download proper images (this especially goes for OS), ie recovery ones.
Click to expand...
Click to collapse
The main problem right now it that i can't charge it. It turns on automatically when i so plug it in and then starts rebooting, so i can't even charge it to the point when i cant enter fastboot.
I'm still not sure about the state that is mentioned in the hard-brick guide, when i need to hold the volume up button for 10 seconds and then plug it in without letting go of the button. When i do that, it doesn't turn on, but also doesn't charge.
Whew.. Bad thing :-S
Honestly, this goes out of my knowledge: looks something related more to onyx itself than android internals..
If you can't find a special button procedure to stop the bootloader and start charge, I fear you'll need to have it serviced...
But before giving up I'd suggest you to wait for some more valuable opinions..
dr.prodigy said:
Whew.. Bad thing :-S
Honestly, this goes out of my knowledge: looks something related more to onyx itself than android internals..
If you can't find a special button procedure to stop the bootloader and start charge, I fear you'll need to have it serviced...
But before giving up I'd suggest you to wait for some more valuable opinions..
Click to expand...
Click to collapse
Thank you nonetheless!
I've managed to succesefully run through the unbrick guide and managed to repair it.
Okay I read sth on unbricking.
I found that win xp is the best option for driver compatibility (no surprises here, Win7+ are far more restrictive on unsigned ones: Ms politics) ..
So find an original Ms xp setup iso (a home would suffice, pro is better.. Still an optimal OS IMHO.. So sad it's been abandoned) and install it on VirtualBox.. It should be able to bind to your onyx via USB (warn: this is not automatic: you have to enable usb bind from VM lower icons - warn2: you can do it only with the device attached).
VirtualBox virtual HW is very well supported in xp with its guest additions (even direct3d works fine, for instance), so you shouldn't have problems with onyx drivers.
If you can start the phone in "unbrick mode" and link it to Xp, it should work I think ..
Otherwise prepare yourself to format your beloved Pc