I rooted my phone at the beginning of November to install call recording - and everything went well.
I needed to check a recording yesterday and it had not recorded properly (caller was not recorded) and when I checked my phone rootchecker showed that the phone was no longer rooted.
What would have caused the phone to de-root without intervention from myself.
My phone is an Xiaomi Redmi Note 9 on Android 10.
The "root checker" apps are useless, they just ask the root manager for root permission for no reason at all, since you can simply take a look at the magisk manager and check if stuff is working properly from there. So you're basically giving root permission (which is a not a toy) for a random app so it can say if you have root or not lol.
Anyways, could you send more info like screenshots from the manager, and things like that? Your report lacks info.
Even so, I could recommend you to simply try and reinstall magisk to see if it fixes the problem, just download the magisk zip and install it as if it was a module, using the manager, and reboot. If you can't do that, install through the recovery (twrp or whatever you use).
Related
POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.
Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.
Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.
It didn't worked. S7 edge exynos (6.0.1)
Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?
Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.
Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?
Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.
immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily
Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.
Today I updated to Magisk-v13.1, first it all worked grade and SafetyNet successfully past again in an App.
Then I tried it in another app, there it didn't worked, so I wanted to restarted the system and looked again if it worked, but then I had lost Root after reboot.
I reinstalled Magisk-v13.1 and tried it again and again, but it seems like it all is working grade, even Magisk Hide on apps like Root Checker and other, but on a certain app (Seqr) it isn't working and after reboot Magisk isn't working at all and Root is gone.
Magisk log, please. Both after using the troublesome app and after the reboot (you'll have to reboot into recovery and copy the log from /cache).
Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!
Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.
Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!
At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).
Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.
Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]
I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
Hi all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?
No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.
Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".
I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.
Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.