Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).
inc0n3ck said:
Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).
Click to expand...
Click to collapse
Did you try toggling Magisk hide off/on as per Magisk support thread?
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
@Didgeridoohan has a good article on the matter here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Principially Magisk Hide is working in this state and e. g. my banking app was, too.
Other users have full support, but i don't know what's wrong here.
Everything Magisk was special when i tried Los17. Bootlooping after a Magisk update with successful reboot after the umpteenth time.
Endless boot after installation of the Youtube Vanced module. Entering TWRP at boot also was impossible(but you could access Fastboot), but there seemed to be some watchdog timer and after about 30min Twrp came up instead of the os.
Related
Hey guys, is sky go still blocked on rooted devices? I have an S5 that i rooted a while ago but returned to stock for the purpose of sky go, Has anyone found a way around it? i know there was rootcloak and a few other apps to try and prevent it but those didnt work back then, Hope for a reply. thanks alot guys.
Wasn't there a sky go xposed module for this? I maybe wrong... I use "hide my root" and a stock kernel when using the "all 4" channel 4 on demand app. Maybe the same will work for you? Root cloak didn't work me, the normal or xposed version both were fails for me. But the app I mentioned did the job.
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot
I felt I had a simile but without effect hoped for , try this
There's finally a way round the restriction that prevents people with rooted Android devices from being able to use Sky Go.
Follow this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
It involves:
1) returning to stock ROM (unrooted)
2) installing a custom recovery such as TWRP and booting into it
3) installing Magisk
4) installing Magisk's version of phh's Superuser
5) rebooting into system
6) installing phh's Superuser app
7) installing Magisk's management app
8) whenever wanting to use Sky Go, disabling root in Magisk's app
9) re-enabling root afterwards in the same app.
I can confirm this works reliably. I have it running on my rooted LG V10, having never managed to get Sky Go to run on a rooted device before.
Do bung the developer who invented Magisk a donation if it's worked for you and if you can.
Sent from my LG-H960 using XDA-Developers mobile app
My device: Gt-p7500 with lollipop aosp.
Sky go was detecting the rom (not rooted ) wasn't stock and it considered that as a root problem showing the error message. After many tests I assumed sky go was detecting the aosp rom by reading a string "key tests " in the build number and looking the SeLinux mode permissive.
The solution was: rooting the device, mounting system with twrp, downloading app "prop-editor "(play store) , edit the parameters of the build.prop file (under folder system) and replace every "key tests " string( with whatever you want) in the parameters., set enforcing mode of Se Linux by flasing a zip file ( https://forum.xda-developers.com/devdb/project/dl/?id=12047) After that full unrooted the device, reboot....and finally everything works. I hope it will be useful. Ciao.
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?
Last night before turning in I decided to update to the latest version of Magisk Manager, 6.0.0. This morning I turn on the phone and have no cell service or data. I noticed on the main screen of Magisk it only displays Installed Version v17.1 and Uninstall instead of the usual Latest Version, Installed Verision, Tap to Start SafteyNet check, etc.
I have been looking around but can't seem to find any posts with the same issues. At this point tempted to uninstall Magisk and reinstall to see if that fixes it. Anyone have any suggestions.
I have tried restarting the phone, changing the Cell Service from LTE to 3G, removing all forms fingerprint and pattern locks but nothing so far.
Running
Nexus 6P
Lineage 15.1 August build
Magisk 17.1
TWRP : Most recent
Open GApps
Thanks
:good:
I don't believe that Magisk Manager could do that to your device. I'm running the same setup as you and I'm not having any problems, only difference is I'm using magisk v17.2 instead of v17.1. You can find the new version at magisk's github (I'm not able to post links on my messages yet)
Hope it helps!
Zombillano said:
I don't believe that Magisk Manager could do that to your device. I'm running the same setup as you and I'm not having any problems, only difference is I'm using magisk v17.2 instead of v17.1. You can find the new version at magisk's github (I'm not able to post links on my messages yet)
Hope it helps!
Click to expand...
Click to collapse
Thanks for your reply. It turns out it had nothing to do with the software or the phone. We experienced severe weather in the area, something we are not accustomed to, and it took out big areas of our cell network. Sorry for wasting your time. Everything is good now.
Stock out of box Samsung Galaxy S6 From Boost Mobile.
Disclaimer >>>Might Work With the Sprint S6, since Boost is just the prepay of Sprint, the same phone I think...
First to say this is a rare find (2015 Release) but if you can get your hands on this awesome handset it has, 8Cores, 32Gb of Memory, 16mp.Cam, and as far as i know the Last Samsung Galaxy With the iR Blaster. So I take No-Responsibility to any Malfunctions or Broken Devices. Personally Had Little to Zero Problems Achieving this I would say This is the Best, Most stable Rooted Device i'v ever owned.
Im Posting here expecting that everyone knows what ROOT, TWRP, CWM, SuperSU is, Developer Mode/How to activate, how to reboot to recovery/Download Mode, Flash via Odin, and use TWRP.
I'll try to put this whole thing in chronological order. so out of box... or anyone who can restore their device back to this build BOL1It Works Flawlessly, Very-Fast/ResponsiveSystem Wide Equalizer>V4A-starts on boot, Xposed FW, Xprivacy, Lightning Wall, and The Google PlayStore still works.
Take Phone out of box [UNACTIVATED/NOSIM/AIRPLANE] LoL... Turn on at home alone... DO NOT CONNECT TO WiFi/DATA it will force update BOL1. Dont sign in google Acc. or Samsung Acc. SET UP http://wakasoftware.com/app-freezer-setup/ Once Completed With Freezer App Set up Reboot and Freeze The following Apk.'s
Search (Update) in Freezer app. You should find [com.sec.android.fotaclient, com.wssyncmldm, com.sec.fwservice, com.sprint.ce.updater, and [NOT100%ON com.policydm] Disable them. Next search sprint in Freezer; Disable every apk. listed under sprint search [com.sprint.zone, com.sprint.psdg.sw, com.samsung.sprint.chameleon, com.sprint.w.installer, com.sprint.ce.updater, com.sprint.w.prefact, com.sprint.dsa, com.samsung.sprint.setupwizard, and com.sprint.voicemail]
You can probably leave voicemail enabled boost has theirs installed anyways. Not sure if sprint-Vmail works or not. Go ahead and freeze any bloat ware or apps you don't want. Disable at own risk. If something messes anything up, reboot to recovery, factory reset, then start over lol
THIS WILL TRIP KNOX
Alright now go developer options and turn on OEM unlocking (allow the Bootloader to be unlocked) Now im going to thank (spammy l) XDA Member for this post https://forum.xda-developers.com/sp...ainfire-autoroot-stock-custom-kernel-t3294308
Follow That Root Method-Just USE THE LATEST SuperSU & TWRP instead. Im on [SU 2.82-SR3] & [twrp-3.3.1-0-zerofltespr] Once obtained Root, an have installed TWRP&BUSYBOX; Create a Custom Recovery backup-TWRP BEFORE you go on to install XposedFW.
You can connect to WiFi/Data, set up google, samsung accounts, and activate wireless services/put SiM Card Back/Disable-airplane-mode now that you have the sprint apps disabled. WARNING if you root this without sprint apps disabled sprint will detect root on the phone and try to force update and continuously restart the phone only 10seconds or so after bootup. I did not know this when i first activated my services. Even after i turned off wifi and pulled the sim card out it was still rebooting only 10seconds after bootup. Giving me only moments to navigate to freezer app and search ''sprint'' and freeze freeze freezze.... so thats why we freeze them first. Also by disabling the sprint Apk. s it Removed the Boost Mobile Boot Animation not sure which one but just FYI just see stock samsung boot.img cool still.
Next have to Thank (wanam Contributor/Developer) For Their Forum( https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ) on how to install XposedFW For [5.1/6.0]Lollipop/Marshmallow. Follow That to get Xposed Installed properly. Once flashed it dose take a few minuets to startup, it will boot cycle a couple times, be patient.
Last but my personal favorite piece of software to place in to the system, ViPER4Android-FX 2.5.0.5
My last shout-out goes to (kevintm78 Senior Member) for his method on installing V4A The Proper Way. Here (https://forum.xda-developers.com/note-4/themes-apps/how-to-viper4android-install-proper-t3691597) after all that you should make a new custom recovery point to save your work. Thanks to all just wanted to put all that into one place for this specific build of phone.
A Few Apk. s to Mention
--Galaxy Universal Remote Version 4.1.3 out there on the web<<aptoid
--XBooster-Free Version 5.1.2 PlayStore
--Physical Button Music Control Version 4.0 beta6 Xposed Module
--lightningWall Version 3.9.2 Xposed Module
--APM+ (Advanced Power Menu) Version 17.12 Xposed Module
--XPrivacy Version 3.6.19 Xposed Module
--Flappy Bird Version 1.3 lol...
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
night hawk said:
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
Click to expand...
Click to collapse
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Shredz98 said:
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Click to expand...
Click to collapse
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Disable the modules you have installed.
Reboot, does it loop?
If no then it's a module
If it does then it's your boot img
I'd recommend booting your patched boot img then directly installing via magisk (do not reboot until you have)
Hope this helps
night hawk said:
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Click to expand...
Click to collapse
The issue is definitely lucky patcher, I had the same problem and my phone was useless until I got rid of it. So it seems it's not playing well with A11 or OOS11 in any case do not use it or you'll end up in a boot loop.
Cheers!
Ah lucky patcher..oh dear, can't help you with that crap.
Best advice, get rid
Bummer about Lucky Patcher....
In b4 the lock.
I can confirm the same findings, lucky patcher seems to break reboots later.
Hopefully a new version will find and resolve the issue, but until then not much we can do but to wait.
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
uaktags said:
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
Click to expand...
Click to collapse
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
night hawk said:
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
Click to expand...
Click to collapse
Did xposed work on 11?
night hawk said:
...
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. ...
Click to expand...
Click to collapse
@night hawk
Hi!
You better read the XDA Forum Rules and refrain from such topics. We don't accept discussions about issues with warez!
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
THREAD CLOSED!