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?
Thanks to the release of other roms for the R1_HD it was proven that the hardware does work as an FM radio.
The spec sheet did say it had the feature.
To anyone interested in adding the radio. Attached is a flashable recovery zip that will enable it for you.
ATTENTION:!!!! For the radio to function, the kernel needed to be made "permissive"
This was line in logcat that pointed me to permissive.
Code:
W android.fmradio: type=1400 audit(0.0:641230): avc: denied { read write } for name="fm" dev="tmpfs" ino=9679 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fm_device:s0 tclass=chr_file permissive=0
So this update will re-flash your boot.img , And because the newest supersu has been systemless it modified your boot.img. This means after flashing this you will need to reinstall supersu.
This obviously only will work if you're rooted and have custom recovery.
Note,.1
the changed boot loader may cause the stock messenger app to force close. Other sms, and txt apps seem to be fine.
Note. 2
Just noticed amazon music and amazon video did not work after installing this. Reflashing the stock boot image allpws them to work again bit kill the radio.
Will update the zip if i find another way to allow permisive and have amazon apps still work
Boot.img seems to effect too much for my likeing. Found new (old) way to switch to permissive. .
New method for installing does not change boot.img
mode changer app is old and as of now it has hard coded root, looking for the binary in /system/xbin. This new fm_Radio_WITHOUT_boot.zip also has the fix for this root problem.
Need to install this SELinux Mode changer app
http://forum.xda-developers.com/showthread.php?t=2524485
http://forum.xda-developers.com/devdb/project/?id=1561#downloads
Awesome.
Works well from what I tried. Thanks for sharing!
Anybody know if this will KO safetynet? I already change to permissive and back, as well as tried just copying the system files, so that doesn't ko it. However, not sure what else is done.
Guess I could back up and try. If nobody knows I guess I will, but thought I would ask first.
This worked great, thank you. I'm running vampirefo's safe v6.6. Flashed your FM zip in TWRP, rebooted and it worked.
Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
mumbel said:
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
Click to expand...
Click to collapse
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.
Rotation fix
FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44
mumbel said:
Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",
Click to expand...
Click to collapse
I did not make the change to be permissive. I just used the boot.img from zenrom.
But now I have decided to suggest using the selinux mode changer app instead of changing the boot.img
theredbaron1834 said:
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.
Click to expand...
Click to collapse
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.
FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
Please restore to your previous boot.img, reflash supersu and use the mode changer app to make it permissive. Will need to run the new install zip so that root will work with mode changer.
mrmazak said:
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.
Click to expand...
Click to collapse
Yeah, not sure what's up with it. Just know that vampire's twrp had the name p6601 and the other one worked.
Why do we have to have root if we have TWRP? Or do we not really need it?
voluptuary said:
Why do we have to have root if we have TWRP? Or do we not really need it?
Click to expand...
Click to collapse
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.
Rotation Fix!
Wow, that worked on stock v12 (8GB/1GB and 16GB/2GB models)!!!! Thank you so much!!!
bjbjs said:
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44
Click to expand...
Click to collapse
LOL... Was linked to an old post of mine that I never followed up.
mrmazak said:
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.
Click to expand...
Click to collapse
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.
parkerlreed said:
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.
Click to expand...
Click to collapse
Thanks. Good to know. I was just trying to stay with the version from tje developers thread.
Just installed SELinux Mode changer app downloaded from f-droid.org and flashed the fm radio zip file wow working like a charm!
Great job, dude!
I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?
ase1590 said:
I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?
Click to expand...
Click to collapse
Yep the standard headphone antenna
PROPS to all those hardworking developers who developed all these apps!
First of all u need root and TWRP recovery;
Then install BusyBox by meefik, important that you download the right one.
Put the latest Viper4android v2.5.0.5 (Android 4.0~7.0) https://forum.xda-developers.com/sho....php?t=2191223 in your sd card or external card. Mine can only read the external sd card.
Flash via TWRP.
BEFORE you open the app. install https://forum.xda-developers.com/and...ernel-t3333549
Then open the Kernel Auditor app then go to the Misc Controls. Set the apply on boot. Toggle SE Linux to Permissive.
Now you will be able to open viper and it should be working just fine!
When you reboot your phone, it will take five seconds for the kernel auditor to set the kernel to Premissive-mode.
chrisss5000 said:
Put the latest Viper4android v2.5.0.5 (Android 4.0~7.0) https://forum.xda-developers.com/sho....php?t=2191223 in your sd card or external card. Mine can only read the external sd card.
BEFORE you open the app. install https://forum.xda-developers.com/and...ernel-t3333549
Click to expand...
Click to collapse
Hi Christopher,
thanks for that information, but the links you posted are are not complete / don't work. Could you please correct them?
Christian
skyball2 said:
Hi Christopher,
thanks for that information, but the links you posted are are not complete / don't work. Could you please correct them?
Christian
Click to expand...
Click to collapse
Never mind, I think Ifound them:
Viper4Android: https://forum.xda-developers.com/honor-8/themes/viper4android-2-5-0-5-installation-t3468389
Kernel Adiutor: https://forum.xda-developers.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
Not working failed driver installation
not working for me driver install failed : I/O error
Try https://mega.nz/#!Hgg2FArT!nNsEameb8JdMJIMNQKy-EkJy3wXLFfFqESQ_fC6tnS0
It work if u have busybox
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Try https://mega.nz/#!Hgg2FArT!nNsEameb8JdMJIMNQKy-EkJy3wXLFfFqESQ_fC6tnS0
It work if u have busybox
Sent from my CUBOT_MANITO using Tapatalk
Click to expand...
Click to collapse
Hallelujah, it works.:good:
Synthi said:
Hallelujah, it works.:good:
Click to expand...
Click to collapse
I know I used it many times after I read why the driver installation failed
So I put together a zip for myself
Sent from my ALE-L21 using Tapatalk
Hey guys,
After seeing this Magisk module https://github.com/DeicPro/xiaomi-safetynet-fix
I began to experiment to make SafetyNet pass on Osprey.
And finally I was able to do just that.
DO REMEMBER THAT THIS REQUIRES MAGISK WITH MAGISK HIDE ENABLED. THIS WILL NOT WORK WITH SUPERSU.
IF YOU ALREADY HAD SuperSU, CLEAN FLASH THE ROM AND THEN FLASH MAGISK ZIP.
Steps-
NOTE: SINCE GOOGLE HAS UPDATED SAFETYNET, THE BELOW METHOD NOW REQUIRES MAGISK v14.0+-
Open the build.prop file located in /system. [REQUIRES ROOT]
Add this line to the build.prop file-
For XT1550(Retail Asia | India (2GB))-
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
For XT1543(Retail Latin America (1GB)) -
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
For XT1540(Retail US (2GB)) -
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
For XT1540(Retail US (1GB))-
ro.build.fingerprint=motorola/osprey_retus/osprey_umts:6.0/MPI24.65-25.1/1:user/release-keys
Save and Exit.
Make sure you have enabled Magisk Hide in Magisk setings.
Reboot.
NEW! Magisk module is available here.
~Please read the Note section below~
---------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE-
1. The fingerprint values need to be exactly the same. Any small change will trigger safetynet.
2. You can use any fingerprint value for your device. It's not necessary for you to take value specific to your device. As long as the fingerprint is valid, it will work.
3. This same trick should also work on Merlin devices.
4. Read this too please.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to -
@Rohi09 for providing stock ROM XT1550 build.prop
@Deic for his magisk module which inspired me to do this.
@KrisM22 for providing XT1540(2 GB) values.
@xMotoDA for providing XT1543 values.
@lettucecube for providing XT1540(1 GB) values and creating the Magisk module.
This method is working fine on purenexus rom
This is only for Asian Ospreys with 2GB of RAM, right?
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
xMotoDA said:
This is only for Asian Ospreys with 2GB of RAM, right?
Click to expand...
Click to collapse
Does that really matter?
Changing these specific values to the ones in the stock ROM makes SafetyNet pass! Since mine is dual sim and a different model I changed this in build.prop:
Code:
ro.product.name=osprey_retla_ds
ro.product.device=osprey_uds
ro.build.product=osprey_uds
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Click to expand...
Click to collapse
Try to enable Magisk Hide for that specific app. Its there in the settings.
coolguy_16 said:
Try to enable Magisk Hide for that specific app. Its there in the settings.
Click to expand...
Click to collapse
Nothing happened. I even went a step further by totally uninstalling Magisk. Yet no luck.
bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Does that really matter?
Click to expand...
Click to collapse
I cant also log in my digi bank acount...i hav got a fixed deposit there....what is creating problem?any help
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Grt work....
I didnt found two lines in my build prop..so i add those...and safety net passed...
Thanx mate:good:
Can someone help me with this build.prop. Its from aex 4.2
Susan Dahal said:
Can someone help me with this build.prop. Its from aex 4.2
Click to expand...
Click to collapse
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
coolguy_16 said:
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
Click to expand...
Click to collapse
It worked Thanks
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
KrisM22 said:
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
Click to expand...
Click to collapse
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
coolguy_16 said:
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
Click to expand...
Click to collapse
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
KrisM22 said:
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
Click to expand...
Click to collapse
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
coolguy_16 said:
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
Click to expand...
Click to collapse
It works! Huge thanks!
(This is LineageOS 5-11-17 )
When I removed SuperSU, I chose not to clean up the boot since I saw someone who supposedly bricked their phone doing that, so of course Magisk gave a nasty message about it when flashing,
so I wiped everything (dalvic/ART,Data,System,Cache) and rebuilt: flash rom, flash gapps, install, when get to desktop, install Magisk Mgr with play store and d/l zip(Magisk-v12.0.zip), and go back to TWRP and flash that zip (it does not say anything about su), but after boot I installed TBPro and discovered that yes, indeed I had root. Somewhere in there I set Magisk to "hide". So modified build.prop by only adding the one line you gave me up 2 posts (repeated below) and voila! And PokeGo works!
This is the line I added:
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
HINT: I used the JRummy Root Browser for a file manager to copy the line from a text file on my SDcard(from PC), to /system/build.prop and within that I use RB text editor. I say that because for some reason X-plore didn't work for me - edited fine, said saved, but didn't. Wasted time with that.
I do notice that HIDE is checked only for PokemonGo for me, so far, but I haven't tried any banking apps.
THANKS!!!.
Oops - next morning, no root access. Magisk status still shows good. Magisk/Superuser shows all 3 apps (BBS, JR RootBrowser, TBPro) and all switched ON.
EDIT: In Magisk/3 bars/Settings/Superuser - Superuser Access - Set it to "Apps and ADB". Root is back!
I believe @coolguy_16 has said this but I just went and tested and used the line from the 1st post:
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
and safetynet works just fine. So it would seem that as long as you have a valid fingerprint for some phone, it doesn't seem to matter what phone you put it on.
It is unknown whether google's "snet" would eventually alert the safetynet folks to this incongruity and then block it. EDIT - I would guess in the long run it would probably be better to use an "exact" fingerprint that would look correct.
EDIT There is a short FAQ in the first post that may help for solving Magisk problems:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Guys just an FYI.
Even though one can pass safetynet, some apps will still refuse to work.
You can try to enable Magisk hide for that specific app(see Magisk settings)
This happens because -
1. The app is sh*t
2. The app checks for other "dangerous props"
So anything which the app finds wrong in your build.prop will cause that.
Well, to find out what your app is checking exactly for.. You will have to decompile it and check for yourself. (Google is your friend)
:good: Great, tks m8.
I am now able to use my banking app (KBC Sign)
(however the app has to be checked in Magisk Hide, otherwise it wont work) :good:
it's for Treble-GSI only
Tested in AospExtended V6.3 (B partition)
1. Bluetooth audio connection fix
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. AptX-HD
1) Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager (APTX for Android Oreo & Pie NOT WORK)
2) Remove /vendor/overlay/RazerAuraBluetoothRes.apk (There's content of aptx and I don't know why it is in here)
!:?촒 resources.arsc5? ?com.android.bluetooth.overlay.razer.aura X 8$attrinteger?,"Gra2dp_source_codec_priority_aptx""a2dp_source_codec_priority_aptx_hd((a2dp_source_codec_priority_aptx_adaptive##a2dp_source_codec_priority_aptx_tws [email protected] 0 PK !:AndroidManifest.xml븪켷 A ?總?bp굛 ?C(??*
Click to expand...
Click to collapse
3) Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
4) Profit!
I've only tested in AOSPExtended GSI v6.3 so if you are in stock only try living in the edge
What was the original issue with BT in Pie?
ewgit said:
What was the original issue with BT in Pie?
Click to expand...
Click to collapse
Fail to connect to bluetooth audio in Treble-GSI Roms
It's due to Razer's overlay issue.
And Also APT-X Disabler exists in Razer's overlays
This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).
Nomyth said:
This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).
Click to expand...
Click to collapse
There are kernel protections in stock that disable modification of the vendor partition. Arter97's kernel has these disabled but I strongly recommend NOT modifying the vendor partition(it pisses off the bootloader). Learning how to make a custom Magisk module would be a better option here...
Nomyth said:
This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).
Click to expand...
Click to collapse
I tried it in stock but don't work at stock (Enabled aptx but connect failed)
Does this actually work? I want the gsi ROMs
Craftingmod said:
I tried it in stock but don't work at stock (Enabled aptx but connect failed)
Click to expand...
Click to collapse
Hmm. If I remember right stock needs aptx libs to work. I tried that at one point and it actually connected, but only succeeded in making my ears bleed with a horrible static screeching when trying to play audio. Maybe both the libs and this thread are required...
This does not work in the ROM suggested too, the Bluetooth fails to work, doesn't even turn on, its something to do with BluetoothResCommon.apk
popeye2468 said:
This does not work in the ROM suggested too, the Bluetooth fails to work, doesn't even turn on, its something to do with BluetoothResCommon.apk
Click to expand...
Click to collapse
Once you delete the BluetoothRrsCommon then reflashing your rom and wiping cache should fix Bluetooth.
Managed to get music working but not in call Bluetooth audio
popeye2468 said:
Managed to get music working but not in call Bluetooth audio
Click to expand...
Click to collapse
In call audio is a known issue of the the base phh-treble rom as per this issue: https://github.com/phhusson/treble_experimentations/issues/374
That being said, if you are running a CAF based rom you may be able to get in call working with methods mentioned in the above issue thread.
Edit: fixed link to proper issue
Not AptX, but apparently LDAC just works on the stock ROM simply by adding it to the offload prop. It's supposedly just part of a standard Android build now, but needs a certification process for the OEM to be allowed to turn it on.
CurtisMJ said:
Not AptX, but apparently LDAC just works on the stock ROM simply by adding it to the offload prop. It's supposedly just part of a standard Android build now, but needs a certification process for the OEM to be allowed to turn it on.
Click to expand...
Click to collapse
Has anyone tried this method? I just got a bluetooth device which can use the advanced codecs so I want to get ldac working.
elyod said:
Has anyone tried this method? I just got a bluetooth device which can use the advanced codecs so I want to get ldac working.
Click to expand...
Click to collapse
I had tried before posting actually sorry, so I can confirm LDAC works fine. I remember there was more than one prop though. I'll try find the ones I changed...
CurtisMJ said:
I had tried before posting actually sorry, so I can confirm LDAC works fine. I remember there was more than one prop though. I'll try find the ones I changed...
Click to expand...
Click to collapse
Thanks I appreciate it. I spent quite a while trying to find other resources for it, best I could find was people porting ldac on Sony phones and I was hesitant to try it on the razer.
elyod said:
Thanks I appreciate it. I spent quite a while trying to find other resources for it, best I could find was people porting ldac on Sony phones and I was hesitant to try it on the razer.
Click to expand...
Click to collapse
Ok, so the following prop change is needed:
persist.vendor.bt.a2dp_offload_cap=sbc-aac-ldac
I can't seem to find the other one I changed, I suspect it didn't exist. I'll try to get back to my scripts tommorow to check. There are various ways to change props. I think there's a Magisk module to do custom ones (I just have my own boot scripts for this kind of stuff).
No porting needed as the LDAC libs are part of Android 9.
CurtisMJ said:
Ok, so the following prop change is needed:
persist.vendor.bt.a2dp_offload_cap=sbc-aac-ldac
I can't seem to find the other one I changed, I suspect it didn't exist. I'll try to get back to my scripts tommorow to check. There are various ways to change props. I think there's a Magisk module to do custom ones (I just have my own boot scripts for this kind of stuff).
No porting needed as the LDAC libs are part of Android 9.
Click to expand...
Click to collapse
Cool, I've modified the build.prop several times using a text editor so that's what I'm comfortable with. I'll give it a shot.
Okay, so I found a magisk module that enabled ldac.
Confirmed working using the companion app for my ES100 bt dac.
popeye2468 said:
Managed to get music working but not in call Bluetooth audio
Click to expand...
Click to collapse
by using this method?