Related
Hi,
Because of the need of a bootmanager and the lack of patience to type a hack a lot at the console, I created a ubuntu maverick based build system for arm crosscompiling with a script helps by building kernel, ramdisk, recovery archive, debugging via fastboot and so on. As chroot env it is very flexible, needs not to install something and runs inside all linux distris.
just extract it somewhere onto an ext partition goto the directory and type ./start
in the root of the chroot env is a README file which contains infos where is what. read it before.
it contains three tools
build (a script supports different actions, "build help" shows them)
unpack-boot (extracts a boot image into the actual directory)
unpack-ramdisk (extracts a ramdisk into the actual directory)
Download:
http://www.bisme.net/files/xda/bootbs.tar.bz2
TODO:
the chroot env is still based on a desktop version of maverick and bigger than needed, this will change soon.
PS: Bootmanager is still in work, should finish(as a trivial but working version) in the next days and is the first step to support multiboot different linux installations(also different android versions) on android tablets. But this is another story will get an own Thread here. In the meantime I hope all romcookers out there will have fun with this build system.
So following a couple of tuts that I've found on the forums I've been able to install debian linux wheezy armhf build on my tablet in a dual boot configuration with it booting off of a second ext4 partition on the microsd card along with getting the drivers/codecs from Linux4Tegra to be installed and somewhat used on debian linux.
What works:
-Wifi
-USB
-Display (doesnt use tegra drivers)
-Buttons (power, vol, rot switch [acts as wifi switch])
-Touchscreen
What doesnt work:
-Bluetooth (Untested but apparently it finds it and sets it up.)
-Audio (Detects it in the kde info center. System Settings program only says that there's a dummy output. Playing any form of audio crashes the program.)
-HDMI (with the Tegra gfx drivers it finds it but says it's disconnected even when connected.)
-Cameras
-GPS
-Motion Sensing
-Light Sensor
With the display, whenever the tegra drivers are used, it finds HDMI (as HDMI-1) and the LCD screen (as LVDS-1) but says that there is no device on the lcd screen. With that being said, it is using the fbdev driver instead which shows pink and/or inverted colors in some instances but at least it shows a gui.
Guides used:
{HOW TO} Native Debian on A500 and building your own rootfs
[BOOTLOADER][DUALBOOT + RECOVERY][BOOTMENU] Patched ICS bootloader V8 (07/06/2012)
[Dev] Native linux on Iconia
Requirements:
-an A500.
-a 16+GB microsd.
-Linux OS (Debian, Ubuntu, etc.)
-Linux 4 Tegra: Download the Ventana files under "Additional Information" and "Driver Packages"/"Codec Packages".
Ok, so here's how I've done it.
1) Make sure you have a multiboot loader and have flashed the appropriate bootloader image to the second boot partition. get the boot image from the 3rd guide under "precompiled kernel image" and flash that to the second boot partition. (be sure to check the dualboot guide above on flashing the image if you are using the bootloader that is in the guide.)
2) Have a microsd card partitioned with two partitions, one for normal data (can be any format) and a second one that is in ext4. you can do 3 partitions by adding a swap partition but the ext4 partition must be the second partition.
3) Install qemu on the host system.
Code:
For Ubuntu - sudo apt-get install qemu-user-static
4) Mount the microsd's ext4 partition.
Code:
sudo mount -t ext4 /dev/<microsd 2nd partition> /mnt/Linux
5) Run:
Code:
sudo qemu-debootstrap --arch armhf wheezy /mnt/Linux
6) Chroot into the installed environment.
Code:
chroot /mnt/Linux /bin/bash
7) Add sources to /mnt/Linux/etc/apt/sources.list. you can get debian sources from http://debgen.simplylinux.ch/. Be sure to choose "Testing (wheezy)" and all the sources check boxes along with where you live to find the nearest repository.
8) Install the wifi drivers pt1.
Code:
apt-get update ; apt-get install broadcom-sta-common broadcom-sta-source firmware-b43-installer firmware-b43legacy-installer b43-fwcutter
9) Install the wifi drivers p2. In the "{HOW TO} Native Debian on A500 and building your own rootfs" guide, there is a download from mediafire for the firmware files for the drivers. Extract that and put it into /lib/firmware. I dont know if the individual files in the brcm should be in the /lib/firmware or not so i just copied the folder into it and the files within it into /lib/firmware.
10) Install the GUI:
Code:
apt-get install <gui>
List of GUI's (that i know of):
Code:
KDE (takes a long time to install): kde-full
XFCE: xfce4
11) extract the ventana_Tegra-Linux-R16.1.0_armhf.tbz2 file and the ventana_Tegra-Linux-codecs-R16.1.0_armhf.tbz2. you should get a folder called "Linux_For_Tegra" and a file called "restricted_codecs.tbz2". go into the "Linux_For_Tegra/nv_tegra" folders and extract the nvidia_drivers.tbz2 file. from there you should get 3 folders: etc, lib, usr. copy those to "/mnt/Linux" (you are going to have to do this as root). back out of those folders and extract the restricted_codecs.tbz2. you should get a folder called "lib" copy that to "/mnt/Linux". after that, it's time to make a hard link so that the X11 can find the tegra driver:
Code:
ln /usr/lib/xorg/modules/drivers/tegra_drv.abi12.so /usr/lib/xorg/modules/drivers/tegra_drv.so
Note: without using an xorg.conf file, by default it will use fbdrv instead of the tegra driver.
12) set the root password:
Code:
passwd root
13) add a normal user:
Code:
adduser <username>
14) exit chroot by typing "exit" and unmount /mnt/Linux:
Code:
sudo umount /mnt/Linux
15) pop that sucker into the the tablet and boot into it by holding power and vol down to get into the boot menu. select "boot into second partiton".
If everything went ok, you should be presented with a gui, if not and you are at a command line, log into root and type "startx". if that doesnt work then something wrong must have happened.
Untested easy script:
Code:
#! /bin/sh
set -e
#if there is a tegra_install.deb file.
hasTegraDeb=0
tegraDeb=acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-1_armhf.deb
#change these if you do not like default install of kde.
arch=armhf
build=wheezy
rootDir=/mnt/Linux
guiEnv=kde-full
newUser=User
#setup the basics of debian linux using armhf and wheezy build.
qemu-debootstrap --arch $arch $build $rootDir
#copy the tegra_install.deb file for the tegra specific drivers.
if ["$hasTegraDeb" = "1"] then
cp $tegraDeb $rootDir/$tegraDeb
fi
#setup sources.list for apt-get.
echo "deb http://ftp.us.debian.org/debian testing main contrib non-free" >> $rootDir/etc/apt/sources.list
echo "deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free" >> $rootDir/etc/apt/sources.list
echo "deb http://security.debian.org/ wheezy/updates main contrib non-free" >> $rootDir/etc/apt/sources.list
#create the chroot_install.sh script and set it up.
echo "#! /bin/sh" > $rootDir/chroot_install.sh
echo "set -e" >> $rootDir/chroot_install.sh
#update apt-get inside the chroot.
echo "apt-get update" >> $rootDir/chroot_install.sh
#install the wireless card drivers inside the chroot.
echo "apt-get install broadcom-sta-common broadcom-sta-source firmware-b43-installer firmware-b43legacy-installer b43-fwcutter" >> $rootDir/chroot_install.sh
#install the desktop in the chroot. (note: this will take a long time)
echo "apt-get install $guiEnv" >> $rootDir/chroot_install.sh
#install the tegra specific drivers inside the chroot
if ["$hasTegraDeb" = "1"] then
#install the tegra drivers.
echo "dpkg -i $tegraDeb" >> $rootDir/chroot_install.sh
#hard link the tegra_drv.abi12.so as tegra_drv.so in /usr/lib/xorg/modules/drivers/ to enable X11 to find the display driver.
echo "ln /usr/lib/xorg/modules/drivers/tegra_drv.abi12.so /usr/lib/xorg/modules/drivers/tegra_drv.so" >> $rootDir/chroot_install.sh
fi
#set the root password in the chroot.
echo "passwd root" >> $rootDir/chroot_install.sh
#add normal user in the chroot.
echo "adduser $newUser" >> $rootDir/chroot_install.sh
#execute the final stage of the install.
chroot $rootDir /chroot_install.sh
#cleanup
rm $rootDir/chroot_install.sh
if ["$hasTegraDeb" = "1"] then
rm $rootDir/$tegraDeb
fi
Script sets up everything along with installing kde window manager. Please note that the tegra_install.deb file does not exist, it is something that i am thinking of making in the future that has all the drivers and what not needed that is from the Linux 4 Tegra site. you are still going to have to manually install the tegra drivers in step 11.
Edit: Experimental copies of the deb files that has all the files needed from Linux 4 Tegra and the wifi drivers can be found at the bottom of the post.
xorg.conf to enable tegra driver (found in the Linux_for_Tegra/nv_tegra/config.tbz2/etc/X11 folder):
Code:
# This is the minimal configuration necessary to use the Tegra driver.
# Please refer to the xorg.conf man page for more configuration
# options provided by the X server, including display-related options
# provided by RandR 1.2 and higher.
# Disable extensions not useful on Tegra.
Section "Module"
Disable "dri"
Disable "dri2"
Disable "glx"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
EndSection
Section "Device"
Identifier "Tegra"
Driver "tegra"
# OverlayDepth is a 32-bit integer which is used to control overlay
# stacking order. The overlay with the lowest depth is in front of
# all others. This value has meaning only when multiple overlays are
# present on a display.
# Option "OverlayDepth" "255"
# ARGBHWCursor controls whether the X driver uses an overlay to
# display 32-bit "true-color" cursors, or whether such cursors are
# emulated in software. Valid values are "true" to enable hardware
# cursors, and "false" (default) to disable them.
# Option "ARGBHWCursor"
EndSection
At the moment, I have looked through the config.tbz2 file and may have to stick the stuff in there into the tablet's linux filesystem. will test this later.
NOTE:
I am not a linux developer, I have no idea how to create linux drivers. All I can do is mash things together and hope things work out.
In theory, this should work for all tegra2 and tegra3 (using cardhu drivers instead of ventana) devices with some minor differences.
Edit:
Apparently it is using kernel version 2.6.38. I'm going to see if I can update the kernel to 3.2.23-1 which is the latest version for armhf in the debian package list (http://packages.debian.org/wheezy/kernel/linux-headers-3.2.0-3-all-armhf).
Edit2:
Looks like updating the kernel from apt-get doesn't necessarily enable the kernel to load as it seems that the boot loader loads a prepackaged kernel that has been flashed into mmcblk0p7. Tried out kexec and the kernel doesn't support it so adding it to the /dev/inittab script is useless for loading up new kernels. I tried making the new kernel into a flashable image using mkbootimg that is found within the Linux 4 Tegra folder but it doesn't do anything and the image apparently isn't valid when i tried booting it from fastboot (black screen). along with that, apparently it changed my password on my encrypted /data partition's password (when i flashed it within linux using dd) so a word of caution with that. If anyone can help me out, i would like to try to create something similar to grub (or even port it) where it loads up new kernels from the microsd or a specified place based on a boot list.
deb Files (Install using "dpkg -i acer-iconia-tab-a500+tegra+brcm+wheezy_<version>_armhf.deb" within the linux environment of the tablet.):
1.0-1: acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-1_armhf.deb
--takes care of steps 9 and 11 sans hard linking the X11 tegra drivers.
1.0-2: acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-2_armhf.deb
--has pre-depends for the first part of the wifi driver installation so this should, in theory, install both part 1 and 2 of the wifi drivers.
--takes care of steps 8, 9, and 11 sans hard linking the X11 tegra drivers.
Update log:
10/17/2012: added updated version of the deb package.
10/16/2012: first version.
Ok, so since I cant post anything including into ongoing threads in the android development forum due to the 10 post required thing i'll just have to ask development questions here till i reach the 10 post requirement.
Can anyone point me into the direction for how the second boot image that you flash for the dual boot bootloader is created? Trying to figure out how to create an image so that it boots everything off the microsd card including the kernel. It seems that the kernel used in the guide is locked to 2.6.38 and if you update the kernel within the tablet's linux environment it doesnt load it up. so i need to figure out how to create a boot image so that it loads it up or create a boot image that has grub (or other bootloaders) installed on it to boot different linux images.
alatnet said:
Ok, so since I cant post anything including into ongoing threads in the android development forum due to the 10 post required thing i'll just have to ask development questions here till i reach the 10 post requirement.
Can anyone point me into the direction for how the second boot image that you flash for the dual boot bootloader is created? Trying to figure out how to create an image so that it boots everything off the microsd card including the kernel. It seems that the kernel used in the guide is locked to 2.6.38 and if you update the kernel within the tablet's linux environment it doesnt load it up. so i need to figure out how to create a boot image so that it loads it up or create a boot image that has grub (or other bootloaders) installed on it to boot different linux images.
Click to expand...
Click to collapse
You are on the right track with mkbootimg. I have not figured it all out myself yet.
You have to compile your arm linux kernel then make a bootable image with mkboot
I don't know if you have seen this or if. this will help---Nethams kernel compile commands are;
make ARCH=arm menuconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueable--j16
./mkbootimg --ramdisk dev/zero --kernel arch/arm/zimage -o ../recovery.img
I believe these are the commands he uses to compile his recovery image (boot.img)
It is my understanding that mkboot combines the kernel with a ram disk to make an image file that will boot the system
That image file can be placed in several places 1-primary boot position 2 recovery position 3 and if you have Skrilax dual boot secboot position
So it depends on what mkboot compiled as to what happens when that boot point is activated.
I am still trying to work out how Spdev and Netham combine or configure the kernel + initramfs+ ramdisk to create their bootable images.
I know these images boot and point to the file system which can be stored on internal or external sd card or even usb drive it all depends on how the boot image is configured.
Still learning myself
Here is a link I found explanes about Linux ram disk and initram
http://www.ibm.com/developerworks/linux/library/l-initrd/index.html
And more info here downloads a PDF presentation on how to.
http://www.google.com/url?sa=t&rct=...poCoAw&usg=AFQjCNHLTHE3DaroC71FAjOjQWU2A61qEQ
All about that mkbooting after you get your kernel
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
themechaniac said:
snip (freaking 10 post limit...)
Click to expand...
Click to collapse
Yea, i did find some stuff with mkbootimg including the last link that you posted.
The kernel was already compiled when i downloaded it using apt-get and it is placed in /boot folder.
I did make a boot.img from that kernel using mkbootimg and looking at "/proc/cmdline" at the arguments that were passed to the kernel in the other kernel image and it made it, flashed it to secboot and it didnt do anything except use the same kernal as before, though i did flash the image via dd in linux. Apparently this sorta screwed up my /data partition or something in where it wouldnt recognize my password for de-encryption to mount it. (fixing it by just erasing "/data" [bye bye data... TT.TT]) So i tried booting it using "fastboot boot <kernel>" and it didnt boot, only showing a black screen, but using the other boot.img it would boot linux up.
So I'm thinking of somehow creating a kernel image that can use kexec to make a grub like bootloader kernel that you flash onto the secboot partition that has something similer to grub.cfg in which you can easily select which kernel to load.
As for looking for a grub.cfg file, it would look in a few different places:
-in internal storage (probably recovery partition or the "/system" partition as the "/data" partition can potentially be encrypted and not mountable.)
-sd card (has to be in first partition and in fat32 format)
-usb drive (same as sd card)
from these places it will load each grub.cfg. that way it'll make the grub like bootloader kernel extendable in which kernel to load (i.e. have a linux system on usb that you want to boot from.)
I may be wrong but it is my understanding that the compiled kernel is in the boot image packed by mkbootimg.
The kernel is compiled to look for the compatible root file system in a particular place.
So when you change or use a boot image you change the kernel you are using.
So we have a system that;
Has a modified Linux kernel that selects the Android file system from internal memory installed in the first boot position.
We can put a Linux kernel compiled to find a compatible root file system say on external sd card in the second boot position.
We can replace the recovery image with a Linux kernel that finds a compatible root file system on the internal sd card.
That gives us a hardware selective three different systems (triple boot)
With fastboot on the PC we can quickly change any of the Three boot images, replace the recovery image or repair system.
I think all we need is a 3.2.23 kernel compiled thee separate ways and packaged with mkbootimg.
1st find root file system internel, 2nd find file system externel 3rd find file system usb
We already have two 2.6.38 kernels. One from Spdev (external root file system)and One from Netham {internal file system)
They are different kernels as Nethams has added modules.
I believe the were both compiled from the same Git.
I have tried switching the two boot images in second boot position with both root file systems installed and when you boot the second position
it switches to it's own file system.
I haven't tried swapping the root file positions yet.
themechaniac said:
I may be wrong but it is my understanding that the compiled kernel is in the boot image packed by mkbootimg.
The kernel is compiled to look for the compatible root file system in a particular place.
So when you change or use a boot image you change the kernel you are using.
So we have a system that;
Has a modified Linux kernel that selects the Android file system from internal memory installed in the first boot position.
We can put a Linux kernel compiled to find a compatible root file system say on external sd card in the second boot position.
We can replace the recovery image with a Linux kernel that finds a compatible root file system on the internal sd card.
That gives us a hardware selective three different systems (triple boot)
With fastboot on the PC we can quickly change any of the Three boot images, replace the recovery image or repair system.
I think all we need is a 3.2.23 kernel compiled thee separate ways and packaged with mkbootimg.
1st find root file system internel, 2nd find file system externel 3rd find file system usb
We already have two 2.6.38 kernels. One from Spdev (external root file system)and One from Netham {internal file system)
They are different kernels as Nethams has added modules.
I believe the were both compiled from the same Git.
I have tried switching the two boot images in second boot position with both root file systems installed and when you boot the second position
it switches to it's own file system.
I haven't tried swapping the root file positions yet.
Click to expand...
Click to collapse
Interesting. Though i think it needs to be a specific type of kernel (i.e bzImage or uImage instead of vmlinuz) to actually run. also, the precompiled kernel in the guide that i had used in the opening post had a command line where one option was "root=/dev/mmcblk1p2" which pretty much says for the kernel to look for the linux file system in the second partition on the sd card.
Yes with the way the system is formatted you cannot change out the kernel on the fly. It is basically hard coded in the boot image. Skrilax has given us a way to change boot positions so we don't have to sacrifice recovery position to boot second kernel. I have not seen any pre configured 3.2.23 kernels yet. The one that Netham posted boots from internal SD but causes problems for some people as not all a500 have their internal SD card formatted in the same memory block. It works great for me I prefer to have my root file system on a fast external SD so would like to modify or compile a kernel like Netham's. I find I run out of space when I have it internal. Netham's kernel has USB sound and seems to boot differt than Spdev's.
themechaniac said:
Yes with the way the system is formatted you cannot change out the kernel on the fly. It is basically hard coded in the boot image. Skrilax has given us a way to change boot positions so we don't have to sacrifice recovery position to boot second kernel. I have not seen any pre configured 3.2.23 kernels yet. The one that Netham posted boots from internal SD but causes problems for some people as not all a500 have their internal SD card formatted in the same memory block. It works great for me I prefer to have my root file system on a fast external SD so would like to modify or compile a kernel like Netham's. I find I run out of space when I have it internal. Netham's kernel has USB sound and seems to boot differt than Spdev's.
Click to expand...
Click to collapse
Right, but this is how the linux boot loader is going to go with, instead of loading the linux system (sans kernel and initrd) from the sd card, we create a boot.img that has a linux system built in that has a sole purpose of loading other linux systems using kexec.
Edit:
Here's how the path is going to go:
Startup-->Bootloader-->Linux Bootloader (loads linux on external drives)-->Linux (on external drives)
Well I am happy with Ubuntu on my external SD card, I even ran a kernel compile on it and it ran pretty fast. I am stuck on the mkbootimg part. It can't be done on the tablet, has to be a PC. I tried unpacking the Two ready made boot images to see how they are configured but they don't seem to have a ram disk. Still working on that. It is learning how the system is put together that is half the fun, Getting it to work the way you want is the goal. When it is all squared away it will be time to move on to the next puzzle. I have enough computers that I could just put a system on each one and be done with it. Where's the fun in that. Most of them are dual booted already.
themechaniac said:
Well I am happy with Ubuntu on my external SD card, I even ran a kernel compile on it and it ran pretty fast. I am stuck on the mkbootimg part. It can't be done on the tablet, has to be a PC. I tried unpacking the Two ready made boot images to see how they are configured but they don't seem to have a ram disk. Still working on that. It is learning how the system is put together that is half the fun, Getting it to work the way you want is the goal. When it is all squared away it will be time to move on to the next puzzle. I have enough computers that I could just put a system on each one and be done with it. Where's the fun in that. Most of them are dual booted already.
Click to expand...
Click to collapse
Well, even though mkbootimg is suppose to be run on linux, i don't think it was compiled for arm so you are going to have to use a pc for that program. as for the initrd, i did find a website that may help in creating an A.L.B.L. (Android Linux Boot Loader): http://www.thewireframecommunity.com/node/14
Essentially what is needed to create the A.L.B.L. is to create a kernel with kexec in it and an initrd that mounts the external drives along with an easy to use interface to be loaded before loading any kernels to allow for selecting kernels. with that said, how do you figure out how to use the volume buttons and the power button within linux using a c\c++ program?
BUMP!
any progress?
also
-Audio (Detects it in the kde info center. System Settings program only says that there's a dummy output. Playing any form of audio crashes the program.)
Click to expand...
Click to collapse
But
Code:
cat /any/file/for/ex/bin/bash > /dev/dsp
works properly
Unfortunetly no.
Been to busy with other stuff to work on this.
tegra driver
I have ubuntu 12.10 armf runing on my a500 thanks to the "Linux on A500: The Future" thread. I am using the ferrariforzaleo mod of rogro82's kernel.
The problem I had was getting the xorg tegra module to load. I fixed this by getting the "https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1"]https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1 and installing with
sudo dpkg -i
after I rebooted it started using the tegra video driver.
Cheers
HardlyAbelson said:
I have ubuntu 12.10 armf runing on my a500 thanks to the "Linux on A500: The Future" thread. I am using the ferrariforzaleo mod of rogro82's kernel.
The problem I had was getting the xorg tegra module to load. I fixed this by getting the "https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1"]https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1 and installing with
sudo dpkg -i
after I rebooted it started using the tegra video driver.
Cheers
Click to expand...
Click to collapse
can you explain me the steps you done ? I also want ubuntu 12.10 running but I can't install any desktop on it ( show error and other error )
ubuntu 12.10
Forzaferrarileo said:
can you explain me the steps you done ? I also want ubuntu 12.10 running but I can't install any desktop on it ( show error and other error )
Click to expand...
Click to collapse
Hi, I used the debootstrap and and qemu / chroot to setup my rootfs. i found post #61 in the "Linux on A500: future" very helpful.
Also, make sure you have a usb keyboard handy. After you run "apt-get install -d ubuntu-desktop" (assuming you have a pc running ubuntu to use) in a qemu chroot, you can move to the a500 and boot up and login as root and run "apt-get install ubuntu-destop". since the stuff is cached. I found this faster than installing the desktop while in the chroot. After that finishes, you should boot up with a desktop available. If something is wrong and you can't login, try doing "ctrl-alt-f1" to get to the getty command line login and look at the /var/log/ folder for clues in the logs.
How to compile the kernel?
I succesfully got debian running on my iconia a500 :laugh:
Building my own rootfs and getting the wifi to work were not that hard, but I still don't know how to compile the Linux kernel for the a500 from source.
I already found the git repository of rogru82 (https://github.com/rogro82/picasso-kernel) and I downloaded the source to my pc (running ubuntu 13.04). Can someone point me to a tutorial explaining how to compile this source?
Also, can someone explain what sort of partition table the internal memory uses? I am running the 3.0 kernel and I can see a block memory device in the /dev folder but there are no partitions. How can I mount the internal memory?
I present to you
Project POC - Phoenix OS Custom
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1.Pre-rooted with SuperSU 2.76
2.Busybox
3.CM File Manager (root access to files)
4.Deodexed
5.Adaway
Changelog for Project POC
V1.1.0
First Build
Added SuperSU 2.76
Added Busybox
Added CM File Manager
Added Deodex
Added Adaway
Install Instructions:
1. Extract Project POC
2. Run Phoenix OS Installation Tool
3. Select desired install location: Hard Disk or USB
4. Select target drive and partition
5. Press next and choose data partition size and continue to allow the installer to finish
6. Copy system.img from the POC zip you extracted to the install location (eg. C:\PhoenixOS\)
Downloads:
Google Drive
32-bit only:
V1.1.0 https://drive.google.com/open?id=0B-mpriMWe2WUcjhhbnZXNzdYUHM
Credits:
PhoenixOS for providing us with an awesome OS
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
Android (Google) for Android
CyanogenMod Team for the apps
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
I am trying to install on ASUS T100, no windows. I get usb stick made and it just boots to GNU GRUB grub> command line. Any ideas?
Thanks in advance,
Gary
I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect
meanhacker said:
I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect
Click to expand...
Click to collapse
I'm not entirely sure of this, but it could possibly have broken the ability to update via OTA.
It would make sense that OTA Updates won't work due to foreign files (SU, CM APPS) in the system partition.
Does it replace win bootloader with grub?
XPOSED FRAMEWORK INSTALLATION ON PHOENIX OS
Hello guys ,
After A long time ,Sir @youling257 released latest x86_64 Xposed Frameworks v89 for SDK25
It booted far eaisly with xposed frameworks being active.
Instructions:-
Similar to those of RemixOS ,
1.Download official xposed-v88 sdk25 x86 zip from
Framework http://dl-xda.xposed.info/framework/sdk25/x86/xposed-v88.1-sdk25-x86.zip
For x86_64
Framework https://github.com/youling257/XposedTools/releases
<------------+++++++++++++++++++++++++++++++++------------->
Installer
https://forum.xda-developers.com/showthread.php?t=3034811
No need for x86_64
<------------+++++++++++++++++++++++++++++++++------------->
2.Decompress it and copy the system folder and flash-script.sh (located at /META-INF/com/google/android/) from extracted folder .put them in a seperate folder inside /system partition or in root of hdd partition where is your PhoenixOS folder resides.
For x86_64 ,just decompress zip in Xposed folder and put folder in /system/*(here)
3.Boot Grub and select debug option if you have otherwise.hover over normal boot and press e to edit the boot option
Add
Code:
DEBUG=1
at the end of kernel args.
before the last line for initrd (not in this line).
And boot it with F10
4.Now ,in debug Mir-shell.Go to /mnt/* if you placed it in root parttion of your PhoenixOS folder from Windows 10 or in /system/*/ folder if you placed it there.
Code:
cd /mnt/xposed/ //for me * is xposed
Or
cd /system/xposed/
* is the folder where you copied flash-script.sh and system folder.
Now run
Code:
sh flash-script.sh
For x86_64
Code:
sh script
It should flash latest xposed framework .Ignore failing to set selinux file contexts for files.
Now simply reboot .
Credits
youling257
Camlin3 said:
XPOSED FRAMEWORK INSTALLATION ON PHOENIX OS
Click to expand...
Click to collapse
Hi!
I've installed version 1.5.0 of Phoenix OS 32bit (not UEFI). How do I install Xposed?
Maybe it's not booting by Grub.
I've tried to install Xposed Framework by using the XposedInstaller.apk on Phoenix OS. But after installation and reboot, my Phoenix OS was failed to boot and stuck at logo.
(p/s) Do you know how to disable the "Change Keyboard" window popup when pressing the "Ctrl+Shift" key combination? I try to using Xposed for this reason.
Please help!
Need your expertise
Hi there, I'm new here and need your help with setting up exposed on phoenix os.
Will you please help me with detailed and step by step guidance. Or can you share screen shot of each of the steps you've listed in the process.
I really want to set this up, hope you'll be able to find time to help me out here.
Thank you...
mcuong said:
Hi!
I've installed version 1.5.0 of Phoenix OS 32bit (not UEFI). How do I install Xposed?
Maybe it's not booting by Grub.
I've tried to install Xposed Framework by using the XposedInstaller.apk on Phoenix OS. But after installation and reboot, my Phoenix OS was failed to boot and stuck at logo.
(p/s) Do you know how to disable the "Change Keyboard" window popup when pressing the "Ctrl+Shift" key combination? I try to using Xposed for this reason.
Please help!
Click to expand...
Click to collapse
Unfortunately PhoenixOS based upon lollipop aka x32 bit doesn't support xposedc,it caused bootloop.
Sunnyghoshal said:
Hi there, I'm new here and need your help with setting up exposed on phoenix os.
Will you please help me with detailed and step by step guidance. Or can you share screen shot of each of the steps you've listed in the process.
I really want to set this up, hope you'll be able to find time to help me out here.
Thank you...
Click to expand...
Click to collapse
Since,there is no 32 bit more pos on nougat so it can't be helped .For x64 device,no developer is interested in making xposed framework for x86_64 devices.
Thread Updated .
unable to install xposed on phoenix os 64 bit missing script file?
hi i followed your instructions to get xposed installed on a 64bit phoenix os, but the zip file [xposed framework by youling257] that u gave for the 64bit does not have a "script" file inside it,so can u be a bit more clear as to how you managed to install the xposed framework. cos going through your instructions u told to run the script file for the 64bit is that some custom script u wrote to install the framework if so can u please provide that for download as well.
nitroboozter said:
hi i followed your instructions to get xposed installed on a 64bit phoenix os, but the zip file [xposed framework by youling257] that u gave for the 64bit does not have a "script" file inside it,so can u be a bit more clear as to how you managed to install the xposed framework. cos going through your instructions u told to run the script file for the 64bit is that some custom script u wrote to install the framework if so can u please provide that for download as well.
Click to expand...
Click to collapse
You can use updater-script Instead ,however here it is ,put it beside system folder and set permission executable .
I tested this on Bliss x86 7.2 Stable, and it worked great.
I took the x86_64 zip and extracted it's contents into a folder named 'system'. I then put the 'system' folder and installer script into '/tmp'. I then opened terminal, elevated privileges with 'su', then executed the installer script.
Okay, I tried various methods mentioned here.
I have latest Phoenix OS, of course x86_64, sadly no more stable x86 anymore.
I have Framework downloaded from https://github.com/youling257/XposedTools/releases
Then extracted it, TWICE, one with folder and one with contents of inside folder. So I had 3 possible types of same thing (zip, folder, extracted from folder)
Now those 3 things, and also, with script.txt and a copy renamed top script.sh, 5 total were moved to /system,/mnt,/sdcard.
As you can see, I left no chance of lack of anything. Yet I got errors. (attached)
Then I tried with no apk, as mentioned no installer needed. I got various errors.
I then downloaded it, placed in priv-app with XposedInstaller.apk name, also installed it.
Then still I got errors. (Look at attachment)
I have also attached the script I am keep using. Is it for 32bit or what?
Please do help. This Xposed thing made me reinstall my 5 multiple OS booting system to REINSTALL.
fddm said:
I tested this on Bliss x86 7.2 Stable, and it worked great.
I took the x86_64 zip and extracted it's contents into a folder named 'system'. I then put the 'system' folder and installer script into '/tmp'. I then opened terminal, elevated privileges with 'su', then executed the installer script.
Click to expand...
Click to collapse
Which script you use. Mine give error xposedinstaller.apk not found and after installation finished when i manually install xposedinstaller.apk its says xposed is installed but not active.
On phoniex 2.6.3
netship said:
Which script you use. Mine give error xposedinstaller.apk not found and after installation finished when i manually install xposedinstaller.apk its says xposed is installed but not active.
On phoniex 2.6.3
Click to expand...
Click to collapse
Sounds like it should be working. Maybe check that the toggle at the top right of xposed installer is enabled and give it a reboot?
Yeah! it is working now
Thanks much for this. Running LineageOS 14.1 r2 x86_64. Used the files from the OP's github link, dropped the extracted files into my system folder with X-plore file manager, rebooted and was ready to go. Simple and easy, I appreciate it!!!
Seems to be running, installer says Xposed framework active, but I can not download and install any module installer reports permission issues, but LOS 14.1r2 us rooted (I'm using 32bit system)
Any help?
Camlin3 said:
XPOSED FRAMEWORK INSTALLATION ON PHOENIX OS
Click to expand...
Click to collapse
Thank you friend
You're just a wizard.
the truth is I'm not using Phoenix OS, but Lineage OS 14 x86_64, but according to your instructions it works.
pepelillo said:
Seems to be running, installer says Xposed framework active, but I can not download and install any module installer reports permission issues, but LOS 14.1r2 us rooted (I'm using 32bit system)
Any help?
Click to expand...
Click to collapse
If you got issues about xposed, you can install Xposed Framework with Android PC Toolbox.
https://forum.xda-developers.com/ph...release-phoenixos-android-pc-toolbox-t3748153
PizzaG said:
Thanks much for this. Running LineageOS 14.1 r2 x86_64. Used the files from the OP's github link, dropped the extracted files into my system folder with X-plore file manager, rebooted and was ready to go. Simple and easy, I appreciate it!!!
Click to expand...
Click to collapse
DoanART said:
Thank you friend
You're just a wizard.
the truth is I'm not using Phoenix OS, but Lineage OS 14 x86_64, but according to your instructions it works.
Click to expand...
Click to collapse
You people can hit thanks instead or a little free will donation to sir @youling257 will be appreciated.I mean see yourself, from almost 2years ,No one dared to release xposed for x86_64 but @youling257 has done this again after Solarwarez ,even rovo89 himself declined my request many times. But who cares.
can't install on x64 AMD A8
always show not compatible with ur architecture
Yohanes_Adi said:
always show not compatible with ur architecture
Click to expand...
Click to collapse
Try editing build.prop for same architecture value ....
PS:BTW its weird ...
{
"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"
}
Latest Stable Magisk Version: v15.3
Latest Magisk Manager Version: v5.5.5Installing Magisk will give you ROOT, a super powerful Systemless Interface,
Magisk Modules support, and hide from tons of integrity tests like SafetyNet!Magisk only modifies the boot image and install files to /data and /cache
Your /system partition will only be modified if root is installed in /system, or using custom rom with addon.d support!
This Guide has been deprecated,Try Post#7
Before Proceeding , Beware that after this modification ,you will loose ALT+F1 TTY shell completely and you will only get back that after restoring original ramdisk.img.Mirroring System Image is still not working .So Limited Function
Requirements:
1.Linux OS or Windows OS (optional)
2.Phoenix_OS or any Android-x86 based Distro
3.Magisk Manager App
Installation Instructions
1.In Linux OS
Download android-tools-mkbootimg ,abootimg packages
For Debian Based Distros:
Code:
sudo apt install android-tools-mkbootimg abootimg
Copy ramdisk.img and kernel from Phoenix os iso and put in Home Directory
Now put these commands in terminal
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
Copy generated boot.img somewhere you can access in Phoenix OS
2. Now boot into Phoenix OS and Download Latest Magisk Manager from Official Github Repo
3. Now open Magisk Manager and Tap Install
Choose Patch boot.img
Select boot.img generated earlier
Now ,it will save patched img in /sdcard/MagiskManager/patched_boot.img
Save it somewhere again where you can access it in Linux OS
Go to ALT+F1 (ALT+Fn+F1) TTY and run these codes
Code:
cd /system/xbin && mv su su.bak
4. Go into Linux OS :
Open Nautilus and copy patched_boot.img in Home Directory
Now open terminal and enter these :
Code:
abootimg -x patched_boot.img
It will generate kernel and initrd.img file in Home directory
Rename initrd.img to ramdisk.img and replace with original ramdisk.img in Phoenix OS Installation Directory
5.Cool! Its Done ,Check Magisk Manager to confirm Root Access and Enjoy Magisk Latest features.
6.For Windows OS users ,check Sir [email protected] Android Kitchen thread for extracting and recompiling boot.img .
Further for sole Androidx86 users check CNexus thread .
Downloads:
I have done one for Phoenix OS 2.5.7 .see attachment ,backup original one and replace it.
This method will work for Any Android-x86 Distros like Bliss-x86 , LOS-x86 etc.
Credits:
topjohnwu
osm0sis
Ifom
Android-x86 Developers
PhoenixOS Team
Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage
gps3dx said:
Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage
Click to expand...
Click to collapse
1.There is no mm release of phoenixOS ,btw for Lollipop ,you can try .it should work
2.Nope lomount is still not working ,limited system tweaks @topjohnwu still silent
Camlin3 said:
Download android-tools-mkbootimg ,abootimg packages
Click to expand...
Click to collapse
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.
DaniDeVega said:
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.
Click to expand...
Click to collapse
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1
2.5.9
Does this also work for 2.5.9?
Works perfect for Windows users. This would help more people with same issues.
Camlin3 said:
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1
Click to expand...
Click to collapse
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .
Jpalmer82 said:
Does this also work for 2.5.9?
Click to expand...
Click to collapse
Yess
Camlin3 said:
@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .
Click to expand...
Click to collapse
Yes, so I just did a little traduction of the chinese link you gave me, so I don't know yet if post this here (with or without mentioning the owner of the work) is forbidden or not on XDA.
If so, then, I would like to talk with a high rank member to explain and find any kind of way to let this be on xda too. :fingers-crossed:
This translation could help here so many people who would be with the same kind of issues to install Magisk on Phoenix OS that I found until finally you told me to review the link that gets me the solution, and I translate, just like a very helpful suggestion. :good:
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
This method works on 2.6.2 but How can I update Magisk?
And None of the modules that I have tried get enabled after rebooting
Update: Any module that has an app it requires you to install the app separately all other modules work fine
Hello, how to update pls :silly:
after the installation the internet was working, but after reboot, the internet stopped working, even configuring an static ip.
I'm using a desktop with wired cable and I don't have wireless network card
1.5.0 x86 Phoenix OS
Sorry for my bad english and sorry for posting here.
Hi ,the tools you mentioned I didn't find on CentOS, could you please give a repo address or direct RPM address? Thanks.
Does this method work in other android-x86? cm-14 r1, bliss etc?,
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
I couldn't have it work on x86 5.0.1
It boots back to BIOS
There's anyway for use phoenix os 3.0.5 or 3.0.6
I'am using windows,want use magisk
It works but after using it for a few minutes it reboots. Any fix?
Ytim08 said:
It works but after using it for a few minutes it reboots. Any fix?
Click to expand...
Click to collapse
I didn't get that ,if you can upload log ,I may help
Camlin3 said:
I didn't get that ,if you can upload log ,I may help
Click to expand...
Click to collapse
If I could get a logcat I could've maybe fixed it myself already, the problem is it reboots and logs are reset
Edit: out of curiosity, were you able to successfully install magisk 18 on latest Phoenix is version? It works for a couple minutes and then crashes and I have to hard reset