Related
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Thank you for this!
Sent from my SM-P900 using Tapatalk
trying to build kernel
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
dodo99x said:
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
Click to expand...
Click to collapse
It looks like you're in Windows. To my knowledge it is not possible to compile a Linux kernel in windows. I would recommend downloading virtual box and installing some Linux distro in there. This is what I was talking about in the "environment" section at the top of the article.
For android development I find that you need access to a lot of tools where some are only available on Windows and others are only available on Linux so a Windows PC with a Linux VM is ideal in my opinion.
Oh ok, no problem. I just misread the guide. I've setup a build environment in a vm before to compile aosp for my Nexus 10. Shouldn't be too hard to do it again. I recently rebuilt my pc so the vm I had got nuked.
Sent from my SM-P900 using Tapatalk
ok I got my Ubuntu VM up and running using this guide
http://forum.xda-developers.com/showpost.php?p=50748836&postcount=25
installed android NDK to ~android/NDK, and unzipped the kernel source to ~android/kernel
followed your guide to build a SELinux permissive kernel but i'm getting some errors when trying to compile. here's the output:
http://pastebin.com/Npdu7J5h
EDIT: retried doing the EXPORT command and now it seems to be compiling
dodo99x said:
EDIT: retried doing the EXPORT command and now it seems to be compiling
Click to expand...
Click to collapse
When you export a variable in the terminal it only exists for that one session, so if you open a new terminal instance you need to run the command again. If you want to set it permanently normally you can just put the export command into ~/.bashrc
Oh I see. I'll give that a try. I was able to create a new boot.img following the rest of your guide. I have yet to try flashing it though. Will have to find some info about all the kernel options that can be set. Hopefully be able to integrate HMP to get all eight cores running at the same time.
Sent from my SM-P900 using Tapatalk
Cool, let us know how that goes. I wonder how much it would affect battery life.
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Click to expand...
Click to collapse
I tried to install this using VBox Odin and I couldnt get it to work. Tried using BOOTLOADER and also PDA. Not sure the correct one but neither worked for me. Also, Moblie ODin hasnt yet worked but when it does, things will be much easier for me at least.
I have a newly rooted SM-900. I will have to find time someday to compile the kernel against what I have. Must be a slightly newer version than the one you posted. That is only thing I can think since I just got my 12.2. Thanks for the detailed info.
Camera?
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
aarstar said:
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
Click to expand...
Click to collapse
The camera fails for me too. I dumped a logcat and isolated the issue here:
W/ActivityManager( 2746): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
V/ApplicationPolicy( 2746): isApplicationStateBlocked userId 0 pkgname com.google.android.GoogleCamera
But... the camera is not a huge deal. It did, however, break wifi. I did not get a logcat of that yet, but I would assume it is also a permission issue.
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
aarstar said:
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
Click to expand...
Click to collapse
Wow, I totally missed that entire line in the OP... You literally just made my whole day. I fought this all day long, desperate to get ubuntu working. Thank you for pointing that out.
I get "xt_mark.h" is missing (no such file or directory) error. Any idea why that may be?
I'm using the source for p900 international hoping that I may sidestep the camera issue that way (by enabling permissive to the international kernel I mean), but as it stands it does not compile.
I've googled it but until now it was/is to no avail...
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play).
Click to expand...
Click to collapse
Hey Graeme H,
we both have the same intention. I am downloading the international Kernel at the moment and will compile it again for you guys. The download takes a little longer as I am at vacations.
I am going this route: doviak.net/debian-kit/debian-kit_p00.html . In the future I would like to have arch linux running on this device but a customized debian would be okay for the beginning, too.
Eventually I will try to use framebuffer instead of vnc or something like that. I would love to use sublime-text and dwm on that device with that resolution
Good luck guys. I will try to update.
Edit: hehe I have dwm in front of me now and the resolution is so high that I am barely able to read
Compiled the kernel and flashed in on my device but my camera is still not working. Maybe we need to edit the config:
# Camera sensor devices
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
CONFIG_VIDEO_S5K6B2=y
# CONFIG_S5K6B2_CSI_C is not set
CONFIG_S5K6B2_CSI_D=y
CONFIG_S5K6B2_POSITION_FRONT=y
# CONFIG_S5K6B2_POSITION_REAR is not set
CONFIG_VISION_MODE=y
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
Click to expand...
Click to collapse
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
PHP:
smylion said:
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
Click to expand...
Click to collapse
Compiled from Kitkat source. [ur#l]erhan.es/upload/sm-p900-permissive-intl.tar[/url] (odin)
Thank you but the link does not work
smylion said:
Thank you but the link does not work
Click to expand...
Click to collapse
Sorry, it is erhan.es/upload/sm-p900-intl-permissive.tar
Hi everybody!
I use the stock lollipop 30A, by Skin1980. Big thanks for his great work! :good:
In the Dual Window, originally you can use only the LG apps. Root and build.prop modding, you can then all installed app in Pad.
Root Explorer, or Build Prop editor. Search this line:
persist.splitwindow.support_all: here originally: false Modding this: true , then reboot. The results in images.
Before you do anything, save, save, save!! If you have bootlop, the factory reset don't help, because the modding occured in system files. Just the rom reflash helped, which re-write the system, with the originaly build.prop
Good luck/modding to you.
That's cool. Just tried here and it works perfectly.
Thanx!
Works like a charm
Tanks! Do you know if this can be ported to other custom ROM also, like CyanogenMod?
just repot Flex multi windows also working
I have used this app from this guy on my LGs, like G3, and it works
http://forum.xda-developers.com/showthread.php?t=2707310
basically it's a easier way to select the apps you wanna show in multi windows, and if that doesn't work, usually go into phone/tablet 's setting page, and toggle dual-windows on/off, and it will work
It's working on my V500 on lollipop
---------------------------
and i don't think it will ever work on CM, because you might need the LG framework to get this working, correct me if I am wrong
but MultiWindows is coming in Android M i heard
I'm not sure if anyone will find this of use, but I did so I figured I'd post it for everyone to use:
I recently ran into issues running a few binaries on my V10. After doing a bit of research I found that non-PIE (position independent executables) will not run on newer devices (5.0+). Given I needed to run non-PIE binary, I looked further into a fix. This lead me to a thread posted here on XDA about bypassing the PIE check on Android L for the Nexus 5. Unfortunately the linker included in this fix is not usable by our device. Thankfully the linked thread goes into some detail about how to patch /system/bin/linker to allow non-PIE binaries. After reading into the provided information, I was able to patch our own linker and get my non-PIE binary to run just fine.
I've thrown together a flashable ZIP that simply replaces /system/bin/linker with a patched version that will allow non-PIE binaries. :good:
As a note:
Code:
[I]
[B][COLOR="Red"]
I HAVE ONLY TESTED THIS ON MY OWN LG V10 H901 ON MARSHMALLOW (6.0).
I CANNOT VOUCH FOR ANY OTHER MODEL, VERISION, OR DEVICE. AS ALWAYS
BE SURE TO PERFORM A BACKUP BEFORE FLASHING![/COLOR][/B]
I am, by no means, a developer. I simply dabble in Android for fun. I am not
responsible for any issue(s) caused by using this patch and you are doing
so at your own risk.
[/I]
So what this does is allow older non 6.0+ compatible apps to work?
Swizzle82 said:
So what this does is allow older non 6.0+ compatible apps to work?
Click to expand...
Click to collapse
It's helpful for any app with binaries that don't support position independent execution. In my case it allowed me to use my debugging server (which wouldn't run otherwise).
this works on the latest cm build for the htc one m8
but im a little confused as to which byte was modified can you please explain how you found which byte to replace i am using hex editor on my phone and cannot find the hex allocation mentioned in the forum
well i thought it worked until i went to restart my phone and it woudnt boot... thankfully tho i didnt delete the old linker file i just renamed it to linker.old so i was able to boot into my recovery and use its file manager to fix the issue
for now i guess i will create a script to automatically switch the file when i shutdown my phone and switch it back when it starts
Hi Guys!
I would be happy if someone could post a tutorial on how to Bypass PIE on Android 6.0.1
I have some experience in disassembling ELF files, but do not know where to look for disabling PIE in linker file. I would like to learn how to do it on my own, so i am not asking someone to patch my linker file.
Using G928F with Android 6.0.1
Thank you in advance!
Please help me to patch my linker
Works on Samsung J710MM (Marshmallow 6.0.1) perfectly. Thanx a lot!!!
Could anyone help me bypass PIE On marshmallow Touchwiz 6.0.1 would greatly appreciate your help?
Deleted
*If you do not want to read the whole case,scroll down for a TL;DR*
Hello,so I have heard that android M 6.0.1 has different bunch of new features including multiwindow.That was pretty cool and I checked on my phone if it was there but it was not.Then after some researching I found out that you have to edit the build.prop and change the 'user' to 'userdebug'.Since I have average knowledge on rooting as I have done it on other phones I know that editing system files can't be done without rooting or something like that.The second way was using ADB and I learnt some things about ADB,watched some vids and tried it with no success because even after getting all the drivers working ADB either it does'nt recognise my phone or it doesn't load TWRP at all and just hangs on waiting for phone(or some message like this can't remember at the moment,may confirm later).I also heard that samsung phones use some fastboot thing which I have no clue about.So can anybody tell me a way to pull the build.prop from my J5(6) using an other way which doesn't require root or help me make the ADB method work?If you want more information or something else feel free to ask.
TL;DR:I want multiwindow to work on my J5(6).It can be done by editing the build.prop 'user' line but i do not want to root my phone as its still in warranty.I failed at ADB method so im asking you for help to either show me full ADB steps to edit the build.prop or tell me another way.Thanks in advance.
then use an app, search for them in play store, there is a lot of them
DontTouchMaPhone said:
*If you do not want to read the whole case,scroll down for a TL;DR*
Hello,so I have heard that android M 6.0.1 has different bunch of new features including multiwindow.That was pretty cool and I checked on my phone if it was there but it was not.Then after some researching I found out that you have to edit the build.prop and change the 'user' to 'userdebug'.Since I have average knowledge on rooting as I have done it on other phones I know that editing system files can't be done without rooting or something like that.The second way was using ADB and I learnt some things about ADB,watched some vids and tried it with no success because even after getting all the drivers working ADB either it does'nt recognise my phone or it doesn't load TWRP at all and just hangs on waiting for phone(or some message like this can't remember at the moment,may confirm later).I also heard that samsung phones use some fastboot thing which I have no clue about.So can anybody tell me a way to pull the build.prop from my J5(6) using an other way which doesn't require root or help me make the ADB method work?If you want more information or something else feel free to ask.
TL;DR:I want multiwindow to work on my J5(6).It can be done by editing the build.prop 'user' line but i do not want to root my phone as its still in warranty.I failed at ADB method so im asking you for help to either show me full ADB steps to edit the build.prop or tell me another way.Thanks in advance.
Click to expand...
Click to collapse
just root it, in my case 24months from the store, as no Samsung Service here, they will fix my device Knox tripped or not...
Wizardlysense said:
just root it, in my case 24months from the store, as no Samsung Service here, they will fix my device Knox tripped or not...
Click to expand...
Click to collapse
Yeah,looking forward to rooting but anyway thanks for your help.
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: