have created this thread to explain how to use snapchat on a custom rom or port rom so sorry for my English because I'm French and maybe to have post it on the bad section. Anyway
1*) go on super su and un install the root
2*) if you use xposed go on and disable it
3*) reboot (it can take some minute)
4*) go on snapchat and connect you
5*) if you want to be root again use the root file of the rom or flash again the rom on the recovery and choose root on the aroma.
6*) (enable xposed and reboot)
You will not loose your files it works on all phone and rom and snapchat will be able to worck
You can repeat this each time that you are disconnected of your snapchat account.
Why am I still getting the temporary login failure error? Are these the only steps you guys offer?
Related
Hello,
I wish to install (and use) the application DME Excitor (corporate emails) but it is detecting the root in some way.
I have a i9100 device with cm9.1 (latest stable one) & siyah kernel 5.0.1.
I've also made sure (using ExTweaks) that the kernel is not re-rooting the device every boot.
I've tried to remove the root using "Hide my root" / "ExTweaks" / "SuperSU" - and others that say they will hide the root - so far with no success!!!
Can you please suggest how to prevent DME from detecting my root?
I really don't mind unrooting the device - but please do not suggest me to return to stock!
Any help will be highly appreciated! :good::good::good:
bump
bump
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
florox said:
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
Click to expand...
Click to collapse
sorry - no success yet
In case you find any way, please let me know
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
bkraptor said:
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
Click to expand...
Click to collapse
Did you tried it with DME ?
By default, installing the SuperSU from the play store is in '/data' (you can later change that option in settings to be set on '/system')
Anyway, tried that, didn't worked.
Any help would be highly appreciated. :good:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
bkraptor said:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
Click to expand...
Click to collapse
Hi,
First of all thanks for trying to help.
There's no any Superuser.apk in /system/app/ (that's the first thing I've checked).
And I did made sure to uncheck the "Enable Superuser" option within SuperSU.
Still doesn't work.
If you don't mind me asking, could you please provide me with more details on your firmware?
Which rom are you using (is it Cyanogenmod)?
Special kernel?
CWM ?
Any details would help.
And once again, thanks!
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
bkraptor said:
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
Click to expand...
Click to collapse
Thanks for the info.
I was afraid that you would note you're using a rooted stock firmware.
The thing is that by going back to stock rom, there's no need to root it and then unroot it to use the DME (simply use the stock firmware unrooted).
The first post on this thread was a question on how to use the DME on different rom than the stock one (such as CM).
After that being said, I would like to thank you for trying, but this didn't help me, since I wish to use the Cyanogenmod rom and DME together.
If you still have any suggestions on how to use the DME with a non-stock rom, I would be more than happy to hear.
I don't see how running CM is any different than running official. You should check that after disabling Superuser from within SuperSU that there is no "su" binary anywhere within the directories in the PATH variable (i.e. /system/bin or /system/xbin).
Is dual booting a stock/cm setup possible, and would that serve as a "workaround"?
Edit...just thought....even if possible, the dual boot kernel would probably give the game away....
Sent from my CM10 powered S2 via XDA Developers App
is there any solution at this point? I have cm installed and i want to use dme on my rooted phone...
finally!!! fully functional nexus 7 ))
meaning stock browser AND DME running
rooted with this method (from stock 4.2.2):
http://forum.xda-developers.com/showthread.php?t=2233852
installed stock browser from here:
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
SuperSU settings (many thanks to bkraptor):
http://forum.xda-developers.com/showpost.php?p=42009031&postcount=6
Can someone please let me know how to install superSU in /data. As If I instal UPDATE-SuperSU-v1.51.zip by using PhilZ-cwm6. It is installed by default in /system.
If I install it using Playstore it does the same got installed in /system. and further conflicts with SU installed by PhilZ-cwm6.
Will appreciate any suitable advice
Hello! I want to install Safestrap Recovery v3.71 and i have the HDX8.9 WIFI.
"First Requirement: Rooted w/ SuperSU installed." (Hashcodes HowTo from here http://forum.xda-developers.com/showthread.php?t=2612772)
I have the stock rom, the only thing i have done ist root it and prevent OTA-Updates.
Before i make a backup/copy of the stock rom, i dont want to make much changes, like installing an alternate market.
Now my question:
How to secure install SuperSU ?
I found the APK can be downloaded from http://www.1mobile.com/supersu-358316.html.
But can i trust that download from 1mobile ?
Is a scan of the apk with https://www.virustotal.com/ usefull ?
THX for Help ...
Hello! I recently updated to stock 5.1.1. I have root access and have set SELinux to permissive as well. Problem is I cannot delete system apps or convert them to user apps using ROM Toolbox or any other method. I can freeze them though. Any idea how can i do this???? e.g. Chrome at the moment is a system app I want to delete it...how can I do this on 5.1.1
Thank you in advance
Since 5.1 came out I've been reading a lot of threads & posts of users with semi-root problems. Because you don't have a proper o real root access you won't be able to do much. My advise is "simple": Build yourself a prerooted zip with all the latest software:
23.4.A.0.546 .ftf
PRF Creator v0.9
SuperSU 2.46
XZDR 2.8.21
I don't know if the SELinux thing is the same as modifying the XZDR.prop but I did. This 2 lines are "true": dr.initd.active=true and dr.keep.byeselinux=true
I don't have any root problems, even when installing 5.1.1 from 4.4.2. Other thing I do: After installing the pre-rooted .zip, I flash a "stripped" .ftf: I select all the 3 wipes, No final verification and Reset customizations BUT excluding system. The phone starts "like new" but with fully functional root and recoveries.
If you want to keep your semi-rooted phone but want to delete system apps, use a debloating script. It is like a flashable .zip but will not install anything, just delete whatever you want.
I managed to remove movie creator with the kinguser app that comes with kingroot.give it a try
Sent from my D6503 using Tapatalk
Google has recently launched the Tez app for India, which supports payments from banks using UPI.
I tried installing it on my OnePlus X, rooted with xposed framework, Oxygen OS. It gives the message -
Tez can't be used on this device.
Click to expand...
Click to collapse
We've detected software running on your device that may not be secure.
Click to expand...
Click to collapse
I tried searching for solutions which generally end up with - Unroot your phone.
I tried RootCloak, doesn't help.
I don't want to unroot my phone, but I want to install this app.. it's getting quite popular among my friends.
So is there any other way to truly hide my root status for installing this app?
Root ur phone using magiskSU and hide root to tez by magisk hide.
Your device have to pass the safety net check for TEZ to work ,install safety net checker from playstore and test
On OOS it should work with Magisk SuHide option activated.
Remove Xposed forever. And would be better never ever use your rooted device for banking activity.
Unrooting or removing Xposed framework does not gives excuse to run Tez app. I have experienced. As your phone has the custom ROM, you cannot use Tez on your device. You have to completely install vendor's Official firmware on your device
i have no issue with magsik
On my OPO running COS 13.1.2, this is how I got it to work:
• Install Tez from PlayStore
•Disable the Xposed module within the Magisk Manager
•Goto Magisk Hide in Magisk Manager and select Tez to hide
•Disable the Xposed framework within the Xposed app
•Reboot phone
•Open Tez
I have found that once I successfully opened Tez and linked my profile and Bank Account, I could re-enable Xposed and still use Tez after rebooting
If the above process doesn't work for you, unroot your phone, and root it again with Magisk Manager, instead of flashing Chainfire's SuperSu
Follow simple steps -
1. Just uninstall xposed framework (No need to remove exposed installer)
2. Register tez / BHIM (dismiss root notifications)
3. Reinstall / update xposed framework.
I was facing issues during registration process only and im not using any third party app to hide root.
Now both are working fine.
Run Tez or any other secured apps on rooted device:-
I had the same problem with my rooted phone and magisk didn't do their part or we can say unsuccessful.
So I tried this and it works...?
Caution:- Follow step-by-step.
1. First download these three apps(in external card):- (Download all in recovery bootable zip )
1(a). SuperSu v2.82 RS3 (Recovery Flashable) :-
1(b). SuHide v1.09 Lite (Recovery Flashable) :-
1(c). SuperSu Config Aroma File v1.00 (Recovery Flashable) :-
2.Now root your device in TWRP mode
2(a). Select supersu config file and install it in "systemless SBIN mode" (modes showed when you start installation) and then leave all the other options default.
2(b). Install SuperSu into twrp boot mode.
2(c). Reboot once into android (or main screen) then again reboot it in recovery mode.
2(d). Install SuHide into twrp boot mode.
3. Reboot your device normally.
4. Open SuHide find the app which you want to use in rooted device and press right button (front of that app) till it changes to slash(/?️) eye or pirated eye.
5. Now use that app.
Note:- Succesfully Tested on MOTO G4 PLUS with given versions (if lastest version does not work use this versions only).
Kindly Check This Thread https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567
Hi,
i have problems to get Magisk respectively Magisk Manager to work proberly.
Everytime i open Magisk Manager the changes notification appear and althought i disable supersu notification popup it appears everytime a app request root.
The settings i changed doesnt stick
I tried older Magisk and Manager version, reinstalled, cleared cache but nothing works.
This all was done on LOS14.1 and i also tried Omnirom 8.1 but there is exact same problem.
I trtied to get help with this in Magisk section (here, here,here) but it seems noone can help me with this.
This must be a Redmi Note 4 (mido) specific problem as with all my other devices there are no problems at all.
Hopefully someone have an idea whats the problem here.
der_Kief said:
Hi,
i have problems to get Magisk respectively Magisk Manager to work proberly.
Everytime i open Magisk Manager the changes notification appear and althought i disable supersu notification popup it appears everytime a app request root.
The settings i changed doesnt stick
I tried older Magisk and Manager version, reinstalled, cleared cache but nothing works.
This all was done on LOS14.1 and i also tried Omnirom 8.1 but there is exact same problem.
I trtied to get help with this in Magisk section (here, here,here) but it seems noone can help me with this.
This must be a Redmi Note 4 (mido) specific problem as with all my other devices there are no problems at all.
Hopefully someone have an idea whats the problem here.
Click to expand...
Click to collapse
I'm unable to understand what exactly do you mean?
Are you unable to use root? What rom do you use? Do you have super su previously installed, and did you flash magisk over it?
ok i will try to explain a little better
Magisk is working so far and apps are getting root.
But as far as i start Magisk Manager the "changes" notification appears every time (which should only displayed once after new install or update of Magisk Manager)
Also when i disable the supersu notification popup inside Magisk Manager it wont stick. Every time i open an app the popum informs that root is granted.
The only solution i have so far is to hide Magisk Manager with the option inside the Magisk Manager settings.
Its hard to describe and i hope its now understandable
Here posted some logs !
der_Kief said:
ok i will try to explain a little better
Magisk is working so far and apps are getting root.
But as far as i start Magisk Manager the "changes" notification appears every time (which should only displayed once after new install or update of Magisk Manager)
Also when i disable the supersu notification popup inside Magisk Manager it wont stick. Every time i open an app the popum informs that root is granted.
The only solution i have so far is to hide Magisk Manager with the option inside the Magisk Manager settings.
Its hard to describe and i hope its now understandable
Here posted some logs !
Click to expand...
Click to collapse
I see now. What magisk version u using? I'm on v16.0 and it works fine, even the changed settings work well
MyNameIsRage said:
I see now. What magisk version u using? I'm on v16.0 and it works fine, even the changed settings work well
Click to expand...
Click to collapse
Magisk v16 and Manager v5.6.1
But i tried older verions of Magisk and Manager but it doesnt help at all.
Also i reinstalled ROMs (LOS and Omni) tried different recoveries..... no go.
I have no idea ... on my other devices no problem at all.
I hope someone see an error in the logs.
The following lines doenst look as they should
W/SharedPreferencesImpl( 9451): java.io.FileNotFoundException: /data/user/0/com.topjohnwu.magisk/shared_prefs/com.topjohnwu.magisk_preferences.xml (Permission denied)
W/pool-1-thread-1( 9525): type=1400 audit(0.0:146): avc: denied { rename } for name="com.topjohnwu.magisk_preferences.xml" dev="mmcblk0p49" ino=1664194 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=0
These lines doesnt appear in the logs of my working devices but I compared the permission of that folder with one of my working devices but it looks OK.
Dude are you using Dual boot? Then this is expected
no i dont use Dual boot.
But maybe i did something wrong at Installation ?
Unlock Bootloader -> flash Recovery -> format Data and wipe -> flash ROM, GApps and Magisk
der_Kief said:
no i dont use Dual boot.
But maybe i did something wrong at Installation ?
Unlock Bootloader -> flash Recovery -> format Data and wipe -> flash ROM, GApps and Magisk
Click to expand...
Click to collapse
Your flash queue is right, but possibly you should try flashing magisk after one boot. (Just flash rom and gapps, reboot , set up device, and then boot to recovery and flash magisk)
then the Redmi Note 4 must be something special
With my other devices i made it exactly the same and there are no problems at all.
Maybe next time i flash new/update ROM i will try it ....