Related
I Rooted a buddies DINC (SLCD) over the weekend using Unrevoked 3.1. The device is rooted (verified in ADB), and applications such as Root Explorer, and Drocap 2 work.
Here enters the problem. When I opened up Titanium backup it said "Could not find root". My next step was to hit the Problems button. As soon as Busybox updates there is an endless stream of root permission requests. Once you click allow about 20 times, they will stop. After you re open Titanium and click menu>Batch>Backup, again with the endless Superuser permission. I clicked allow at least 30 times by the time the backup reached 3 percent completion.
I figured maybe a quick fix permissions via ROM Manager might help. This time rom manager continued to error out.
NEXT, I figured I would install Busybox via the Busybox app on the market. I downloaded the stable version, Incredible rebooted, and once booted, I tried Ti Backup again......failed.
Next solution was to ADB push Busybox to the DINC in recovery. I got it to install, and even verified its existence with root explorer. I placed it in /System/xbin.
This fixed ROM manager, and I was able to fix permissions HOWEVER Titanium backup still CONSTANTLY asks for superuser permissions.
Also the last thing I can even think of adding to this is that I noticed that some of the root apps seem to ask for permission a little more than I am used to on my DINC. The logs are quite large.
Really have no idea why his is such a pain compared to mine. Again, like I said, he has a 2.2 stock rooted SLCD Incredible.
Any help would be appreciated.
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Only thing I havnt tried is wiping Dalvik. He wants to try flashing his first ROM without loosing all of his apps. But that may have to happen.
Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Wish it was all that easy. I have tried all of this lol. Titanium does not find busybix, so I doubt it is an SU issue. All the other root apps I have come across work. Like I said, I pushed Busybox, and it is now in system/xbin, but Ti still does not find it.
Similar issue
Hi, I have similar problem on Desire. I tried all as you and also no luck. I am going back to previous version where it worked.
I'm using SuperSU on the unlocked version of the M8. S-Off ARHD. I have rooted and everything, but I seem to be hacing issues with most apps not requesting SuperSU permissions. Greenify and FX File Explorer are the only 2 that have asked for them. So far, I can't run BusyBox, Auto-hide SoftKeys and the GSam root companion because none of them will request SU permissions.
I've attempted uninstalling and reinstalling through both the play store and TWRP recovery. Any other suggestions?
ryno9100 said:
I'm using SuperSU on the unlocked version of the M8. S-Off ARHD. I have rooted and everything, but I seem to be hacing issues with most apps not requesting SuperSU permissions. Greenify and FX File Explorer are the only 2 that have asked for them. So far, I can't run BusyBox, Auto-hide SoftKeys and the GSam root companion because none of them will request SU permissions.
I've attempted uninstalling and reinstalling through both the play store and TWRP recovery. Any other suggestions?
Click to expand...
Click to collapse
have you got it to allow all in settings
jaythenut said:
have you got it to allow all in settings
Click to expand...
Click to collapse
I don't see that option in there. I'm using the free version if that matters.
ryno9100 said:
I don't see that option in there. I'm using the free version if that matters.
Click to expand...
Click to collapse
Open app then it should be in settings allow all ,deny all and ask
jaythenut said:
Open app then it should be in settings allow all ,deny all and ask
Click to expand...
Click to collapse
It's set to prompt. Still not asking for permission in apps.
Edit:
I just set it to grant, and it still won't run BusyBox or any of the other apps I mentioned. But I have SU on FX and Greenif, and can confirm both of them work. What the heck?
ryno9100 said:
It's set to prompt. Still not asking for permission in apps.
Edit:
I just set it to grant, and it still won't run BusyBox or any of the other apps I mentioned. But I have SU on FX and Greenif, and can confirm both of them work. What the heck?
Click to expand...
Click to collapse
in aroma on ARHD theres 2 supersu opinions try the 2nd one instead just dirty flash
jaythenut said:
in aroma on ARHD theres 2 supersu opinions try the 2nd one instead just dirty flash
Click to expand...
Click to collapse
I'll have to try that one later. Apparently, my work internet blocks the mirror he gives on the original thread. :/
Not sure if i should start a new thread, but I am also having problems with SuperSu pro v2.14 (chainfire) Its not asking for permissions when trying to install the drivers for the viper4android app. been trying the for days. I have an htc one max (sprint) unlocked and rooted running 4.4.2, and root checked. busy box v1.22.1 installed, using twrp recovery v2.8.0.1. Other than that its all stock. SuperSu has granted permissions for other apps, but not viper4android. I have been browsing and trying many different ways to install, even found a zip file to try and flash, but the install failed. probably cause the zip file is old. I also tried to install the viper4android xhifi and it DID ask for superuser permissions. In the process of installing drivers, it asked to choose cpu. I chose CortexAx with NEON option and it failed install and told me to check root and busybox installation . Im not a master of this kind of stuff but not a newb either, and any help with this would be greatly appreciated.
Update: got the super user to give permissions, but still couldn't get viper4android to install drivers...
S-off?
HTC One M8
Hey all,
I realize this might need a wipe, but honestly if there is a fix it will save me a few hours headache of reloading and re-configuring everything.
Currently my phone will not root properly. I'm using the latest release MTC19V. I used the Nexus Root Toolkit to upgrade without wipe from the previous version like I normally do. After upgrading, I used the root function. There were no errors, however some applications are stating SU is not present.
SuperSU thinks everything is fine. Root requests are popping up normally.
BusyBox states "the su binary was not found on your phone", even after SuperSU pops up and I grant it permission. I assume BusyBox is no longer installed.
AdAway states "su binary could not be found" after I grant permission.
Greenify gets root access fine.
Xposed is working.
Also, after it is rooted, I no longer have access to DATA services over the 2G/3G/LTE networks, there is a "!" icon by the signal bars. WiFi works fine. If I flash back to stock without wipe, everything works normally.
I have tried:
- Unroot, flash back to stock MTC19T
- Removing all apps and installs of Xposed, SuperSU, BusyBox
- Using the uninstall and clean options in SuperSU
Going to keep messing around, but if anyone can point me in the right direction to avoid a full wipe, that would be fantastic.
Thanks.
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Tarv said:
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Click to expand...
Click to collapse
Ok, the regular ole busybox and adaway don't work with systemless root. There are additional things that need to be flashed. When I get to my computer I'll post a link to the files.
Sent from my SM-G930V using Tapatalk
---------- Post added at 05:00 PM ---------- Previous post was at 04:51 PM ----------
Flash the systemless hosts file from THIS link to get adaway working.
Try THIS busybox. If it doesnt work try THIS one.
Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?
Sent from my Nexus 6P using XDA Labs
Spikedude said:
I think the problem might be a corruption of the Busybox installation
Click to expand...
Click to collapse
Spikedude,
I think I was in the same boat. Before it stopped working, I too was seeing BusyBox 1.24.1 and not able to upgrade to 1.24.2. I also did an uninstall.
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
I used the other method of installing BusyBox as PiousInquisitor mentioned, and it installed properly, although it's using 1.24.1. BusyBox by Stericson still does not show it's installed.
I also think the installer from Stericson is busted and what caused this whole mess.
Tarv said:
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
Click to expand...
Click to collapse
Hey Tarv,
Thanks for the update. When you wiped the phone, what method did you use? Factory reset from within settings, or using NRT to flash stock and unroot with the "no wipe" option to preserve user data disabled?
Also, you might be right about the broken Stericson Busybox installer. Busybox on Rails looks like a good alternative. I've disabled the NRT option to install Busybox by Stericson when rooting, so I'll just install Busybox on Rails after the fact.
Sent from my Nexus 6P using XDA Labs
Spikedude said:
When you wiped the phone, what method did you use?
Click to expand...
Click to collapse
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Tarv said:
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Click to expand...
Click to collapse
Thanks Tarv,
Followed your procedure and am once again rooted and have data connectivity.
Unfortunately, installation of Busybox was not successful. Tried the BB on Rails version, but it only installs to /system/xbin, not /su/bin. As a result, the same root apps that didn't work previously still don't work. BB by Stericson pops up the success message, but then indicates BB is not installed.
So almost back to square one. I'll try going back to stock and rerooting using NRT again, but this time enable BB installation as part of the rooting process. Maybe...
UPDATE:
First, I may have spoken too soon about BB on Rails not working. I based that on root mode of ES File Explorer not working properly, but that might be an ES problem. Play Store reviews are also complaining about the ES root problem. So maybe installation of BB to /system on systemless root is ok?
I wiped and rebooted with NRT, and allowed it to install BB by Stericson. This worked fine, allowing installation of 1.24.2 of BB to the /su/xbin directory. Originally it indicated /su/bin, and that the "cat" file was missing (whatever), but after reinstalling to xbin a couple times and some restarts it all looks normal. Adaway works, full data connectivity works, etc. Trying to flip the root mode switch in ES pops up an error, but I can still explore root, so no big deal (I'm using Solid Explorer more anyway).
I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.
I see so many posts with users having login failures using Rooted devices and some solutions which to me are more complicated than needs be. This is my two cents worth and may be of benefit to the community.
Here we go.
When you Root your device it triggers security issues within the Snapchat app and login fails.
Easiest solution for me is to flash a custom recovery (TWRP) and then download most recent SuperSU zip if not already done.
One rooted the issue of login to Snapchat occurs. Simply open SuperSU application, select remove root from within the menu of SuperSU App. Root access is then lost. Open Snapchat and login as normal and the Application detects no Root and gains login access. Keep the Snapchat application logged in and then reboot to TWRP recovery and flash the downloaded SuperSU zip file which was downloaded earlier. Reboot the device and there you go, a rooted device and a working Snapchat on your device. Takes very little time and seems to do the trick for me every time.
This to me is reasonably hassle free and saves the hassle of issues that many users experience.
jody04c said:
I see so many posts with users having login failures using Rooted devices and some solutions which to me are more complicated than needs be. This is my two cents worth and may be of benefit to the community.
Here we go.
When you Root your device it triggers security issues within the Snapchat app and login fails.
Easiest solution for me is to flash a custom recovery (TWRP) and then download most recent SuperSU zip if not already done.
One rooted the issue of login to Snapchat occurs. Simply open SuperSU application, select remove root from within the menu of SuperSU App. Root access is then lost. Open Snapchat and login as normal and the Application detects no Root and gains login access. Keep the Snapchat application logged in and then reboot to TWRP recovery and flash the downloaded SuperSU zip file which was downloaded earlier. Reboot the device and there you go, a rooted device and a working Snapchat on your device. Takes very little time and seems to do the trick for me every time.
This to me is reasonably hassle free and saves the hassle of issues that many users experience.
Click to expand...
Click to collapse
Didn't work for me
Or just keep a titanium backup of app logged in and then just restore it, Everytime you flash new ROM
I don't use Snapchat, but did you try Magisk with Magisk's suhide?
emuandco said:
I don't use Snapchat, but did you try Magisk with Magisk's suhide?
Click to expand...
Click to collapse
I'm on OnePlus 3T and I use Magisk's suhide to fix snapchat connection issue Just download Magisk app and tick su hide !
0xelectron said:
Or just keep a titanium backup of app logged in and then just restore it, Everytime you flash new ROM
Click to expand...
Click to collapse
Sorry for the noob question. How are you making a backup with Titanium without root? I'm not able to use the app unless I have root. I've tried Helium, but Snapchat seems to have blocked apps from backing it up.
I'm using an SM-G930FD on Nougat, so I don't even have access to the xposed framework, yet.
5yL said:
Sorry for the noob question. How are you making a backup with Titanium without root? I'm not able to use the app unless I have root. I've tried Helium, but Snapchat seems to have blocked apps from backing it up.
I'm using an SM-G930FD on Nougat, so I don't even have access to the xposed framework, yet.
Click to expand...
Click to collapse
You need root. You should first login to snapchat app, then root, and take backup. Now, restore the backup everytime you flash new rom.
0xelectron said:
You need root. You should first login to snapchat app, then root, and take backup. Now, restore the backup everytime you flash new rom.
Click to expand...
Click to collapse
Well I can't root without wiping my phone. Using TWRP and wiping my phone is the only method for a G930FD on Nougat at the moment. I even have to wipe my phone just to install TWRP without root. So there is pretty much nothing that can be done. Xposed isn't on Nougat and Titanium backup won't work because I'm unable to obtain root without wiping.
5yL said:
Well I can't root without wiping my phone. Using TWRP and wiping my phone is the only method for a G930FD on Nougat at the moment. I even have to wipe my phone just to install TWRP without root. So there is pretty much nothing that can be done. Xposed isn't on Nougat and Titanium backup won't work because I'm unable to obtain root without wiping.
Click to expand...
Click to collapse
If you don't have root, you shouldn't have the problem with loging into Snapchat due to root.... am I missing something?
bidyut said:
If you don't have root, you shouldn't have the problem with loging into Snapchat due to root.... am I missing something?
Click to expand...
Click to collapse
I am rooted... There is no way for me to back up snapchat while rooted, because I have to reformat to root. Which wipes my data. Making it impossible for me to use titanium backup to create a backup of snapchat, the only thing I can back up is the log in screen, because I can't root without losing data.
5yL said:
I am rooted... There is no way for me to back up snapchat while rooted, because I have to reformat to root. Which wipes my data. Making it impossible for me to use titanium backup to create a backup of snapchat, the only thing I can back up is the log in screen, because I can't root without losing data.
Click to expand...
Click to collapse
Try Magisk.
5yL said:
I am rooted... There is no way for me to back up snapchat while rooted, because I have to reformat to root. Which wipes my data. Making it impossible for me to use titanium backup to create a backup of snapchat, the only thing I can back up is the log in screen, because I can't root without losing data.
Click to expand...
Click to collapse
Ah. I just waiting till it was time to flash a new update again, and started without root. Logged into Snapchat, rooted and then backed up by Titanium.
Last weekend I ended up using Magisk instead of SuperSU and that way I didn't have to restore Snapchat and could log in with a rooted phone.
5yL said:
I am rooted... There is no way for me to back up snapchat while rooted, because I have to reformat to root.
Click to expand...
Click to collapse
I'm confused with this. if you're rooted, why do you have to format to root again? Are you able to login to Snapchat?
If not, uninstall it. Try using magiskmanager and doing the hide feature before logging in. If you try activating anything after you open the app you going to run into problems.
Kamikaze_Hulk said:
I'm confused with this. if you're rooted, why do you have to format to root again? Are you able to login to Snapchat?
If not, uninstall it. Try using magiskmanager and doing the hide feature before logging in. If you try activating anything after you open the app you going to run into problems.
Click to expand...
Click to collapse
Sorry, I can be vague at times.
In order to obtain root on my hone (Galaxy S7 Duos) I need to reformat my device due to the way Samsung encrypts there new devices. If I don't reformat then my phone won't allow SuperSU to mount. Re-formatting the device allows me to mount SuperSU before the device encrypts itself.
I looked into Magisk, I've been using it for awhile (for the double speaker mod). Trying to use the Hide feature I get a pop-up saying "Not using MagiskSU ... It's not officially supported,". I tried logging into Snapchat after that but I still get the same problem
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
bidyut said:
Ah. I just waiting till it was time to flash a new update again, and started without root. Logged into Snapchat, rooted and then backed up by Titanium.
Last weekend I ended up using Magisk instead of SuperSU and that way I didn't have to restore Snapchat and could log in with a rooted phone.
Click to expand...
Click to collapse
What phone are you using? I'm using an S7 Duos, which requires the device to be reformatted before obtaining root, due to Samsung's encryption. Not sure if that encryption thing is just the stock ROM, I've download a few other ROMs so hopefully I don't get the same problems.
Can't log in to snapchat. Rooted s7. No Xposed. I have magik app. Can't find the tick to su hide. My Snapchat account is locked..I unlock it then it immediately locks again when trying to log in..
SimPRoBer20 said:
Can't log in to snapchat. Rooted s7. No Xposed. I have magik app. Can't find the tick to su hide. My Snapchat account is locked..I unlock it then it immediately locks again when trying to log in..
Click to expand...
Click to collapse
Try flashin Universal SafetyNet Fix Beta 5 and it will be ok with snapchat. Them go to the menu and you should see the Magisk hide option. Then find and check Snapchat to be hidden. Open the app and in theory you should be ok to log in.
https://www.youtube.com/watch?v=a-PtwtQFBWg
I made a video on how to increase your snap score. Hope you enjoy it!
AndroidFL said:
Try flashin Universal SafetyNet Fix Beta 5 and it will be ok with snapchat. Them go to the menu and you should see the Magisk hide option. Then find and check Snapchat to be hidden. Open the app and in theory you should be ok to log in.
I made a video on how to increase your snap score. Hope you enjoy it!
Click to expand...
Click to collapse
Thanks I'll give it a try!