Develop Bugs

[5/4/2013] Running real linux on your Kindle

---
DISCLAIMER: THIS IS A REALLY GOOD WAY TO EFF UP YOUR KINDLE IF YOU DON'T KNOW WHAT YOU ARE DOING!!!
IF YOU DON'T KNOW WHAT ADB, PARTED, OR WHAT LINUX IS, YOU MIGHT WANT TO JUST CLICK THE BACK BUTTON!
---
Most that know Android, knows that it's just fancy UI and API on top of Linux, but it's still not quite Linux... But what if you want to run real Linux on your tablet?
Well, it's actually not that hard to do, but certainly not for n00bs...
Need to know: Linux, fastboot, adb, parted, etc.
You will also need the mkbootimg program, fastboot, working ADB, etc.
And a USB OTG adapter and working USB keyboard.
(this is assuming you already have modded your kindle with the usual FFF+TWRP 2.1+CM9)
The first step is to do a little repartitioning, so boot the Kindle into recovery, and run an 'adb shell'.
Then run 'parted'.
The idea here is to basically maintain the stock layout, while making room for linux...
Which can be done a few ways, the easy way would to just delete 'media', then recreate it much smaller (I did 1GB).
Then make one more new partition, using the remaining flash memory (should be a little over 4GB).
Making sure to reassign the name 'media' to partition 12, you can also name the new linux partition 'linux' or whatever, if you like.
After that, quit parted, and create the new FS on the new linux partition (mke2fs -Text4 /dev/block/mmcblk0p13, but you should know that already ).
Then reboot the tablet, get back into Android, it may or may not complain about the 'SDCARD' needing to be formatted, which should be done anyway, since it changed in size.
Do another 'adb shell', mount the new linux partition to a useful place, you can just mount over '/mnt' if you like, it won't hurt anything. Exit out of the shell.
Download this pre-built Debian rootfs I found:
http://rcn-ee.net/deb/rootfs/wheezy/
Unpack that file on your host machine, then use 'adb push' to copy the armel-rootfs tar to the Kindle's '/mnt'.
'adb shell' back into the kindle, and change to '/mnt' and untar the armel rootfs tar file... Maybe go to the bathroom, get a drink, get some fresh air or something, it'll take a little time to do it's thing.
After that's done, download my rc.local and 'adb push' that to '/mnt/etc' and make sure to ungzip it, and chmod is 0777 (or is it 0766, either should work lol).
http://www.mediafire.com/?gx46xxb4813n5ob
Then you can delete the rootfs tar file if you like, get out of '/mnt', and unmount it.
Linux is now installed, easy eh?
Now, download my kernel (acutally it's Hashcode's kernel, but with needed changes):
http://www.mediafire.com/?2lqex9j5bgws0b1 (Updated 6/11/2012)
Using mkbootimg:
'mkbootimg --kernel zImage --ramdisk /dev/zero --cmdline "root=179:XX" --base 0x80000000 -o boot.img'
Where XX is the partition that you put linux on (if following this exactly, should be 13), you should now be able to use /dev/mmcblk0pXX as well, if that doesn't work just use 179:XX.
Then using fastboot, boot the kernel package:
'fastboot boot boot.img'
While it says 'waiting for device...", reboot the Kindle and wait for it to download and boot the package.
Then wait for the linux login!
Plug in your favorite USB keyboard, a USB 1.1 one works best I've found.
The root password for that rootfs package is just 'root'.
-------------
Now, the fun part: Internet access, the hard way.
I'm still working out getting the WIFI modules working, so you'll have to use it tethered via USB... Which means no keyboard, but you can still log in by SSH.
In my kernel, instead of being an 'android' USB devices, it's a multifunction USB gadget with ethernet, serial port, and mass storage.
Mass storage works, but a little buggy sometimes.
Serial port seems broken for some reason.
Ethernet is what we're after.
Now the rc.local I made, in addition to enabling the video overlay (so there's a framebuffer console on the LCD), it also sets up the ethernet USB gadget.
I set the IP address to 192.168.5.1, which really should be out of the common IP range that most people use, but if it conflicts, then you can edit rc.local before you push it over above.
On your Linux host, with the Kindle plugged in, bring up the USB ethernet interface:
'ifconfig usb0 192.168.5.2 netmask 255.255.255.0'
After that, maybe try pinging the kindle (192.168.5.1), to make sure everything is working... If it is, you should have no problems connecting with SSH and logging in.
Once you can connect/login by SSH, you'll need to add your host machine as the default gateway ('route add default gw 192.168.5.2'), then edit '/etc/resolve.conf' and add a DNS server (add your ISP's DNS, or use 4.2.2.1).
After that, you should have internet access on the kindle side via SSH, and should be able to download/install your favorite Debian packages.
Oh, did I mention that you'll need a IP forwarding/NAT service running on your linux host too? I'll have to refer to linux manuals on how to do that, but if you can do all this, you should have no problems doing that.
I should also say that this CAN technically be done in windows as well, since all the needed programs are available in WIN32 bins, but you won't be able to get tethered network access working, because Microsoft doesn't support CDC ethernet devices.
Have fun!
OH! And X works fairly well with the omap3 video driver, just so long as you DON'T touch the screen, the touch screen driver currently crashes X on input.
So fair warning, make sure you know how to navigate X with just a keyboard, unless you have a OTG working hub and can use a keyboard and mouse, or have a wireless keyboard/mouse combo of some kind.
Update 6/11/2012:
Uploaded new kernel (link above), touch screen is now working, though no multitouch.
I have a boot loader with multiple boot options, http://www.mediafire.com/?l6aaqgsdkiksfw0
To use it, make a partition named "linuxboot", and flash your linux's boot.img created with the above instructions.
Still working on wifi.
Update 6/11/2012:
Ok, WIFI is working... Not sure why it wasn't before.
Here are the modules: http://www.mediafire.com/?139hold2a2l9vbl
Don't forget to run depmod.
You'll also have to copy the firmware from android system partition in /etc/firmware and copy it to Linux /lib/firmware

In case no one believes me, here's a console dump (typing blind of course, this was an early attempt with no LCD):
Code:
d.
.
Starting periodic command scheduler: crond.
FATAL: Could not load /lib/modules/3.0.21+/modules.dep: No such file or directory
Debian GNU/Linux 5.0 carrier tty1
carrier login: usb 1-1: new low speed USB device number 2 using musb-hdrc
usb 1-1: device v0b38 p0010 is not supported
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.0/input/input4
generic-usb 0003:0B38:0010.0001: input: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-musb-hdrc-1/input0
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.1/input/input5
generic-usb 0003:0B38:0010.0002: input: USB HID v1.10 Device [HID 0b38:0010] on usb-musb-hdrc-1/input1
root
Password:
Last login: Sun May 27 21:55:28 UTC 2012 on tty1
Linux carrier 3.0.21+ #40 SMP PREEMPT Sun May 27 16:59:27 CDT 2012 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
carrier:~# echo skdjfhnsdkjfshdsummit_bat_notifier_call val=41
summit_smb347 4-0006: summit_fsm_stateTransform:state : suspend(0) -> suspend(0) ; event : EVENT_BATTERY_NTC_NORMAL
kfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb0
carrier:~# echo skdjfhnsdkjfshdkfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb1
-bash: echo: write error: No such device
carrier:~# omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
cat /dev/vcs1 > /dumpp.txt
I was trying to get something to come up on the framebuffer, to no avail of course.
The backlight comes on, and it seems like it want to work, but there's nothing.

Are you talking about a true Debian dual-boot on our tablet? That could be really awesome .
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk

Actually, yes.
It's mostly a matter of having a proper framebuffer console and telling the kernel to use a root instead of using the initrd to setup android.
If we could get a scripted bootloader, one that would give a customizable boot menu, you could easily boot whatever you wanted.

And what about it : http://thomaspolasek.blogspot.fr/2012/04/arch-linux-lxde-w-xorg-mouse-keyboard_16.html?m=1 ?
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk

Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.

seishuku said:
Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.
Click to expand...
Click to collapse
Display might be tricky, as we are currently using the very latest graphics modules from TI. I'm not sure if you can use those in our current build.
That being said you could send a cat /proc/msg to a file during boot and that might contain your error.
Sent from my Amazon Kindle Fire using Tapatalk 2

Well I already have a working fbcon in android, but it seems the display just isn't being enabled in Linux.
I've tried "echo 1 > /sys/devices/omapdss/display0/enabled" to force it on, but nothing.
The back light is already on though...

I thought EXT2 was for really old linux distros.
Sent from my Kindle Fire using XDA

Not really, its just more compatible.
I could have made pretty much anything...

I read somewhere that SSDs should use EXT4.

i am really anxios to see this even though is only cmd line.
will the steps to get this going available even for SSH commands?

I really should hack together a wifi script to get some kind of network connection, would make working on it a little (lot) easier.
The idea here though is to basically have a full linux, to operate exactly like it would on a PC.
With a working framebuffer console, an X.org config can be made and X should work just fine with the touch screen too.
The end result, with just keyboard, should be a full blown linux system.

The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2

Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk

Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
pbailey212 said:
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.

I'm at a bit of a loss here... if I disable surfaceflinger, so I keep my android fb console, then if I disable the display and reenable it, I lose the console.
Also, in my initrd, I can remove everything except ueventd and still keep the console... so something ueventd (init) is doing to enable the console.
In Linux I can play with enabling/disabling the display, but nothing seems to provoke Linux to give me an actual console.

Sblood86 said:
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.
Click to expand...
Click to collapse
On the vm670 legend has it, people have compliled whole roms in 30 minutes, with an optimus v, and Leslie Ann's build server
sent from my Nokia 5110

Aha! Got it!
http://www.youtube.com/watch?v=PXhnVP3lWLU
For whatever reason sysfs wasn't taking my commands.
Now I can work out some bugs and get X working.
I also switched the USB gadget from android to an Ethernet CDC, so I can SSH via USB while I get wifi working.
Edit-
Sorry about the super blurry video, my phone's camera is having "issues".

Ok, I've switched to the official Debian armel wheezy distro (basically just formatting my linux partition and untaring the distro), seems to have fixed a lot of problems... One being aptitude not working correctly (seen in the video).
I need to enable some kind of ip forwarding on my local linux install, so I can get a temp internet connection on the kindle via USB gadget ethernet cdc (ssh and http already works).

Nextbook Flexx 11 how to dual boot android and 8.1/10

ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost

ever get anywhere with this?

I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app

I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.

I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.

I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.

64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.

GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.

rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.

Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great

OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution

Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.

I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks

murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.

UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.

korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.

This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015

Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori

KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...

Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...

[RECOVERY] TWRP 2.8.6.0 for Shield TV (all variants)

I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img

MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments

Thanks Steel01!

I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).

Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...

I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!

Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.

Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks

Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy

Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.

cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.

I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance

Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse

I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.

Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.

Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.

I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.

Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers

This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse

Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility

[ROM][BETA] PrimeOS 2.1.0 for Rpi4 and Pi4B

TeamPrimeOS is pleased to present you PrimeOS 2.x.x for Raspberry Pi4 and Pi4B
PrimeOS is an android based OS that provides a desktop experience with user top-of-the-line features like multi-window, taskbar, swipe simulation, and deca-pro key mapper for gaming.
Warning: PrimeOS 2.x.x is a free-to-use software in its beta version and is constantly under development. We are not responsible for any kind of damage, data loss, or anything else that happens to you or your device due to PrimeOS. Please feel free to report bugs and other suggestions. This is not for commercial use, please contact us if you wish to do that.
Feature Summary -
Desktop Experience:
Multi-window support with maximize, minimize, close, resize, etc
Taskbar with the ability to pin apps, show notifications, and system icons
Mouse scroll will actually send touch swipes for android apps support
Right click support for homescreen, app icons on taskbar etc.
General keyboard shortcuts like alt + tab, alt + f4, win + d etc
Android Gaming:
Decapro key mapping tool to play games with keyboard and mouse
Press F10 when running a game to manually adjust the controls
Pre-mapped some popular games like PUBG, Freefire, Subway surf, etc
Gaming Centre is available to browse recommended games
Others:
Based on LineageOS 18.1 (android 11)
Our own desktop browser based on kiwi
Gapps included, no need to install them manually
Settings to change resolution, frequency, cpu governer are present
Known Bugs:
Hardware video encoding/decoding
Same as other android roms
Screenshots -
https://imgur.com/a/7ctTity
Installation -
Write the image to sdcard using balena etcher.
Download PrimeOS -
https://www.primeos.in/download/
!! Please do not mirror without permission !!
Consider donating to us to keep this awesome project up and running.
Credits -
PrimeOS on RPi4 would not have been possible without the awesome contributions of LineageOS, OMNI ROM, Konstakang.
Community -
Get Support on Telegram

Reserved

what about Raspberry Pi 3B+

coming here from ETA Prime youtube video! nicee

What about "Hey Google" wakeword? HOw activate it?

MechWarriorZero said:
what about Raspberry Pi 3B+
Click to expand...
Click to collapse
It's arm64 based so Raspberry PI 3B+ is supported. You can tweak the boot.conf a little to match your needs after flashing it to a usb or an sd card.
I've been using this on Raspberry Pi 4b for the last 2 weeks since they first posted there release on the Rasbian Forums. And I will say it's pretty good. I've been running it off of a 64gb Sandisk Cruizer USB. Besides a few glitches in the graphics while using my 4k Roku TV and the original mini-hdmi to hdmi adapter. I would say this is going to go far. I have lots of hopes for this OS!
For everyone who is trying to boot these builds from USB you can follow this:
Q: How to boot from USB device?
A: Warning, this is still an experimental feature. Especially TWRP seems to have some issues with USB boot.
Install EEPROM that supports booting from USB
Write image to your USB device as above
Mount the USB device on your computer and make following changes to /boot/config.txt under ‘Boot device’ section:
#dtoverlay=android-sdcard
dtoverlay=android-usb
Plug in the USB device to your Raspberry Pi, remove any sdcard, and boot
Click to expand...
Click to collapse
Quote by @KonstaT . A very good developer that has made Android on the Raspberry pi much more easier. Don't forget about @maxwen though(for all of you OmniROM fans ))

NonStickAtom785 said:
It's arm64 based so Raspberry PI 3B+ is supported. You can tweak the boot.conf a little to match your needs after flashing it to a usb or an sd card.
I've been using this on Raspberry Pi 4b for the last 2 weeks since they first posted there release on the Rasbian Forums. And I will say it's pretty good. I've been running it off of a 64gb Sandisk Cruizer USB. Besides a few glitches in the graphics while using my 4k Roku TV and the original mini-hdmi to hdmi adapter. I would say this is going to go far. I have lots of hopes for this OS!
For everyone who is trying to boot these builds from USB you can follow this:
Quote by @KonstaT . A very good developer that has made Android on the Raspberry pi much more easier. Don't forget about @maxwen though(for all of you OmniROM fans ))
Click to expand...
Click to collapse
USB boot not working correctly. Every time need to change /boot/config.txt file to boot from USB!

Newbie here. I have just installed this on a 64gb sd card and using it on raspberry pi 4. BTW, big thanks to everyone involved in this. It looks and feels amazing to be able to do this on a raspberry pi. I have two questions if anyone can answer these.
1. I can't seem to be able to expand the userdata partition. I have expanded the main boot parition but that doesnt seem to be of any help. I still have only 5gb disk space when I check on the Prime OS.
2. How do I shut it down. I assume there is a way to shut it down before actually unplugging the rasppberry pi.
Thanks.

mshs013 said:
USB boot not working correctly. Every time need to change /boot/config.txt file to boot from USB!
Click to expand...
Click to collapse
Same trouble for me

andrei_retro said:
Newbie here. I have just installed this on a 64gb sd card and using it on raspberry pi 4. BTW, big thanks to everyone involved in this. It looks and feels amazing to be able to do this on a raspberry pi. I have two questions if anyone can answer these.
1. I can't seem to be able to expand the userdata partition. I have expanded the main boot parition but that doesnt seem to be of any help. I still have only 5gb disk space when I check on the Prime OS.
Click to expand...
Click to collapse
Okay so the Userdata can be expanded using another device. Or from the recovery image itself. I'm not sure if PrimeOS has a recovery mode by default. You can use this zip to flash to the devices recovery if it has one.
lineage-18.1-rpi-resize.zip
2. How do I shut it down. I assume there is a way to shut it down before actually unplugging the rasppberry pi.
Thanks.
Click to expand...
Click to collapse
You can shut it down by pressing F5 on your keyboard and holding it. But you can not boot it back up that way. You can check out one of his guides for setting up manual hardware keys here: https://konstakang.com/devices/rpi4/LineageOS19/
@vontoff @mshs013 could either of you help me out a little and send me the `/boot/config.txt` I'm on some pretty bad wifi and I don't want to redownload the entire PrimeOS file just to see it. You may both also have to get the latest Raspberry Pi bootloader and flash it. Here's a simple guide on how to do that:
https://pimylifeup.com/raspberry-pi-bootloader/
Otherwise if your SD Card is still in the Raspberry Pi then you might have issues.
Last case scenario is that you're both telling me you're stuck in a bootloop because the `boot.config` isn't applying the changes to tell PrimeOS and the bootloader you're booting from USB.
I hope some of this works out for you any of you three. If you need more help feel free to ask.

Hello, sorry for late answer... Each time need to modify boot settings for usb..... Join my config.txt after boot Ok.
Really weird because USB boot seems to be OK
tHANKS
# normal boot
kernel=Image
initramfs ramdisk.img followkernel
device_tree=bcm2711-rpi-4-b.dtb
arm_64bit=1
# audio
dtparam=audio=on
[HDMI:0]
[HDMI:1]
hdmi_force_edid_audio=1
[all]
# disable kms audio path and force bcm2835 card 0 = hdmi card 1 = headphone jack
dtoverlay=vc4-kms-v3d-pi4,noaudio
disable_fw_kms_setup=1
# usb adb
dtoverlay=dwc2,dr_mode=peripheral
# booting from sdcard
#dtoverlay=rpi-android-sdcard
# booting from usb
dtoverlay=rpi-android-usb
# serial console
enable_uart=1
# SPI
dtparam=spi=on
# I2C
dtparam=i2c_arm=on
# I2S
#dtparam=i2s=on
# max oc - can be adjusted in rom during runtime
over_voltage=2
arm_freq=1750
# gpio fan - start 55 deg stop 45 deg
#dtoverlay=gpio-fan,gpiopin=12,temp=55000
# pi camera
#gpu_mem=256
#start_x=1

Is there a way to mount NTFS drives? I would like to use PrimeOS as a local video player.

Hi there!
How can I add hardware buttons for power down, volume up and volume down?
Thank you!

how do i exit TWRP ? i changed boot mode to recovery for installing a recovery-zip. But how do i boot to system again ? It always boots recovery now.

i need to install "volkspc" - need root for that. magisk.25.2.zip ends with error.
How can i get root ?

Hi,
I'm stuck at 'System UI isn't responding' on Pi4B 1GB. btw is that too low for this rom?
I want to see if it'll run kodi
thanks!

Vik0_ said:
Hi,
I'm stuck at 'System UI isn't responding' on Pi4B 1GB. btw is that too low for this rom?
I want to see if it'll run kodi
thanks!
Click to expand...
Click to collapse
I guess that's too low spec for it, flashed it a couple more times, just to make sure the SD card/USB was not the issue, but never loaded the OS. System not responding messages and reboot in a loop.
Judging by the other ROMs posted for Pi, probably a 2GB RAM minimum also applies to this one.

RPI400: fn+f10 does not work.
Normally a rpi400 can be powered on by fn+f10.
But when i shutting down primeos this does not work. I have to unplug and plug again to make it start.
How can i fix this ?

@TeamPrimeOS hoping you will contribute back to opensource as part of your ethics & commercial model. ATB for Primebook.

ZenFone 2 Z00A(d) ZE551ML - can't boot - black/white screen, no bootloader, want Windows (KVM kernel/OS)

I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.

indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader

I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(