Database Develop

snapchat fail login after root?

Hey everybody I rooted my device this morning, and I was setting everything up again since it gets wiped during the process. So finally I come and try to login in to Snapchat and it says something similar to "log in has failed please try again later" anybody have this problem or a way to fix it? Thanks in advance!

Snapchat checks for root and purposely prevents you from logging in if it find it. If you rooted with SuperSU, try installing Chainfire's SUHide. Otherwise, if you rooted with Magisk, enable MagiskHide in Magisk Manager.

I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.

martinsavvy said:
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
Click to expand...
Click to collapse
so i just do the full unroot option, sign in, then just flash the SU again?

sakumaxp said:
so i just do the full unroot option, sign in, then just flash the SU again?
Click to expand...
Click to collapse
Yeah that's what works for me.

martinsavvy said:
Yeah that's what works for me.
Click to expand...
Click to collapse
OMG thank you so much that was so easy!!!!

magisk is better though because you can still use android pay and mobile banking applications.

If I throw on a custom ROM after wiping will I need to do this process again?

Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.

Anova's Origin said:
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Click to expand...
Click to collapse
I shouldnt brick if i have to loose root and reflash super SU when I'm running a rom right? Sorry for all the questions

Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.

Anova's Origin said:
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Click to expand...
Click to collapse
Yeah cos I would need to flash the ROM, then sign in to Snapchat, then go back to TWRP and flash super SU

Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you dirty flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. ROMs like OOS will either replace TWRP with stock recovery or trigger dm-verity if you don't root immediately after clean flashing.

Anova's Origin said:
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. You might trigger dm-verity if you clean flash a ROM like OOS without rooting before booting.
Click to expand...
Click to collapse
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?

sakumaxp said:
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
Click to expand...
Click to collapse
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.

Anova's Origin said:
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Click to expand...
Click to collapse
I'm on stock ROM, so I guess I can go into super su and loose root then download magisk and get it that way

Thanks mate, it took forever to find this solution, it worked!
I use SU and it was simple to "unroot" from within the SU# app
1. settings scroll down to the "cleanup" section, select full unroot, accept all the warning messages, the phone will reboot into recovery and then reboot the phone after it finishes. Your phone may cycle through the reboot process a couple of times
2. log back into your phone, then you can log into the Snapchat app.
3. now you can re-root your phone, if you want to.
Cheers.

EVA-L09 won't boot after updating Magisk

I opened my phone today and found that there was an update to magisk, so I downloaded it and let it flash. Now upon turning my phone on, it passes the "your device is now booting screen" and then reboots. After a few times I end up in eRecovery.
The boot loader is unlocked, I was rooted and had systemless xposed installed (the one that works as a magisk module), and was running the Bluewei 5.0 ROM.
I am still able to access TWRP, but I do not have access to a computer. I still have the install package for Bluewei 5.0 on the SD, so I was thinking maybe I could wipe the phone and install that?
I ran a magisk uninstall package but that failed, and I tried installing magisk 14.2 using a zip that was already on the SD. So far nothing is working.
Help? I don't want to lose this phone (parents will kill me)

xMrTROLLIPOPx said:
I opened my phone today and found that there was an update to magisk, so I downloaded it and let it flash. Now upon turning my phone on, it passes the "your device is now booting screen" and then reboots. After a few times I end up in eRecovery.
The boot loader is unlocked, I was rooted and had systemless xposed installed (the one that works as a magisk module), and was running the MagicRainbow v2 ROM.
I am still able to access TWRP, but I do not have access to a computer. I still have the install package for MagicRainbow v2 on the SD, so I was thinking maybe I could wipe the phone and install that?
I ran a magisk uninstall package but that failed, and I tried installing magisk 14.2 using a zip that was already on the SD. So far nothing is working.
Help? I don't want to lose this phone (parents will kill me)
Click to expand...
Click to collapse
Solution was published two days ago in MagicRainbow but v3 thread
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
See from there what you can do. But aim to upgrade to MR v3, it's really again an excellent ROM. Probably you could do a clean installation of v3 instead of trying to repair v2

zgfg said:
Solution was published two days ago in MagicRainbow but v3 thread
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
See from there what you can do. But aim to upgrade to MR v3, it's really again an excellent ROM. Probably you could do a clean installation of v3 instead of trying to repair v2
Click to expand...
Click to collapse
I just realised I was actually on Bluewei, not MagicRainbow. Does this still apply?

Magisk v15.2 not installing

Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....

Try installing it in recovery

I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.

Yes. It's happening to me too. Does it work if I flash this update with twrp?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.

After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.

Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.

I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.

I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o

hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?

madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )

Magisk bricks my phone

I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.

I've been having zero luck getting this to work. Does anyone have any ideas?

Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.

yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.

Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?

Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.

I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.

Stuck in Download mode bootloop after updating from v20.x to v21.x

Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.

n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there

Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?

@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk

If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.

Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.

I think it says Unsupported/Unknown image format

Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).

Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?

Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.

Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you

n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.

@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...

Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.

lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".

Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.

lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).

Thanks for the help guys, had to flash the ROM, now its working again.