Database Users

Cant Build for find 5

Hello, I am new to the community and although I have flashed loads of roms to various devices this is the first I have tried to build from source.
As it says in the title I am trying to build for my Oppo find 5 which there is a nightly build for, I wanted to try and build from source though.
I have set up the build environment as described on the omni website.
I have followed a set of instructions but when I come to build using
Code:
brunch find5
i dont get a zip in the out folder. I do get the following notes though in the terminal after the build.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Click to expand...
Click to collapse

Those errors are meaningless. Post the full log as an attachment please.
Although I'd suggest reading through the errors first - the first skill anyone needs in Android development is the ability to look through a log and analyze what is what.
At the very least you might've forgotten envsetup. You probably forgot to pull blobs with extract-files (or finding them through some other source...) too - nearly everyone does.

Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:

jejecule said:
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
Click to expand...
Click to collapse
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote

maxwen said:
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
Click to expand...
Click to collapse
yes i'm sure. i was first using the one from themuppets github, then Guillaume advised me to use the coyote ones. Size of the find5 vendor folder is 40,1MB, 132 files. Strangely i had this issues with my last 5 builds, but with the today one, problem disappeared and now my baseband is recognised and everything ok, though i still have this no radio.img message at the end of the build.
Really strange indeed i hate not to know what was the issue Anyway i will build again tomorrow and let you know, Chasmodo from Asylum team is also helping me a lot in understanding some stuffs as i'm a new and noob in building
One question about blobs: when i try to extract it from my device, it works when i run an 4.3 aokp build but then i get error in building. If i try to extract blobs from omni 4.4 (official nightly) i get some access denied on some blobs and then also some errors in the build. No issue with coyote ones though.
Many thanks for your time mate!

So guys, my problem with find5 modem seems to be fixed, no issue with today build neither. But.....now facing exactly the same issue with jftlexx(i9505)...
Build went OK, blobs from coyote, flash and boot OK....but no modem again, I may be do wrong stuff when flashing or missing something.
Before flashing I always do factory reset + wipe system, then flash build, gapps(pa ones mostly) + supersu.
Same repo, same vendor, I9300 OK but manually added local manifest as in your tuto.
Rebuilding atm
Thanks a lot
Sent from my Find 5 using xda app-developers app

TWRP 3.2.3-0 and older versions for Redmi Note 2

TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk

Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/

If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble

Thank you for sharing!

jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...

@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1

jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !

Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.

@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)

New version 3.0.0-3

jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?

@sanceliken2000 No it is original.

jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?

@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)

Interface look good, old backups need to be re-backup! Thx~

addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.

@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.

There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?

This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk

I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.

Modified Kernels for the SM-S820L!! --__-- Download Here--__--

The Beginning of Advances in SM-S820L Custom Options​
Since coming across Assayyed's Kitchen, I have been uber excited to become saturated with all things custom ROM.
I am by no means a Droid Guru, but I have plenty of awe and drive that synergizes with the freshly ground and brewed coffee beans I use most every morning.
I fully intend to continue learning how to customize the Stock ROM files I have saved from various sites over time.
--------> My goal is to share my work with this and every other Android community so that folks with this model of the Core Prime get the much needed support they deserve for this phone.

This link is for my 'finished product'. This is one of the threads I have at NEEDROM and actually the first one I have made with files I put some work into.
My account at Needrom is the same name as here so you will know you can get ahold of me at either forum and as always via my personal email: [email protected]
http://www.needrom.com/download/samsung-galaxy-core-prime-boot-img-kernel-tweaks-added-for-sm-s820l/
The one draw back is having to create an account with them but it's free and good to have as a source for all sorts of stuff.

Download Here---___
Features of these Modded Kernels For SM-S820L​
ADB Enabled
ADB Direct Root Enabled<----- Only for file labeled as such<----
init.d Support
DM-VERITY Disabled
FORCE-ENCRYPT Disabled
SE Policy Patched
Thanks goes to Assayyed for his Kitchen. Without that program I would not have been able to create these.
The boot.img whose Kernel has ADB Direct Root Enabled comes with a WARNING: This is an experimental feature and may cause BOOT LOOP!!!
I will say, though, that I have personally tested both of these modded kernels and both work just fine on my SM-S820L. :good:
In each ZIP file there is a boot.img with the modded kernel and a TAR_MD5_PACKAGER tool so you have your pick of methods to flash the .img.
I used ODIN because I wasnt sure of flashing with my unofficial TWRP release.
Everything went smoothly and my phone is running perfectly with no errors known as of yet. I dont anticipate any.:laugh:

Info about loop support 7.0+ EMUI [magisk, supersu etc]

Since many people seem to ask continuously if magisk work with nougat and why supersu sr3 flashable zip by chainfire doesn't work ill try to explain it here.
Since M huawei has updated the kernel to work with nougat they seemed to break some important stuff. Or disabled it. I cannot tell for sure. And since sources aren't out we can't tell for sure if it's disabled or just broken.
Supersu and magisk is relying on loop to get it system less. This requires a .img which is being mounted to the path which is being executed on boot. But with loop being broken or disabled the phone will for some reason not handle this well.
But this is the reason why supersu and magisk isn't working when trying to install it reboots twrp notice that even if you manually patch boot so it contains all info related to magisk or supersu images it won't help you. Because you'll not be able to use magisk since the system will not boot. Due to loop is broken or disabled.
So there will be no magisk for nougat? And when will it come if it'll be working?
Wait until kernel sources are dropped.
So can we get magisk working?
Well yes.
Our best shot is to actually create a folder in /data which is being symlinked to / or if we do a similar approach on how supersu works on nougat. But for now we can't mount images and that's why everything fails.
Hope this sum up things for you.
Sent from my CUBOT_MANITO using Tapatalk

You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.

Telperion said:
You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.
Click to expand...
Click to collapse
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk

LastStandingDroid said:
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk
Click to expand...
Click to collapse
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.

hachamacha said:
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.
Click to expand...
Click to collapse
Many people probably have but won't try get people fired because of leaks
Their working on to get in touch though
Sent from my CUBOT_MANITO using Tapatalk

Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.

Telperion said:
Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.
Click to expand...
Click to collapse
I'm not sure how much clout I would have, but it wouldn't hurt to ask.

I think @svetius is more into this.
You should ask him about it tbh
Afaik he's the on that handles this
Sent from my CUBOT_MANITO using Tapatalk

in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method

@simo255 lol

simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method
Click to expand...
Click to collapse
please state more info about which image you use, whether you have stock firmware installed and which steps you took in twrp to install supersu and consecutively, magisk.

[Root] Phoenix OS x86/x64 v2.0.7 (13 June) Rooted Images

Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images

Oooh... now I can test this to see if it fixes my G+ compatibility issue

The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you

meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/

The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working

meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...

The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.

If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.

meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.

irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.

irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211

#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?

Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.

This will work on a Nexus 9 or it only works in pc's?

when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy

Waiting for rooted system.img for Phoenix OS 2.1.0

SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy

MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?

Guys, when to expect a rooted image for V 2.1.0 x86

thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?