Hi all,
I've installed Bliss OS on my machine and everything works all good. Then I restarted my machine and it fails to find the BlissOS partition. Any ideas why? I'm using the latest UEFI build.
Some machines automatically reset the UEFI boot order back to Windows. My Acer Switch 12 is one of these. So you might have to access the UEFI boot selector on power up (Mine is the F12 key) in order to select Bliss OS again.
Related
I found a trick to enter hardware recovery mode without connecting SATV to PC.
In the past, I had to connect SATV to a PC using microUSB to USB cable to enter recovery mode by hold power button for ~3 seconds.
After flashed rooted ROM 3.0 I found behavior of HW recovery mode changed, i.e., I need to hold power button much longer than 3 seconds after power light turns green until entering recovery mode.
Then I found by accident, if I left a micro USB OTG cable like this connected to the SATV:
http://www.walmart.com/ip/27420736?wmlspartner=wmtlabs&adid=22222222222018938306&veh=sem
I can enter recovery mode without connecting to a PC.
Regular Micro USB Cable - A to Micro B cable like this needs to be connected to a PC to enter recovery mode:
http://www.amazon.com/StarTech-com-Micro-USB-Cable-UUSBHAUB6/dp/B0017K4CJC
I have Android in recovery partition and ubuntu in boot partition, I can boot to ubuntu after power up by default, or hold power button to enter recovery mode to boot to Android from recovery mode menu without connecting SATV to a PC.
It can also be done by leaving Android in boot partition and other OS in recovery partition to boot to Android by default.
yahoo2016 said:
I found a trick to enter hardware recovery mode without connecting SATV to PC.
In the past, I had to connect SATV to a PC using microUSB to USB cable to enter recovery mode by hold power button for ~3 seconds.
After flashed rooted ROM 3.0 I found behavior of HW recovery mode changed, i.e., I need to hold power button much longer than 3 seconds after power light turns green until entering recovery mode.
Then I found by accident, if I left a micro USB OTG cable like this connected to the SATV:
http://www.walmart.com/ip/27420736?wmlspartner=wmtlabs&adid=22222222222018938306&veh=sem
I can enter recovery mode without connecting to a PC.
Regular Micro USB Cable - A to Micro B cable like this needs to be connected to a PC to enter recovery mode:
http://www.amazon.com/StarTech-com-Micro-USB-Cable-UUSBHAUB6/dp/B0017K4CJC
I have Android in recovery partition and ubuntu in boot partition, I can boot to ubuntu after power up by default, or hold power button to enter recovery mode to boot to Android from recovery mode menu without connecting SATV to a PC.
It can also be done by leaving Android in boot partition and other OS in recovery partition to boot to Android by default.
Click to expand...
Click to collapse
Hi, nice finding!
May I ask for some assistance? I'd like to dual boot the stock rom (for video watching) and a full android rom (for unsupported games and apps). Do you think it's possible using your trick? I don't mind having to enter recovery to boot my second rom.
Thank you!
grievous2004 said:
Hi, nice finding!
May I ask for some assistance? I'd like to dual boot the stock rom (for video watching) and a full android rom (for unsupported games and apps). Do you think it's possible using your trick? I don't mind having to enter recovery to boot my second rom.
Thank you!
Click to expand...
Click to collapse
I have ubuntu kernel in boot partition and stock SATV ROM 3.0 in recovery because I mainly use ubuntu, I occasionally try stock SATV.
I believe you can leave kernel of stock ROM in boot partition and put kernel of alternative OS in recovery partition. Some versions of ROM had a bug that any alternative OS in recovery partition gets replaced after power cycle. I have not tried to put alternative OS in recovery partition.
This is fantantasic, I've been following your prior posts and links for booting Ubuntu, is this image stable enough to use as a daily PC, and I take it the GPU does not work yet? Or do the aarch64 drivers enable it on the satv
Afeld88 said:
This is fantantasic, I've been following your prior posts and links for booting Ubuntu, is this image stable enough to use as a daily PC, and I take it the GPU does not work yet? Or do the aarch64 drivers enable it on the satv
Click to expand...
Click to collapse
As far as I know, SATV ROM 3.0 and ubuntu kernels base on CM13 or L4T23.1 are stable for dual boot. I have not updated to SATV ROM 3.1 and L4T kernel 23.2. I have run Nvidia Cuda samples without issues. Bluethooth is not working and remote controller is not usable under ubuntu.
so is there a way to dual boot stock android tv ROM & custom ROM with full android support??
Slayerkodi said:
so is there a way to dual boot stock android tv ROM & custom ROM with full android support??
Click to expand...
Click to collapse
You will need to put full android kernel + ram disk in RECOVERY partition and put full android file system in external SD card (or USB drive) and use the trick to switch between stock SATV and alternative OS at power up.
The ram disk should have init file to load file system from external SD or USB drive.
The kernel for alternative OS should be compatible with stock SATV boot loader and device tree.
im sorry is there a guide i can follow as i partially understand what you mean but i have no idea how to do it, but would love this as i have the same adapter so can do the trick hopefully
I can't make this properly work.
Any news about U-boot? Want to use L4T24 and stock Android together smoothly.
I'd like a solution to dual boot too...
Hi all,
I've had this setup on my device :
Code:
ROM info :
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Based On: AOSP-CAF
SlimROM 7
Last monday, my phone was frozen on blackscreen, it didn't want to be unlocked...I tried to hard reboot but it didn't work, so I decided to open its back to remove battery.
After that it bootloop many times on this message :
"Your device has failed verification and may not work properly. Visit this link on another device: g.co/ABH Your device will boot in 5 seconds. Pressany key to pause boot."
There was no ASUS logo. But I'm use to see this message because I've flashed my phone several month before.
After many loop, I've finally access to fastboot, so I've done a wipe data factory reset, after I could access to TWRP. I've flashed my slimrom, but it didn't work, at next reboot, it was the same scenario : bootloop and no asus logo.
To explain my situation now, when i plug my phone, it vibrate and bootloop on message, after 4 - 5 loop I can see Asus logo and after, the dead droid. But after few minutes it bootloop again.
I follow instructions in this tuto : [Guide] Un-brick both (Soft/Hard) bricked Zenfone 2 ze550ml/ze551ml. , but my phone bootloop so i can see Moorefied in IntelSOC Driver during few minutes :
So i can't use xfstk downloader.. (because bootloop). The beautifulest thing is the buttons Vol UP Vol Down and Power not work ...
Any ideas ?
RIP ZE551ML :crying:
(I'm French, tell me if you don't understand me)
You are supposed to off your phone, start xfstk process then attach your phone
https://forum.xda-developers.com/zenfone2/help/recovered-bricked-zenphone-2-z008-2-t3758111
yusoffb01 said:
You are supposed to off your phone, start xfstk process then attach your phone
https://forum.xda-developers.com/zenfone2/help/recovered-bricked-zenphone-2-z008-2-t3758111
Click to expand...
Click to collapse
Buttons doesn't work... To turn off my phone I must unplugged it. When I plug my phone, it boot automatically and loop on error message : "Your device has failed verification and may not work properly. Visit this link on another device: g.co/ABH Your device will boot in 5 seconds. Pressany key to pause boot."
access fastboot and flash raw
It's ok i've easily flashed phone with 6_stock_recovery script from XDA. So now my phone boot normaly, it's great but my POWER button doesn't work ... I'll try to change it maybe ..
***NVRAM backup solved with updated VCOM drivers, but Linux still won't boot***
I want to dual boot my Gemini with Android and Linux and I followed the instructions on the Planet Computer support webpage which recommends that you back up your NVRAM before trying to install the Linux partition.
I'm not happy to try to install another partition without backing up my NVRAM, so I spent most of Saturday and Sunday trying to get this to work without success. On every occasion, the Smart Phone Flash Tool stops responding, the Gemini will only boot if I disconnect the USB cable, and eventually I get this error message on my PC:
ERROR :
STATUS_READ_DATA_EXCEPTION
(0xC0050007)
[HINT]:
Has anyone succeeded in backing up the NVRAM on their Geminis, please???
TCMuffin said:
I want to dual boot my Gemini with Android and Linux and I followed the instructions on the Planet Computer support webpage which recommends that you back up your NVRAM before trying to install the Linux partition.
I'm not happy to try to install another partition without backing up my NVRAM, so I spent most of Saturday and Sunday trying to get this to work without success. On every occasion, the Smart Phone Flash Tool stops responding, the Gemini will only boot if I disconnect the USB cable, and eventually I get this error message on my PC:
ERROR :
STATUS_READ_DATA_EXCEPTION
(0xC0050007)
[HINT]:
Has anyone succeeded in backing up the NVRAM on their Geminis, please???
Click to expand...
Click to collapse
Yes I did succeeded but first I have had to load the scatter file (from Android firmware zip) a then I have to update VCOMM preloader drivers (using windows 10 device manager)
Sent from my Gemini 4G using Tapatalk
OP has had succes backing up his NVRAM partition after installing updated Windows 10 64-bit drivers, as supplied by Planet Computers.
I would therefore recommend anyone having issues backing up partitions to make sure they have installed the latest drivers.
Finally!!! The updated drivers have "allowed" me to backup the NVRAM successfully...and Android 1.1 is available to download.
The link says Android firmware v1.0, but the downloaded file is Gemini Android v1.1. However, looking at the screenshots, I can't see any difference, except in the Android boot sequence one is offered "Configure physical keyboard"?
I then followed the instructions to install Linux as a dual boot, but when I reboot (pressing Press Esc (On) and the side button at the same time until the screen turns ON to boot into Linux) displays a Linux splash screen but then the Gemini boots into Android
TCMuffin said:
Finally!!! The updated drivers have "allowed" me to backup the NVRAM successfully...and Android 1.1 is available to download.
The link says Android firmware v1.0, but the downloaded file is Gemini Android v1.1. However, looking at the screenshots, I can't see any difference, except in the Android boot sequence one is offered "Configure physical keyboard"?
I then followed the instructions to install Linux as a dual boot, but when I reboot (pressing Press Esc (On) and the side button at the same time until the screen turns ON to boot into Linux) displays a Linux splash screen but then the Gemini boots into Android
Click to expand...
Click to collapse
keep the side button held down until it boots to the screen that shows the planets keep it held down and the screen will go black then you can let go of the side button and it will boot up in Linux
I have an old Surface 2 RT from my parents here, which I wanted to rejuvenate for my kids. I had reset it to the factory settings, but that process failed and the device ended up not booting anymore. Using some command line wizardry with dism, booted from USB, I was able to get Windows 8.1 back on the device. Because I was already working on it, I wanted the put Windows 10 on it, using this guide.
Step 1 went fine - I downloaded the recovery image
Step 2 - installing patched Windows RT image went fine too
Step 3 is where issues began
I was able to execute the "disabling UAC" step
When installing the secure boot policy and rebooting, I got an error that the secure boot policy could not be installed.
Because of this, I executed this step - by changing some files on the EFI partition
Now the device does not boot anymore because of error 0xc0000225 by which it cannot find "winload.efi" or it contains errors. Pressing the "WINDOWS KEY=recovery" it says the same error code but with a different description "A required device isn't connected or cannot be accessed". Eventually it reboots on its own and shows the error again, after the Surface boot logo.
I'm trying to follow the troubleshooting steps but the tablet does not boot from USB (anymore)
I properly safely eject the FAT32 formatted GPT partitioned USB drive of 4GB. I also tried a different USB stick of 8GB.
I use the volume down method in an attempt to get it booting, however, it always ends up at the same message. It does read the USB drive, because the light flickers a bit, but it doesn't act on it.
I cannot boot to UEFI either: I press power and volume up - it does not turn on. I am able to turn it on without the volume up button pressed however - but it does not boot of course.
My feeling is that it has forgotten that it needs to boot from USB, but I can't access the UEFI settings either. Besides, it often needs the "10 seconds power button" trick to even turn on.
What steps can I follow to at least get some more life out of it - or is it completely crapped out?
That EFI modification is for booting Windows 10 only, won't work if you have 8.1 installed instead of 10, to do the unlock you must not enter a Microsoft account or do any upgrade.
The Surface RT and 2 are very finicky about what USB they want to boot from power off, basically I have over 10 USB sticks, among which 4 are 4GB or smaller, the Surface RT and 2 only boot from one of them, which is a no brand Chinese one as well.
So basically just get the recovery image from Microsoft then try a lot of sticks till one boots.
Okay, I guess I need to scavenge some USB sticks
Use a SanDisk Ultra 3.0 drive. Worked best for me on my 1st and 2nd gen Surface RTs. Regular cruise gilded work fine, but the ultra 3.0 is better since it has better transfer rates and whatnot.
I only have three: a cheap marketing one of 4GB, a USB stick with SD card slot, and a 2GB one
But the weird thing is that I also had some connection issues in Windows itself, when it still was working. The USB sticks rapidly connected/disconnected sometimes - but I did not have this issue with the USB keyboard I plugged in. Still, perhaps the USB port is busted.
Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
RecoveryYour PC needs to be repaired.A required device isn't connected or can't be accessed.Error code: 0xc000000fYou'll need to use the recovery tools on your installation media. If you don't have anyinstallation media (like a disc or USB device), contact your system administrator or PC manufacturer.
If I try to press the Windows key to "try again", I get:
BSOD
RecoveryYour PC needs to be repaired.Windows cannot verify the digital signature for this file.File: \WINDOWS\System32\winload.efiError code: 0xc0000428
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem
silkway said:
Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
RecoveryYour PC needs to be repaired.A required device isn't connected or can't be accessed.Error code: 0xc000000fYou'll need to use the recovery tools on your installation media. If you don't have anyinstallation media (like a disc or USB device), contact your system administrator or PC manufacturer.
If I try to press the Windows key to "try again", I get:
BSOD
RecoveryYour PC needs to be repaired.Windows cannot verify the digital signature for this file.File: \WINDOWS\System32\winload.efiError code: 0xc0000428
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem
Click to expand...
Click to collapse
Hi I have same problem and have tried everything you have did you fix it
There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.
jwa4 said:
There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.
Click to expand...
Click to collapse
Thanks buddy I will give it a go