I have my Lenovo thinkpad tablet 2 SSD partition erased but I realized latter that UEFI bios prevents me from installing OS e.g. win 8.1 pro coz it contains different certification key, and any other OS simply cant boot.
Any one can help me
Related
I know there is good software out there to clone/image my hard drive and restore it to a new SSD drive.
I'm just wondering though, since my laptop is brand new, I made a full recovery to a USB drive and included the OEM recovery partition.
Couldn't I just swap out the old HDD with the new SSD and boot with the recovery stick and do a full recovery back to the new SSD?
Also, however I do this, recover or image backup/restore, do I need to do some type of SSD alignment? I can't find a clear answer on that.
You can directly image the HDD partitions onto the SSD using a tool such as "dd" on Linux (if you can book off of a bootable Linux image/liveCD, that's probably easiest; just be sure to set a large-ish block size that is a multiple of the SSD block size or the copy will take forever). However, I would tend to recommend doing a clean install of the OS and then restoring your files into it. Using the recovery image would probably work fine, although I prefer clean install media where possible.
Alright...I have a bit of a project going on here. I have a Lenovo S10-3t convertible touch tablet/netbook that I am creating a multiboot scenario for.
To help cover all the details, here are my disks and my partition setup.
640GB HDD as the primary drive
32GB SDCard as the secondary drive.
Primary HDD has these partitions:
MBR PARTITION SCHEME
Partition 1: Windows 8 Pro 64-bit (492.33GB) NTFS, with Win 8 bootloader
Partition 2: Mac OS X Snow Leopard (79.28GB) HFS+ Journaled, with standalone mini-chameleon bootloader
Partition 3: Linux Mint 15 64-bit (23.28GB) EXT4 Journaled, with GRUB2 on this same partition
Partition 4 (in extended partition): Linux Swap (1.27GB) ...swap space
The SDCard has these partitions:
MBR PARTITION SCHEME
Partition 1: Dedicated to ReadyBoost (5GB) FAT32
Partition 2: Android x86 4.2.2 (24.84GB) EXT3, legacy GRUB SHOULD be in the MBR of this disk
I am using the Windows 8 graphical bootloader to manage everything, as it is a touch-screen tablet, and I like having the touch support for the bootloader. So I would PREFER to use it if possible.
I have currently added entries for OSX Snow Leopard and Linux Mint Olivia to the Windows 8 boot manager, and all three OSes chainload properly to their respective bootloaders and are happy with each other.
So...my question is this...is it possible to chainload the Legacy GRUB bootloader in the EXT3 partition on the SD Card that has Android on it with the Windows 8 Bootloader? And, if so, will you walk me through this process?
WHY am I doing this? There's a couple of reasons...as this is a touch screen tablet I would prefer the convenience of having an option to boot Android from the touch-enabled Windows 8 Boot Manager instead of having to fold the screen away from the keyboard, press FN+F11 and selecting the SD Card as the primary boot device every time I want to go into Android. I could have android on a fifth partition on my HDD, but one of the reasons for having Android on flash memory is BECAUSE I have a mechanical HDD, and I use Android if I'm actively moving the laptop around in a rough environment (say, walking or in a moving vehicle for example, and the HDD would be off since it isn't needed). I know I could use an SSD, but I prefer having a mechanical HDD in my laptop for my own reasons.
I am using a combination of VisualBCDEditor and EasyBCD, and I cannot get either to see or acknowledge the existence of the EXT3 partition on the SDCard (though they all see the EXT4 and HFS+ volumes on the primary HDD, and the FAT32 partition on the SDCard...)
feherneoh said:
I'm almost sure that you are using EasyBCD, so just add NeoGRUB to Win8 Bootmenu, and configure it to set root to sdcard's proper partition and do a chainboot.
Click to expand...
Click to collapse
EDIT: Nevermind, I screwed up on the boot arguments and figured out what the problem was (I used windows' notepad to copy the arguments as opposed to Notepad++, which actually respects linux's formatting). I'm able to successfully boot Android chainloading from the Windows 8 graphical bootloader, to NeoGrub, and allowing NeoGrub to boot directly into the kernel. I appreciate the help. I will leave my previous post for future searchers that need help in doing this as well.
-----
Yeah, I mention at the bottom of my post that I'm using a combination of EasyBCD and Visual BCD Editor. I followed your suggestion and added NeoGrub to the list, and opened the menu.lst config file for it.
I copied the majority of the contents of the menu.lst from the "grub" folder in Android x86's partition and pasted it into NeoGrub's menu.lst (editing the harddrive and partition to reflect what it should be, of course).
It sees the kernel and ramdisk images, begins to load them, and then goes into an infinite loop of spawning dots across my screen (I can tell from experience that this means it isn't loading properly and the kernel halted). It seems NeoGrub doesn't support the "special" arguments that need to be passed to the kernel (that passes properly with the legacy GRUB loader), so I guess I need to figure out how to chainload GRUB from NeoGrub now. Back to square one, essentially.
Here is the menu.lst for the existing legacy GRUB on Android's partition:
Code:
default=0
timeout=6
splashimage=/grub/android-x86.xpm.gz
root (hd0,1)
title Android-x86 4.2-test
kernel /android-4.2-test/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 video=-16 SRC=/android-4.2-test
initrd /android-4.2-test/initrd.img
title Android-x86 4.2-test (Debug mode)
kernel /android-4.2-test/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=-16 DEBUG=1 SRC=/android-4.2-test
initrd /android-4.2-test/initrd.img
I notice in the JellyBean entry you have
Code:
acpi_sleep=s3_bios,s3_mode
I'm curious on what this and the "VGA=778" does. My "VGA" is set to -16 for whatever purpose it fulfills.
I'm assuming the acpi_sleep option allows the kernel to use the S3 sleep state for the hardware, like the same state other OSes use when you shut the lid? Currently all my Android install does is shut the screen off if I close the lid...and I'm fairly certain that's hardware-based anyway.
Is it possible to just delete all the partitions on a dual boot android/windows mini pc including recovery and system partitions to maximize space and install windows as I please? Or is there a partition I have to keep on to avoid bricking it?
In other words can I treat it like a normal pc, boot with a windows installation usb, erase all partitions on the hard drive, and install windows?
Also what are the chances of a successful windows 7 install on one of these windows 8.1/10 mini pcs? Willl it error out because win7 is generally just not compatible with for instance a z3735f chipset or its just a matter of drivers and I would be fine with the driverpacks iso?
Thanks.
No need to format all.Just keep the windows parition and the efi boot parition,after formating the android,edit the bcd file in efi parition by easybcd to change the boot order,then it s ok.
As for win7,I have never tried before,but it should be no problem.
Sent from my TCL Y910 using XDA Free mobile app
Hey xda,
I'm trying to install phoenix OS as a standalone OS on my 64bit pc.
I followed every step from this thread, no exception: https://forum.xda-developers.com/ph...opment/problems-installing-phonix-os-t3681518
I'm 100% sure I did not miss any step, I tried it at least 5 times.
After installing phoenix I can chose "Run Phoenix OS" OR "Reboot".
When I chose to run phoenix after installing, it boots straight up, runs extremely well, quite impressive actually!
It boots without the bootable usb, and when going into settings --> storage , I can clearly see it's installed on my HDD (5xx GB free).
BUT, when I restart phoenix, it will just say "Missing OS". And there is no way to boot phoenix, the only way to boot it again is to reinstall phoenix using the bootable usb.
Thanks a lot in advance!
PS: before you ask: yep I created 2 partitions, one fat32, 350mb, flagged as boot and installed GRUB2 on it. The other one ext4 and installed phoenix to that.
And yes, my HDD is set as the first boot device in the bios.
I'm lost
EDIT: 32bit has the exact same issue
I think the problem is related to a limitation of your system, like the partition size or partition format (MBR, GPT, etc). Do you have EFI or BIOS? If you have EFI, I'd suggest that you try to use EFI GRUB2, no need for creating a partition for it, if the disk is partitioned correctly, you should have a hidden EFI partition... If it's not the case, please give more details about your system, it may help...
Has anyone installed Phoenix OS v3.0.2.451 on an ext4 partition?
I installed it on a dual boot laptop yesterday, on a ext4 partition. I hadn't had time to check it out yet, only know that the default file manager don't see Linux partitions, but see only NTFS partitions. That's not a problem, as I keep most of my data on NTFS partitions, for both Linux and Windows to see (read/write) them.
This is an UEFI system.
It seems pretty snappy.
(I had both Remix OS and Phoenix OS quite sometime ago, but had removed them .)
Now on a MBR laptop, also on a ext4 partition...
Installed same version of POS on an ext4 partition of a MBR laptop. It has Debian Sid, few other Linuxes and older Windows 7 Home Basic in it. Works alright atm. Can't uninstall some Chinese only apps from Phoenix from both laptops. Its Stardust browser didn't want to work well in this, so installed Chrome from Play Store. But in the UEFI laptop, the Stardust browser worked quite well.
Installation was done manually in both laptops, the way it was done in the early days.
I find Phoenix OS 3.0.2...works better on a UEFI laptop. No idea why. In an MBR laptop, I can't highlight text in the web browser and copy, the mouse right click doesn't work. The right click doesn't work in the UEFI too, but text can be highlighted, especially in Opera, not in Stardust, nor in Chrome. Btw, Play Store is available.
Maybe I should write how I installed it in another thread?