Related
I hope to meet some people willing to help me,
HaRET works out of the box for me doesnt recognizes my devices MTYPE It only says MSM72xx default, but seems HaRET works fine cause when trying to boot a linux image i get till "Go Go Go ..." But only with one kernel config i got a fullscreen purple flicker. But no console seen till now!
As i'm new to such stuff I want to write down all my expiriences to get things to work, for others with new devices.
I did in haret console:
INPUT: print VRAM %08x
OUTPUT: 0x10000000
INPUT: pfh 0x10000000 640*480 0x00ff
(640*480 is my windows mobile resolution, 0x00ff is blue color code 0xffff is white and 0x0000 is black colorcode if you do 640 * 2 you will get 2 blue lines not full screen repaint)
i did an mmu dump i was told it would help me in haret console i did
INPUT: log mmutrace.txt
INPUT: dump MMU
now i could connect to my device and in de dir of haret i got a file called mmutrace.txt (i attached it)
For more detailed logging create an empty file called earlyharetlox.txt in the same dir haret.exe is lýing in.
I Will write on when i get more to know, hopefully soon.
Greets Neutron
ps. sorry for my englisch im not that good at it
Hi there,
I have being trying to boot into my Ubuntu 10.10 with WIndows 8 Developer Preview installed, and I have found a quick workaround (I think most of you will probably know it already, but I'll post it here anyway for those who don't )
Firstly, install the Linux distribution of your choice (I tested with Ubuntu 10.10, so I'm not sure about any other OS's!)
Next, grab a copy of Super Grub2 Disk off supergrubdisk.org (can't post links yet... too new! ;-) ) and burn it to CD/DVD/USB.
Then, reboot your PC with Super Grub2 Disk in and select your boot device from the boot menu (I pressed F12 on my Acer) and Super Grub2 Disk should load. Select "Detect Any OS" (the first option) and wait while it scans your partitions for operating systems.
It should then display something like "linux 3.0.0-12-generic", "linux 3.0.0-12-generic (single-user mode)" and "Windows Vista (bootmngr)" (I thought the Vista bootmngr was a bit strange - must be the same boot manager as in earlier versions, but with linux-crippling secureboot :-( ). Select linux 3.0.0-12-generic and you are done!
You can now safely remove the disk. For (nearly) seamless usage, burn Super Grub2 Disk to a USB drive and tweak the BIOS settings to boot off said USB drive!
Enjoy
Simpler: after doing this and booting into Ubuntu, reinstall grub via the terminal or software center, problem solved, no more CD needed. (I used this method to triple boot between Ubuntu 11.04, Win7, & Win8)
Sent from my Sensation using Tapatalk
NikolaiT said:
Simpler: after doing this and booting into Ubuntu, reinstall grub via the terminal or software center, problem solved, no more CD needed. (I used this method to triple boot between Ubuntu 11.04, Win7, & Win8)
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
I hadn't thought of that - thanks!
Hi I'm trying to get other OS's to Intel Atom Baytrail-T Windows 8.1 tablet, and so far I have managed to get the following booted to the desktop:
Ubuntu and variation(all)
Puppy Linux Slackware
So I'm asking why you don't make a LiveUSB image, so people can try before installing - not every HW in the world is compatible, so wasting time on installing only to find out that you HW is not compatible could give this OS a bad rep..
Also, something that are not very clear on your homepage: After install, how do you install app's? I don't see Google Play store mentioned anywhere.
With kind regards
JBJ
EDIT: HW spec here incl. the parts I found in linux:
http://www.murga-linux.com/puppy/viewtopic.php?p=925141#925141
insomniacno1 said:
Hi I'm trying to get other OS's to Intel Atom Baytrail-T Windows 8.1 tablet, and so far I have managed to get the following booted to the desktop:
Ubuntu and variation(all)
Puppy Linux Slackware
So I'm asking why you don't make a LiveUSB image, so people can try before installing - not every HW in the world is compatible, so wasting time on installing only to find out that you HW is not compatible could give this OS a bad rep..
Also, something that are not very clear on your homepage: After install, how do you install app's? I don't see Google Play store mentioned anywhere.
With kind regards
JBJ
Click to expand...
Click to collapse
The iso can be burned to a USB and run as a live session. I'm confused. Not really sure what it is you are asking. Also, the current version has some incompatibly with Baytrail devices. There is an Alpha version out for that, though.
I don't have any experience with those devices but I think @Vioner and @greatbal do. Maybe one of them can chime in.
Play store is in the app drawer in Google folder.
I'll test Phoenix OS USB on my Baytrail device and get back to you.
@bg260 - It is not clear in the description that it can be burned as a LiveUSB - thats why I asked - it says that it can be made as bootable USB installer. I'm not interested in installing it on the internal storage right now, I wanted to run it from the USB first to see if all HW got recognized, and if rotation were working.
In Linuxium and Puppy Linux Slacko I could not get sound or rotation to work - still working on that.
@Vioneer - Cool I will wait
insomniacno1 said:
@bg260 - It is not clear in the description that it can be burned as a LiveUSB - thats why I asked - it says that it can be made as bootable USB installer. I'm not interested in installing it on the internal storage right now, I wanted to run it from the USB first to see if all HW got recognized, and if rotation were working.
In Linuxium and Puppy Linux Slacko I could not get sound or rotation to work - still working on that.
@Vioneer - Cool I will wait
Click to expand...
Click to collapse
Oh OK. I thought you were referring to the iso that I created.
Here you go. I made this for you. It is an Alpha release. Baytrail compatible to a point . Very hush, hush......so you didn't get it from me
Remember this is only for testing please feel free to report issues, but it is not intended to be a fully functioning system yet.
Phoenix OS Baytrail/Mesa .iso
You can either follow my guide here:
http://forum.xda-developers.com/android/development/guide-phoenixos-v1-0-9-rooted-iso-gapps-t3420779
or use my portable guide:
View attachment AndroidX86+Install+Guide+Installer.zip
Just unzip, open the folder and run the <HTML> with your web browser.
Let me know how it goes:laugh:
Do you see why I may have been a little confused?
bg260 said:
Oh OK. I thought you were referring to the iso that I created.
Here you go. I made this for you. It is an Alpha release. Baytrail compatible to a point . Very hush, hush......so you didn't get it from me
Remember this is only for testing please feel free to report issues, but it is not intended to be a fully functioning system yet.
Phoenix OS Baytrail/Mesa .iso
You can either follow my guide here:
http://forum.xda-developers.com/android/development/guide-phoenixos-v1-0-9-rooted-iso-gapps-t3420779
or use my portable guide:
View attachment 3907531
Just unzip, open the folder and run the <HTML> with your web browser.
Let me know how it goes:laugh:
Do you see why I may have been a little confused?
Click to expand...
Click to collapse
Hi bg260, thank you for the .iso, unfortunately it ends up in grub> prompt on boot - just like the official version do.
Do you have some suggestions on how to boot this?
Could it be because I used unetbootin to make the usb?
Also I like to have persitence on this, could I just take a clean casper-rw of 3.9GB and rename it to data.img?
With kind regards
JBJ
Ps: I'm in Linux(Xubuntu 14.04 LTS) and don't have windows on my laptop(never going back to windows).
insomniacno1 said:
Hi bg260, thank you for the .iso, unfortunately it ends up in grub> prompt on boot - just like the official version do.
Do you have some suggestions on how to boot this?
Could it be because I used unetbootin to make the usb?
Also I like to have persitence on this, could I just take a clean casper-rw of 3.9GB and rename it to data.img?
With kind regards
JBJ
Ps: I'm in Linux(Xubuntu 14.04 LTS) and don't have windows on my laptop(never going back to windows).
Click to expand...
Click to collapse
So that I'm clear, is your intention to install to HDD? Or are you wanting a permanent install to USB. If the latter, I have no idea, to install to HDD there are several ways to do it. Mostly by unpacking iso straight to partition and the invoking the insmod command.
That's just Phoenix putting grub.cfg in wrong place. It needs to be in EFI:/boot/grub/grub.cfg
I'll try to get a better response within 1-2days.
Hi, I like to test it from the liveusb first(thats why persistence file) then later install on the internal storage of my tablet(removing windows and recovery partition, but leaving 100mb bootloader partition). So far I got linuxium 16.04 and 16.10 to boot(with nomodeset Kernel mode setting) and run where touchscreen, wi-fi and bluetooth work, but rotation, sound don't work. Puppy Linux Slacko boots(with i915.modeset=0) but wi-fi, sound and bluetooth is not working.
I like to keep my options open and get the best OS with the least footprint, but with working HW - it's a 16GB tablet where windows takes up 90% of the space and leaves 3GB free. Not even enough to install ubuntu or android. Thats why I'm looking into alternative ways of testing it.
My main OS is Peach OSI(xubuntu 14.04 LTS) and I don't have windows. So please take in mind this with any answers I got mkusb, unetbootin, live USB installer and dd utility for copying .iso to usb(but dd is not good as it limits the free space on the usb to the size of the .iso). For the life of me, I don't understand why people still makes .iso that needs Fat32, when we have so many other bootable filesystems that can handle -> 4GB .
insomniacno1 said:
Hi, I like to test it from the liveusb first.
Click to expand...
Click to collapse
I here rumors of people running Phoenix OS from an Sdcard.
Hi, I made the usb stick with uNetbootin and created new folders named /boot/grub/ - Copied grub.cfg to the /boot/grub folder and got it to boot to menu where I could choose to try phoenix or install. After choosing Try Phoenix it boots but after finding phoenix on /dev/sda1 the screen goes black. I tried:
nomodeset vga=788
nomodeset
i915.modeset=0
with all these it goes a bit further, but after "detecting phoenix" and "Android" written on the screen there are just a blinking cursor and no more. It's stuck.
It must be something missing or wrong with the boot parameters.
Can you help me get this boot all the way?
/boot/grub/grub.cfg
set timeout=6
menuentry 'Run Phoenix OS without Installation' --class android-x86 {
search --set=root --file /kernel
linux /kernel root=/dev/ram0 androidboot.hardware=android_x86 SRC=/ nomodeset vga=788
initrd /initrd.img
}
menuentry 'Install Phoenix OS to Harddisk' --class android-x86 {
search --set=root --file /kernel
linux /kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 INSTALL=1 DEBUG=
initrd /initrd.img
}
Click to expand...
Click to collapse
/efi/boot/grub.cfg
set timeout=6
menuentry 'Run Phoenix OS without Installation' --class android-x86 {
search --set=root --file /kernel
linux /kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/ vga=788
initrd /initrd.img
}
menuentry 'Install Phoenix OS to Harddisk' --class android-x86 {
search --set=root --file /kernel
linux /kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 INSTALL=1 DEBUG=
initrd /initrd.img
}
Click to expand...
Click to collapse
/isolinux/isolinux.cfg
default vesamenu.c32
timeout 50
label livem
menu label Live CD - ^Run Phoenix OS without installation
kernel /kernel
append initrd=/initrd.img root=/dev/ram0 androidboot.hardware=android_x86 quiet SRC= DATA= vga=788
label install
menu label Installation - ^Install Phoenix OS to harddisk
kernel /kernel
append initrd=/initrd.img quiet root=/dev/ram0 androidboot.hardware=android_x86 INSTALL=1 DEBUG=
Click to expand...
Click to collapse
/isolinux/syslinux.cfg
default vesamenu.c32
timeout 50
label livem
menu label Live CD - ^Run Phoenix OS without installation
kernel /kernel
append initrd=/initrd.img root=/dev/ram0 androidboot.hardware=android_x86 quiet SRC= DATA= vga=788
label install
menu label Installation - ^Install Phoenix OS to harddisk
kernel /kernel
append initrd=/initrd.img quiet CMDLINE INSTALL=1 DEBUG=
Click to expand...
Click to collapse
/syslinux.cfg made by uNetbootin but not being used on UEFI machines, only grub.cfg is being used.
default menu.c32
prompt 0
menu title UNetbootin
timeout 100
label unetbootindefault
menu label Default
kernel /ubnkern
append initrd=/ubninit root=/dev/ram0 androidboot.hardware=android_x86 quiet SRC= DATA= vga=788
label ubnentry0
menu label Live CD - ^Run Phoenix OS without installation
kernel /kernel
append initrd=/initrd.img root=/dev/ram0 androidboot.hardware=android_x86 quiet SRC= DATA= vga=788
label ubnentry1
menu label Installation - ^Install Phoenix OS to harddisk
kernel /kernel
append initrd=/initrd.img quiet CMDLINE INSTALL=1 DEBUG=
label ubnentry2
menu label Untitled Entry Grub 0
kernel /kernel
append initrd=/initrd.img quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/ vga=788
label ubnentry3
menu label Untitled Entry Grub 1
kernel /kernel
append initrd=/initrd.img quiet root=/dev/ram0 androidboot.hardware=android_x86 INSTALL=1 DEBUG=
Click to expand...
Click to collapse
EDIT:
I since tried using nomodeset xforcevesa and dd utilty, mkusb and liveusb installer(like pendrive linux) same thing happens, Android x86 flashes and black screen with blinking cursor and stuck there.
Must be something wrong with the image.
It boots on my Z3740 BayTrail-T tablet after putting grub.cfg in the right place.
Did you have the nomodeset and vga= in the file by default?
Have you tried without these? I boot fine. Also without i915.modeset=0 - this disables Intel gpu
And all you're interested in is the EFI:/boot/grub/grub.cfg
Nothing more.
Vioner said:
It boots on my Z3740 BayTrail-T tablet after putting grub.cfg in the right place.
Did you have the nomodeset and vga= in the file by default?
Have you tried without these? I boot fine. Also without i915.modeset=0 - this disables Intel gpu
And all you're interested in is the EFI:/boot/grub/grub.cfg
Nothing more.
Click to expand...
Click to collapse
Ok, lets start from an end
1. how do make your usb, which tool / which OS?
2. Could you post your grub.cfg?
3. could you post the iso you are using - just to make sure its not a problem with the image?
From the start "my" grub.cfg only had vga=788 - that booted to black screen with no cursor and hanged.
Only if I use kernel mode setting parameters will it continue to boot and I get all the way until it has to switch to loading the desktop and here it stops after printing Android x86 and then black screen with blinking cursor. This basically has happened on all android versions I tried - I never get to the desktop.
The Z3735E cpu is suppose to be able to run android as this were the intended OS when the cpu were made.
Intel cancelled their own android version for this cpu and it is no longer to be found, and it were based on 2.1 - so not really up to date.
With kind regards
JBJ
I just found out that allot of other people have had problems with apha version. Also, that at the blinking cursor if I press Enter it shows that I'm actually at the android prompt [email protected]:/ #
Just downloaded the latest .iso from the homepage and of course it still has no boot folder - I take from your post above that this is a common problem.
Also, after adding the boot/grub/grub.cfg and booting get the correct menu, choose Try Phoenix... - black screen without blinking cursor. This is on a different class 10 usb 3.0 stick.
Same thing with nomodeset vga=788
But with nomodeset vga=791 which is 1024x768 24bit I get to the prompt again.
"#¤%%&&T&//"@
How do you login to android from prompt?
Update: replacing quiet with acpi=off and adding nomodeset vga=795 (1280x1024) to the end of the kernel parameter line makes this go beyond detecting Phoenix OS and actually start loading it - Very slowly - a whole lot of ............................... on the screen. Once in a while the light go out and I have to press ctrl to see what is going on.
How about you guys make the loading a bit faster, I run this from USB 3.0 class 10. Ubuntu and Puppy linux, loads way faster than this one.
Regarding the black screen, if would seem that on these tablets the brightness is reversed, so instead of starting up with max brightnes you start up with no brighness at all, and isnce tablet don't have keyboard with fn key its extremely difficult to adjust brighness while booting. A helpful kernel parameter would be nice.
Problem is very old and is described here: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=712180
UPDATE:
One and a half hour later still loading.
Never mind I will return to Phoenix when the bugs are fixed - and I have more patience!
I'm right now running Androidx86 6.0 r1 32bit(can also run 64bit) on my tablet with nomodeset as only kernel parameter. It boot right away and the only thing so far that don't work is bluetooth.
So I will call Phoenix OS bad programming!
insomniacno1 said:
Just downloaded the latest .iso from the homepage and of course it still has no boot folder - I take from your post above that this is a common problem.
Click to expand...
Click to collapse
I know that the .iso I made has worked for quite a few. I'm just throwing this out but, you say it finds phoenix on /dev/sda1.
I have had problems when testing a new build. If i already have Phoenix installed on the hard drive the probe will detect and boot it, even with a live USB. /dev/sda1 should not be the USB unless you have no Hard disk installed. Should be /dev/sdb1 or sdc1. I'm wondering if you have phoenix grub installed in a hidden sector. Try
Code:
sudo dd
I'm assuming from your experience that you know the power of that command. It will write zeros over the partition. Hidden sectors and all.
Please don't post that sda is normally your internal hdd, if you run this command from a linux system then if might break your os.
When running Phoenix from USB on the tablet, the USB becomes sda1 because the tablet use GPT and not MBR.
As stated above, androidx86 booted into the desktop with the nomodeset, unfortunately that also put the tablet in low graphic mode.
I have installed phonix os via exe file then click reboot.
On 1st boot it was showing be only black screen and nothing coming up. So I forcefully restrat it. Then it showing be me this screen.
How can I solve it?
rabin69x said:
I have installed phonix os via exe file then click reboot.
On 1st boot it was showing be only black screen and nothing coming up. So I forcefully restrat it. Then it showing be me this screen.
How can I solve it?
Click to expand...
Click to collapse
Cursor might be active ,type
Code:
logcat
And check output
I have the same problem, after that screen the backlight of the lcd blinks 2 times and then my laptop restarts. I tried different settings in grub.cfg and it shows some signs of life only if I put the parameter nomodeset, I see phoenix os logo and then the hdd turns off, if i put video=-16 video=LVDS-1:d I listen the hdd working but the screen is completely off. I think that my gpu is not supported. I don't know compile the drivers. I have too much troubles with amd hd8180. Any solution?
update: I tried the x32 version and there are many problems on boot:
service media.audio_flinger died
accept_ra_rt_table no such file or directory
libgapi has text relocation
the icing on the cake is signal 11 segmentation fault refferred to surfaceflinger
Hi, I was have a same problem when i install phoenix 2.5.3 to my alcatel plus 12 2 in 1 notebook ( n3350/4gb ram/32 internal storage + 32Gb ext / 11.6 " FHD / win 10 home ) after finish install the i boot, i will be black screen with cursor in the left corner event i restart again still same, nothing else happening, i allready try to install in internal, external & flash disk the result still the same. Can any one help me ? before this i install in my lenovo notebook G40-30 AMD A8 work fine.
linuxandroid said:
I have the same problem, after that screen the backlight of the lcd blinks 2 times and then my laptop restarts. I tried different settings in grub.cfg and it shows some signs of life only if I put the parameter nomodeset, I see phoenix os logo and then the hdd turns off, if i put video=-16 video=LVDS-1:d I listen the hdd working but the screen is completely off. I think that my gpu is not supported. I don't know compile the drivers. I have too much troubles with amd hd8180. Any solution?
update: I tried the x32 version and there are many problems on boot:
service media.audio_flinger died
accept_ra_rt_table no such file or directory
libgapi has text relocation
the icing on the cake is signal 11 segmentation fault refferred to surfaceflinger
Click to expand...
Click to collapse
Stuck also on boot: cannot detect the phoenix
Hello, I am trying to install phoenix as a dual boot on an HP X2. I have downloaded the latest version from the website (64bit version) and it installs normally on the hard drive. At reboot, I went to the BIOS and disabled the secure boot (it is UEFI boot by the way). I then restarted and I get the dual boot option. I select phoenix and I get the "Detecting Phoenix OS prompt, only that I got dots that populate the entire screen (I even let it run overnight with no luck).
I then tried to install phoenix onto a SDHC 16GB thumb drive. Install went fine but at boot, the BIOS does not have the option to boot on SD card, only on USB. So, I placed the SDHC card onto a USB adapter and it boots onto the SDHC via USB but I have the same issue: I got dots that populate the entire screen.
Any idea of what I could do to be able to install it? I want it on my drive.
Thanks.
PC is: HP 10-p018wm (walmart edition of HP pavilion X2).
x5-Z8350, 4GB RAM, 64GB eMMC
Hi I am also stucked at A N D R O I D x86_64:/ #
anyone can help?
Did anyone find a solution for this yet please help i tried everything :crying:
Edit : i'm using the latest version of phoenix os
I am also experiencing boot issues with Phoenix OS. I've also tried RemixOS and Bliss. All show the same issue. I'm using a Lenovo Yoga 920.
Trying to think outside of Android, specifically, I started looking at compatibility with Linux in general and the Yoga device. It looks like (and I could be wrong here...pretty new to Android_x86) the kernel needs to be up to v. 4.15. (https://forums.lenovo.com/t5/forums...Special_Interest_Linux/thread-id/10264/page/2)
If anyone has any ideas, I'm open to testing.
I got mine to boot by editing the grub file, adding nomodeset and editing vga to vga=ask then picking the 1024x768 32 bit option. Anything else and it won't pass the terminal.
Intel i5-4210u
Intel HD / Nvidia 840m
Legacy BIOS
staffwand said:
I got mine to boot by editing the grub file, adding nomodeset and editing vga to vga=ask then picking the 1024x768 32 bit option. Anything else and it won't pass the terminal.
Intel i5-4210u
Intel HD / Nvidia 840m
Legacy BIOS
Click to expand...
Click to collapse
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.
hotwired34 said:
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.
Click to expand...
Click to collapse
so ? did it work ?
Jinreu said:
so ? did it work ?
Click to expand...
Click to collapse
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.
hotwired34 said:
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.
Click to expand...
Click to collapse
it didn't work for me either, even when i change to legacy i tried typing 'logcat' the logs are going too fast i can't read anything
i see something like this in the logs
Code:
I ServiceManager: service 'media.audio_flinger' died
I ServiceManager: service 'media.player' died
I ServiceManager: service 'media.resource_manager' died
hotwired34 said:
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.
Click to expand...
Click to collapse
It'd be in the hidden ESP partition. I'd test with just adding nomodeset by editing the entry before it boots [e on grub menu]
hotwired34 said:
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.
Click to expand...
Click to collapse
Yeah, looks good. Did it boot for you?
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I actually used Remix OS' grub to set the boot options. Edited one of the boot options to:
find --set-root /PhoenixOS/kernel
kernel /PhoenixOS/kernel root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS quiet nomodeset vga=ask
initrd /PhoenixOS/initrd.img
boot
staffwand said:
Yeah, looks good. Did it boot for you?
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I actually used Remix OS' grub to set the boot options. Edited one of the boot options to:
find --set-root /PhoenixOS/kernel
kernel /PhoenixOS/kernel root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS quiet nomodeset vga=ask
initrd /PhoenixOS/initrd.img
boot
Click to expand...
Click to collapse
It didn't boot. However, looking at your grub entry...it looks completely different. Here's my whole grub entry for PhoenixOS:
menuentry "Phoenix OS" {
search --set=root --file /EFI/PhoenixOS/kernel
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
initrd /EFI/PhoenixOS/initrd.img
}
Would you mind posting your whole grub entry for PhoenixOS?
I too am getting almost a similar problem. I installed the latest version 2.6.0 via the exe installer. It shows the line:
Detecting android x86... Found at dev/sda5
And the pc automatically restarts?... Any way to get it fixeD?
man , how can i fix this problem ? stuck at A N D R O I D x86_64:#
anyone please share solution for this? i am also facing same problem
here is also trouble shooting information
~~~~~~~~~~~~~~~~~~~~~~~
https://store.askey.com/adt-3.html
~~~~~~~~~~~~~~~~~~~~~~~
android 13
for google tv and android tv
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android 13 for TV | Android Developers
developer.android.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
android 12
for google tv and android tv
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
https://developer.android.com/tv/release/12#install-manual
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
android x86
android (tv / tablet / pc) version. i
this runs on laptops and in virtual machines. its stock un bloated
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android-x86
Android-x86: Free software download for windows, linux.
www.fosshub.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------
and now linux options for android tv boxes
-----------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GitHub - 833M0L3/H96MaxX3: Install Linux on H96 Max X3 / Amlogic S905X3 TV Box. Cheap alternative to Raspberry Pi's for making a headless home server.
Install Linux on H96 Max X3 / Amlogic S905X3 TV Box. Cheap alternative to Raspberry Pi's for making a headless home server. - GitHub - 833M0L3/H96MaxX3: Install Linux on H96 Max X3 / Amlogic S9...
github.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linux images for android tv boxes (currently avalaible: archlinux, kali linux) - FreakTab
This topic if for people who want to run linux on thier android tv boxes (by linux i mean kali linux and arch linux) kali linux and arch linux images can be found here: https://disk.yandex.com/d/q3R5VgmiDDLq6w Steps to run linux. 1. Flash the image you downloaded from the link above to an...
forum.freaktab.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Armbian for Amlogic S805 and S802/S812
forum.armbian.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
this is my fav
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kali ARM Statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hack the world
and for reading this as an added bonus... free premium youtube version for android devices ... no ads , download video and/or audio, plays with screen off, no ads any where, picture in picture, back ground play, and no ads
Alright I'm no expert on Android tv boxes but is it possible to flash this without unlocking the bootloader?
Like I've got a tivo 4k box that is android 9 and tivo isn't releasing updates anymore as far as I can tell. So could I flash android tv 12 or 13 on it without OEM unlock and without bootloader unlock?
With out unlocking the bootloader. Linux is going to be the best option. You can run many different linux distributions on these tv boxes. Look into kali linux for arm or ubuntu for arm. Possibly debian.
with kali live boot and a usb or flash drive. It restores a pc with black screen of death and allows access to revoer files or take over the device.
Things to note... chmod -v 7777 written before anything changes its permissions same with chmod +rwxXst or last resort chmod +rwx. Adding -v shows if it worked or not -c or -v does that.
Fsck before the path of a directory such as /dev/sda will try to repair the file system on the device listed (dev is short for device and sda is usb plug device #1)
If you put the file system with the files needed on a sd or flash drive or partition. You can mkfs.ext2 -d // /dev/ and what ever device name added to copy root directorys while making a replacement file system
dd if= insert a disk image name or a directory then type of= and insert location to flash the image to.
dd if=/dev/zero of=/dev/ and device path .. will zero a device for re write
Now if you want to edit parts of the file system then create a mount point on the same path but make a new file with mkdir -v -p /type out where you want to go. Then you can mount with files to implant or replace at the location with mount -L and the devices label/name then the paths location or /dev/sd last letter for your device and then location.
Oh and you can also mount with mount -loop and you will basically have your mount over the original one.
If you need to edit logs. type nano and the name of the file. To save what you write hold ctrl and press x then y then let go ctrl and hit enter
spart0n said:
Alright I'm no expert on Android tv boxes but is it possible to flash this without unlocking the bootloader?
Like I've got a tivo 4k box that is android 9 and tivo isn't releasing updates anymore as far as I can tell. So could I flash android tv 12 or 13 on it without OEM unlock and without bootloader unlock?
Click to expand...
Click to collapse
Android devices boot and pass permission as they pass through security. Problem is partiton 1 and partiton 3 are both partition 1 with partition 2 overlaying it. ...
This is what the gods of android use this is a tool box with magisk and pals programs https://apt.izzysoft.de/fdroid/repo/com.sanmer.mrepo_111.apk
Also with a rooted device and an adroid program called termux. You can actually manipulate other androids in lots of ways. Expecially with kali nethunter on a rooted device.. or emulated rooted device like Ld player
Termux has changed the game when it comes to altering androids.
Termux
The main termux site and help pages.
termux.dev
This on a rooted phone is a trojan horse for androids
Kali NetHunter | Kali Linux Documentation
Kali on your Android phone
www.kali.org
This is where the linux on tv boxes information is
Single Armbian image for RK + AML + AW (aarch64 ARMv8)
The start system in Coreelec is not compatible with LibreELECE Armbian etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, whic...
forum.armbian.com
Personally.. using a linux os on a sd card to wipe android tv box is easier than finding one in a billion rom you need.
They say the rock chip is impossible to brick. It has rockmode or what ever.. i ****ing bricked one last year