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 ?
Related
Hello,
Edit: First off sorry about the title it Pic Untu without the space I didn't realize it until I posted the question.
I have an android tv box. Model name is cs968 and it has RockChip rk3188, its rooted and i had cwm as recovery.
The device is also mentioned in this thread : http://forum.xda-developers.com/showthread.php?t=2457778
I wanted to use a linux distro on it and came across a distro named Pic Untu ; (its not written separately but its getting censored otherwise same with the link below you have to delete the space between 'pic' and 'untu' sorry about that )
http://ubuntu.g8.net/index.php/14-sample-data-articles/86-pic untu-4-5-nand-released
Now I have successfully flashed it without having any problems. But it had no support for built-in wifi or bluetooth so i turned it off as you would a desktop computer ("shut down" from the start menu) and moved it close to a place where i can connect it to ethernet to see if ethernet works. But when I started the device again it stuck in boot loop.
The device is not recognized from windows or linux from adb (but it used to, I've flashed a custom ROM with rkbatchtool from windows, and could connect the device from ubuntu with adb). Also i cant flash it again from a flash drive or sdcard ( although it says it recognizes a usb device or an sd card when booting up).
The only other response i get from the device is that when i press and hold the reset button, it resets and stops booting with an empty screen( this would go to CWM when android was installed)
Last thing is, I have 2 of these devices one of them is untouched so if that helps i can maybe do a nandroid backup and flash it once the adb is working or something similar maybe.
I'm not sure what I can do at this point so any help/pointers is appreciated.
Thank You.
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...
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.
i have a ZTE Max Duo Tracfone which is stuck in a boot loop. What is different about my phone caught in a boot loop, from (other phones caught in a boot loop mentioned on this website is that other people have flashed ROMs which caused the loop, but I have not done that. My device is not rooted. I don't know how it happened but I rebooted because UNDER PHONE SETTINGS/APP I could not clear the cache from google play or anything. Under the reboot menu, I have since wiped the cache and know that the inevitable end is to re-set the phone which will wipe out my calendar, my data, etc.
My question is this, is there anyway I can transfer my data or files on my internal hard drive while it is stuck in the boot loop? I have installed Wondershare android and Mobiledit, but neither have been able to find my phone to transfer the files. Could it be that when a phone is stuck in a boot loop, windows 10 cannot read the phones internal hard drive until the booting is finished? Therefore, since the OS cannot advance past the loop, I can't open the phone to copy it?
I have installed the ZTE universal driver, but Windows (pc) doesn't recognize my phone when I plug it to the PC via cable. Under WINDOWS 10 DEVICES, it says nothing, but once I plug in my phone, Windows 10 device Manager does say Universal Serial Bus Devices/ADB interface, and under (OTHER DEVICES), a device called MTP appears with a yellow asterisk, but i see nothing about zte driver. I tried to update MTP with the ZTE Driver, but it said incorrect driver. Maybe I need the ZTE DUO driver which I haven't been able to find on google. I only have used the universal zte driver.
Not a noob, but not an expert either. Recently installed Android studio, but I don't see anything on the menu which allows me to run commands for the phone. am willing to try anything to save my data.
thanks you, james
So The thing starts from a windows update, After the clicking restart from the power option the windows update starts. The screen says "Configuring windows update 30%" then the PC restarts Then the Blue Screen of death appears It says Unmount able Boot Volume and doesn't boot into the Windows. I tried fixing the error by Reinstalling windows from a flash drive and after a period of time the Blue Screen of death is back. Is there a permanent solution to this problem? Because each time I Reinstall windows all my files are getting deleted, which is really frustrating. I haven't even installed any unofficial software that can corrupt the boot files. I am facing this issue in both windows 10 and 11 on one single computer (2021 ASUS A17 TUF gaming laptop). I even got a exchange done for the laptop. But the new laptop also has the same unmountable boot volume error. Please can anybody help me on this problem.
thanks in advance.
Hi!
2 different laptops with same issue????
Can you explain step by step what are you doing?
Is windows stock windows image or any other else?
Pendrive was creates with windows Media creation tool?
Give us all details so we can help you!
@DJEinsteinBS
look inside here:
How to Fix UNMOUNTABLE_BOOT_VOLUME BSOD in Windows?
The Unmountable Boot Volume is a BSOD error that occurs when the boot volume is not accessible for the system. One of the main reasons that bring this
appuals.com