Related
For those of you who want SELinux Permissive, I built this a couple of weeks ago. Set ro.securestorage.support=false in your build.prop if wifi is not working (Credit Morfic).
Flash via Odin
Disclaimer: I'm not responsible if for whatever reason you brick your device
Download
aironite said:
For those of you who want SELinux Permissive, I built this a couple of weeks ago. Set ro.securestorage.support=false in your build.prop if wifi is not working (Credit Morfic).
Flash via Odin
Disclaimer: I'm not responsible if for whatever reason you brick your device
Download
Click to expand...
Click to collapse
Thanks, this is really useful. Have you considered posting this in development?
Also do you plan to do more kernel development, for our device?
Sent from my SM-P600
LMMT said:
Thanks, this is really useful. Have you considered posting this in development?
Also do you plan to do more kernel development, for our device?
Sent from my SM-P600
Click to expand...
Click to collapse
I do plan on moving forward with developing this kernel as soon as Samsung releases kernel updates for their big.LITTLE technology. Namely Heterogenous Multi-Processing.
Wroth hug if samsung doesn't support our device do you think you could adapt their code from the new devices that will? If samsung won't give it to us I imagine a device can
Sent from my SM-P600 using XDA Premium 4 mobile app
I'll continue to develop this kernel and look at posting an update to the dev thread in the next few days. If samsung makes improvements on other devices with the Exynos 5 series, it can surely be ported to our p600's.
Duly.noted said:
Wroth hug if samsung doesn't support our device do you think you could adapt their code from the new devices that will? If samsung won't give it to us I imagine a device can
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
aironite said:
I'll continue to develop this kernel and look at posting an update to the dev thread in the next few days. If samsung makes improvements on other devices with the Exynos 5 series, it can surely be ported to our p600's.
Click to expand...
Click to collapse
Thanks for the reply. I really need to turn off auto correct. It always mangles my words when I don't check before I post.
aironite said:
For those of you who want SELinux Permissive, I built this a couple of weeks ago. Set ro.securestorage.support=false in your build.prop if wifi is not working (Credit Morfic).
Flash via Odin
Disclaimer: I'm not responsible if for whatever reason you brick your device
Click to expand...
Click to collapse
This is great. No problems installing. I did need to set ro.securestorage.support=false in /system/build.prop for wifi to work. Now VPNroot and sshdroid work correctly.
I could not find an appropriate place to turn selinux off during boot (i.e. setenforce 0). /init.rc and everything in / seems to revert to original version on boot. I tried sticking it in one of the unrelated startup scripts in the /system folder, but that failed as well. Any suggestions?
Thanks a bunch!
aironite said:
For those of you who want SELinux Permissive, I built this a couple of weeks ago. Set ro.securestorage.support=false in your build.prop if wifi is not working (Credit Morfic).
Flash via Odin
Disclaimer: I'm not responsible if for whatever reason you brick your device
Download
Click to expand...
Click to collapse
Does SElinux Permissive allow us to use Linux Deploy to install linux in chroot on note.
https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy
My note is running on mk1 rooted with autoroot , however I can't use Linux Deploy to install linux in chroot, maybe SELinux enforcing is the cause.
robertchow said:
Does SElinux Permissive allow us to use Linux Deploy to install linux in chroot on note.
--cut url--
My note is running on mk1 rooted with autoroot , however I can't use Linux Deploy to install linux in chroot, maybe SELinux enforcing is the cause.
Click to expand...
Click to collapse
I am able to use Linux on Android (linuxonandroid.org), which I couldn't before installing this kernel. Also used SeLinuxModeChanger (in playstore) to have selinux set permissive on boot.
Hope that helps.
Linux Works
robertchow said:
Does SElinux Permissive allow us to use Linux Deploy to install linux in chroot on note.
https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy
My note is running on mk1 rooted with autoroot , however I can't use Linux Deploy to install linux in chroot, maybe SELinux enforcing is the cause.
Click to expand...
Click to collapse
I can say that with this kernel you get a fully functional Linux install. I have not tested Linux Deploy, because I use the Complete Linux Installer(linuxonandroid) and by using the kernel in this thread and then ether use Wanam Xposed and set the system to disable SELinux so it is always Permissive or by using the command "setenforce 0" in a terminal before Linux use then use getenforce it shows Permissive and allows for full Linux function. The command getenforce is not needed to run just for verification.
THANK YOU for this kernel!!!!
Many Thanks for this Kernel
I only registered to say thanks for this kernel. Had to use the build.prop tweak in order to get Wifi back. With this, Selinux Mode Changer, and Complete Linux Installer I was able to get Fedora 19 running on the note. Working great. So, thanks again for your work.
How to install
Can someone tell me please how i can flash this Kernel via Odin?
Amadyl said:
Can someone tell me please how i can flash this Kernel via Odin?
Click to expand...
Click to collapse
Flash it under AP
Sent from my SM-P600 using Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
robertchow said:
Does SElinux Permissive allow us to use Linux Deploy to install linux in chroot on note.
https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy
My note is running on mk1 rooted with autoroot , however I can't use Linux Deploy to install linux in chroot, maybe SELinux enforcing is the cause.
Click to expand...
Click to collapse
Linux Deploy is working with this flashed.
Sent from my SM-P600 using Tapatalk
Thanks for the help and a big thank you to the developer
It worked
This is very nice i will try to install ubuntu now
Thank you very much !
Amadyl said:
It worked
This is very nice i will try to install ubuntu now
Click to expand...
Click to collapse
You might want to check the Linux thread and especially this post
http://forum.xda-developers.com/showpost.php?p=49347734&postcount=9
It tells of problems with Ubuntu even with Selinux Permissive. In any case, do post your experience there. I prefer RPM based systems as these are my daily work in commercial setups. As openSUSE ARM is still beta, I went for Fedora and it works nicely.
aironite said:
For those of you who want SELinux Permissive, I built this a couple of weeks ago. Set ro.securestorage.support=false in your build.prop if wifi is not working (Credit Morfic).
Flash via Odin
Disclaimer: I'm not responsible if for whatever reason you brick your device
Download
Click to expand...
Click to collapse
what did you change in menuconfig? I am working on enabling some drivers within the kernel and I dont want to lose the chroot linux ability. Thanks.
Sent from my SM-P600 using Tapatalk
Thank you very much for the Kernel, I think i'll try flashing it.
Do you know something about converting ROMs between familiar devices? (The Note 3 and our Note)
Edit:
When trying to install Ubuntu via LinuxOnAndroid, i'm getting the error "Unable to create loop device" (and i already installed the Kernel!).
Help?
ilayron8 said:
i'm getting the error "Unable to create loop device" (and i already installed the Kernel!).
Help?
Click to expand...
Click to collapse
The kernel only allows you to change SELinux mode, it does not change the default mode. Have you switched selinux mode to permissive via a root terminal "setenforce 0" or via an app like SelinuxModeChanger from Play?
caferick said:
The kernel only allows you to change SELinux mode, it does not change the default mode. Have you switched selinux mode to permissive via a root terminal "setenforce 0" or via an app like SelinuxModeChanger from Play?
Click to expand...
Click to collapse
I installed the app and i got from Debian the error "Unable to mount the loop device, after it FOUND the loop.
In Ubuntu, I'm now getting the error "Unable to attach image to loop device".
ilayron8 said:
I installed the app and i got from Debian the error "Unable to mount the loop device, after it FOUND the loop.
In Ubuntu, I'm now getting the error "Unable to attach image to loop device".
Click to expand...
Click to collapse
help?
Hey all,
I've got a Galaxy Tab 4 (SM-T330NU) that I've been attempting to run a Kali distribution on using Complete Linux Installer. I've rooted the device but can't seem to get the SE for Android to change to "Permissive" mode and allow me to run the bootscript.sh without kicking back a message saying "Operation not Permitted" when creating the loop device (mknod /dev/block/loop255: Operation not Permitted). I'm running Andriod 4.4.2 with kernel version 3.4.0-1337409. Any help would be great. I've searched all over and can't find anything that gets me to any point of success with this.
Thanks
-Geoff
gch230 said:
Hey all,
I've got a Galaxy Tab 4 (SM-T330NU) that I've been attempting to run a Kali distribution on using Complete Linux Installer. I've rooted the device but can't seem to get the SE for Android to change to "Permissive" mode and allow me to run the bootscript.sh without kicking back a message saying "Operation not Permitted" when creating the loop device (mknod /dev/block/loop255: Operation not Permitted). I'm running Andriod 4.4.2 with kernel version 3.4.0-1337409. Any help would be great. I've searched all over and can't find anything that gets me to any point of success with this.
Thanks
-Geoff
Click to expand...
Click to collapse
add setenforce 0 in the init.rc in the ramdisk at the bottom of this group
Code:
on property:init.svc.bootanim=stopped
restorecon /data/media
restorecon /data/media/obb
start auditd
start freshsebool
Should set to permissive. Theres an app or 2 also. Ive never used them tho
Full tutorial
A full tuto on how to install Kali Linux Nethunter On SM-T330NU will be nice
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!
Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix
I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.
I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!
I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.
I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.
I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.
Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!
Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.
Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!
I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.
zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks
Same way you did it when rooted. It is launched one time only.
mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.
Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it
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 ?
Coconut Kernel for LineageOS 15.1 - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is only for Lineage-OS 15.1 or ROMs based on it
Since I did not find a kernel for LOS Oreo with USB Wifi drivers, compiled one.
This kernel has been built from the LOS 15.1 source on git with changes adapted for standalone compiling. So i don't know if any ROM feature is broken though i believe stock features should work.
Yes, it supports monitor mode and packet injection.
Drivedroid is also supported by default in the kernel.
How to use USB Wifi Adapters?
Download from attachment and flash the kernel in twrp
Reboot (First boot will be a bit slow)
Plugin the adapter
MAKE SURE THAT USB OTG IS ENABLED IN SETTINGS FOR ANY OTHER LINEAGEOS BASED ROM
Test by issuing the command ifconfig wlan1 up
It's also important to be on latest 5.0.8 firmware (not rom) for this to work.
Troubleshooting
If the above steps don't work for you,
1. Clean install latest oxygen os 5.0.8 from stock recovery by side loading ( this will install latest firmware which is required)
2. Do system, dalvik, cache, data wipe(firmware will be still there)
3. Flash any lineage15.1 based rom or LOS itself and gapps
4. Flash and enable root
5. Flash coconut kernel
6. Install and open terminal and type ifconfig wlan1 up as root to test after plugging in usb card
This is the failsafe method
You can use the usb adapters in any chroot environment(eg LinuxDeploy) - not just nethunter.
To mods - i created a separated thread for people to not flash incorrect zip. if its against the rules, i can merge it.
Source
https://github.com/LineageOS/android_kernel_oneplus_msm8996
Been looking for this for ages, gonna test now
Hey can you add the driver for the Atheros AR9271 Chipset?
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
It's added and tested working. Does it not work for you?
fredrickz said:
It's added and tested working. Does it not work for you?
Click to expand...
Click to collapse
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
hairyfred said:
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
Click to expand...
Click to collapse
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
I think otg maybe disabled by default in omnirom. Search otg in settings
fredrickz said:
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
Click to expand...
Click to collapse
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
hairyfred said:
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
Click to expand...
Click to collapse
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
fredrickz said:
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
Click to expand...
Click to collapse
OTG is detected , it can use usbs etc
Send me a link of the omnirom u use
fredrickz said:
Send me a link of the omnirom u use
Click to expand...
Click to collapse
http://dl.omnirom.org/oneplus3/ latest one
hairyfred said:
http://dl.omnirom.org/oneplus3/ latest one
Click to expand...
Click to collapse
Just downloaded and installed that.
Flashed the ROM after wiping data, system, cache
Flashed supersu
Didn't flash gapps as I was just testing.
Flashed my kernel
Rebooted
Downloaded termux
Typed su
Plugged in USB ath9271 tplink wn722n
Typed ifconfig wlan1 up
And it worked
Possible problems for you
You need to install the latest firmware and modem for OxygenOs 5.0.8 .the latest you can get
For that you can either flash full oxygen OS ROM from op3 recovery by side loading
OR
you could download and flash only the firmware and.modem collection.
I recommend you flash stock oxygen is 5.0.8 official from their website.
Then wipe system data cache and then flash omni ROM latest and gapps and SuperSU whatever
Then reboot and complete initial setup
Then reboot and flashy my kernel.
It will work.
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
fredrickz said:
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Click to expand...
Click to collapse
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Hayatzada said:
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Click to expand...
Click to collapse
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
fredrickz said:
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
Click to expand...
Click to collapse
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Hayatzada said:
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Click to expand...
Click to collapse
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
fredrickz said:
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
Click to expand...
Click to collapse
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Hayatzada said:
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Click to expand...
Click to collapse
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
fredrickz said:
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
Click to expand...
Click to collapse
i successfully installed kali but nethunter terminal crashes when ever i open it.