I just download Remix OS from the official site, but when I tried to install it, I just stuck this screen
Below the image, it says "ANDROID root @ remix_x86_64: / #"
I press the enter key, no change whatsoever
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My laptop specification: Intel Core i5, 8GB RAM, Intel + Nvidia VGA (but I have changed to Intel), and using UEFI (Security Boot has been disabled)
Please, give me a solution, thanks..
"... but I've changed to Intel"
By that do you mean you've disabled the NVIDIA GPU via the BIOS? If that's true then it shouldn't have any problem booting. Anyway, try adding "nouveau.modeset=0" (without quotes) onto the end of the menu.lst file in the RemixOS folder via Windows.
Sent from my iPhone using Tapatalk
Related
Has anyone tried to use QEMU or BOCHS with GP5? I haven't seen anything saying it will specifically work with Galaxy devices but I just wondered if maybe someone has gotten it working. I don't fully understand the Android OS yet so I wasn't sure about trying it myself.
Yeah, I got Boochs working!
And I have got it to work with Redhat, and windows 95.
however both are a bit hard to control, and have no internet support:
Boochs:
http://forum.xda-developers.com/showthread.php?p=21293078
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
redhat image:
http://superb-sea2.dl.sourceforge.net/project/bochs/Disk Images/RedHat Linux/redhat_6-512mb.zip
If you want to use the redhat image rename it to c.img and put it in the sdl folder
username:root Password: redhat
Boochs install instructions on the download page.
Sorry to bother you further but after it boots and I put in the username and password, it just starts as a command line tool or something and anything I try it just says isn't a proper command. Is a ui supposed to boot?
Hello folks:
I just bought a AML8726-MX Android TV stick from China and took some pictures of the board/chips. I have a few questions...
(1) Is it possible to discern the type of wifi chip used? The xda-dev Linux build doesn't support broadcom yet.
(2) Is there an XBMC .apk that supports this AML processor? The stick doesn't come preloaded with XBMC, so I need to find an .apk that has Amlogic support. Recent XBMC nighties support Amlogic, but I'm also having issues with "dependencies" that I think are related to nightly builds.
(3) If there is no reset button, then does that mean I can only use bootcard or adb to flash?
(4) Is there a ROM out there that can be flashed?
(5) How do I backup the firmware before I start to play with new ROMs?
Thanks.
Hopefully these images aren't too big
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello together,
as you can see on my screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb driver should be installed properly but my ARC 7 HD doesnt get recognized. When I try to do a manual driver installation (with boot options) my google driver still gets rejected because of it incompatiblity to x64 systems.
Can you recommend me another driver or installation routine?! My Kobo is rooted and in debug mode.
edit: my asus tf101 gets recognized
edit edit: when the kobo pad is in recovery mode it gets regognized, but not booted
Thanks and regards
solved: Installed the recovery with Rashr, also got adb over wifi running. Sadly there is no Kitkat or cyanogen mod available for this pad. I would like to get rid of these reader tools....
hope this helps!
http://forum.xda-developers.com/showthread.php?p=65499511
Sent from my MI 2SC using Tapatalk
Hello, yes like the Titel says.
I was playing around with the MTK Tool on the PC and did Manage to Format my whole Partition there. on a Olefone Armor 7.
So de Charge LED is working but i got no reaction on the adb devices commands and also no reaction on the Power UP Button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my question now. …is there any solution around to fix this?
Lovely greats
Richard
ADB is integral part of Android OS, hence it can't work if Android device's OS got erased.
Try to re-flash device's Stock ROM by means of ODIN.
thank you very much, so I have start W10 in a Virtualbox an use the MTK Tool that's recognize my Phone again,
I was use the MT6779 Scatter-file what I was found to reflash on the Armor 7. But the Pulgin show's me that it is a MT6227.
So I guess i have to find a MT6337 Scatter-file first.
I``ve bought dirty cheap box IK316 Q44 v.1.0.It has 4 chips with 2Gb(1Gb total)
ddr3 samsung 8GB eMMC and some freaky cpu IK316.I cannot find anything about this cpu.Wanna try armbian or some other ROM on it,coz the original one is so buggy and complete waste of hardware power
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello All Winner. Strange chinese factory... they spend more time and money to fake the cpu/ram/OS than optimising it.Sorry for the images, but I prefer to work under the last(may be) good sunlight for this year.
DO NOT CONNECT IT TO YOUR PC/LAPTOP VIA USB!!! It will blow your usb fuse!
hi i have a box like yours , it's stupid to run the command adb reboot bootloader and then get stuck at bootloarder i realized windows has no driver for this chip can you help me save the box, thank you very much