I Installed Ubuntu on ASUS TF101 but when it starts to boot I get the black screen that windows users would call DOS, and I see the Linux two penguin at the top and it loads a source of Linux command takes about 60 seconds, and then reboots and starts the whole thing over again. I let it go and it did it for over two hours. What should I do?
Related
When we will have support of the Remix for those tablets in the title, for most of us there is only black screen after installation !?
On my Encore wt8-32 ive managed to boot it. Problem is it will only consistently book in nomodeset mode which makes gpu slow and a contant blinking cursor on the screen. I have been playing around with grub.cfg trying "xforcevesa" "vga=988" "vga=971" etc... strangely on the odd occassion it booted in properly and was working fine apart from stuck in portrait mode. Frustratingly I would try and reboot with the same settings that worked and other times just get the black screen again, it's like it would just randomly work now and again, anyone know what's going on ?
bigr1979 said:
On my Encore wt8-32 ive managed to boot it. Problem is it will only consistently book in nomodeset mode which makes gpu slow and a contant blinking cursor on the screen. I have been playing around with grub.cfg trying "xforcevesa" "vga=988" "vga=971" etc... strangely on the odd occassion it booted in properly and was working fine apart from stuck in portrait mode. Frustratingly I would try and reboot with the same settings that worked and other times just get the black screen again, it's like it would just randomly work now and again, anyone know what's going on ?
Click to expand...
Click to collapse
That's exactly what I mean, only the first time it booted on my encore, after that only black screens. The messing with the grub and partly working means it can be set up correctly, my/our request is JIDE TEAM to make it stable for constant normal booting if it's possible. Or someone with the same hardware that has the knowledge ti give us some help
It runs good on my MicroCenter TW-801 - but I have not been able to get it to work on the internal drive yet only on a external usb sd card.
guys use rmx installer and use the 64bit remix os beta uefi and u will be able to get it working, but no sound, no Bluetooth, no rotation ( in my case with a m80ta I'm locked in portrait mode), no sensors basically, everything else seems to be working fine,sd reader, buttons, gpu seems to be recognized well but with no rotation most apps wont work at all
by the way the led next to my front camera is always turned on while the os is running
Apparently there is a bug in recent kernels that affects Bay Trail devices.
Try to set kernel parameters intel_idle.max_cstate=1 and tsc=reliable at the end of kernel line in grub.cfg.
That did the trick on my Asus Transformer Book T200TA.
I hope that will work for you too!
I got it working when I change resolution in grub file. I made it 800x600 and it starts then and when it starts the with native resolution.
How to get screen rotation ? It's very important for some apps !
I get hard locks at various times. Using a HP Stream 7, it has a 32 bit UEFI with a 64 bit processor. Dumbest thing I've heard of.
favorite
I have a kindle fire hdx that I had fixed two weeks ago for a broken screen and broken charging port, (why you ask and why I didn't bother to get a new one is because this kindle has important files that I didn't put on my computer or printed out which was a mistake) anyway, it is finally fixed and it looks like it is working, except when I charged it, it was rebooting when all of a sudden it gave me a complete blue screen when it tried to go to the page where you put your password in. I tried restarting it for 30 seconds and now when it reboots, the opening before you enter the password where it has the words kindle fire twice font is blurry and scratchy looking. I really need those files as they are personally important to me. Is there anyone that can help?
After I charged it, the blue screen went away and it is stuck on booting up where the kindle fire logo appears and doesn't go past the screen where I can put in my password. I got close to where the screen changes from the logo to the screen where I can put my password but it freezes and reboots again.
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk
I installed this great OS in my old core 2 duo x64 laptop (dell m4400, 4gb ram). I am dual booting it with windows 10. I have installed Remix OS in second hard drive (which is connected using Harddisk caddy). Every thing works fine but when the OS boots it hangs for a short period of time. And once running it keeps hanging on regular interval like 30 sec for 1 to 5 second. Sometimes I get Android has stopped working error. Is there any fix for this? Thanks
I am trying to revive an ancient Asus Nexus 7 for a local charity for use as an Ebook reader. I am not certain of the model, but the previous owner called it "first generation". It is WiFi only and the Asus and Nexus logo/script is horizontal on a dot mapped, leatherette feeling background.
The device is stuck on the Google logo and will not progress past it. I can get into the bootloader and have tried factory reset, cache wipe, etc. and the device stays stuck on the Google logo. I tried attaching to a PC to see what I could do in adb, but the device isn't detected by Windows when plugged in.
Is there anything I can do to revive this device?