So, im new to rooting devices and stuff, but recently i tried to root my old samsung a50. At first it seemed like I succesfully rooted the phone, but then i found out magisk wasnt working correctly. I found out that zygisk was the problem, so i googled and tried some fixes. After a while I got stuck in a bootloop. The next day I got everything working again (including zygisk) by doing a full reset and trying again. Then, when I tried to add apps to the zygisk special list (or something like that i forgot what its called), i rebooted my phone because it said i would have to do that to make my changes work. After I did that everything has stopped working. Root checker doesnt even confirm that the phone is rooted at all and magisk, zygisk and ramdisk dont seem to be working either if i look at it in the magisk app.
Does anyone know if there is a way to fix this? Ive looked all over redit but couldnt find anything.
Btw i used these instructions:
https://forum.xda-developers.com/t/guide-root-unroot-rooting-unrooting-a505fn.4447651/#post-88239721
If screenshots are neccesairy let me know, but they will be in dutch so i figured it wouldnt really help.
Edit:
I kindoff fixed it. I went in to orangefox recovery and then rebooted trough that service selecting recovery. Now root checker does confirm the device is rooted and magisk seems to be working, but not completely. It still says that ramdisk is dissabled. Any advice on how to fix this? or does it even matter?
My A50 also says that Ramdisk is disabled and I haven't found a way to fix it, and since it's an A-only device it's really hard to flash Magisk. I hope you find a way to fix it
Related
I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday. All apps are working fine after the re-flash.
Anyone else have this?
unknown_owner said:
I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday.
Anyone else have this?
Click to expand...
Click to collapse
That is possible. I had the same issues. To get the ad-free host files in, I had to do it in recovery mode and push the files which is like having the nand lock. I try to do some programs that require root and it reboots the phone.
Hi, I'm super new to this I have no clue what I'm doing, but I did manage to follow the instructions of http://forum.xda-developers.com/gala...-t800-t3079488 and get my t800 rooted.
Until problem occurs, at http://techbeasts.com/2015/05/01/roo...-lollipop-502/ step 9 "Once it has booted up, check out the SuperSu application in the app drawer. If it asks you to update SU binary, update it." When I open supersu app it only ask me to follow someone on google+ but didn't mention anything about update, couldn't find an update option anywhere in the app either.
I ignored this potential problem and then downloaded rootvalidator, everything was green only busy box was yellow and SELinux was blue saying something enforcing, I don't have a screenshot but these 2 were the only one that's not green. I installed busybox free and got busybox in rootvalidator green (from yellow). Not sure if the enforcing part was an issue so I left it like that.
So I use this guide to root t800 is to use xmod, and XMOD actually have their own tutorial on how to root and install and get it to work etc. just didn't have one for this model. I think I made a huge mistake of following their guide after this one, and got mislead not knowing wtf is going on..
I installed xmod and found out it isn't working, I installed kingroot from within xmod app and when I opened kingroot it shows my tab is already rooted. So I was sure it's not a rooting problem, I then found out xmod isn't working because SE is enforcing and I followed the video guide (from xmod faq) on how to make xmod work on enforcing device. I downloaded Link2SD and clear data+ unistalled xmod. But I also clear and unistalled kingroot (and kinguser i think?) and another app that came along with kingroot when i got it (It was in chinese)...
After this I lost root access and when I check rootvalidator it show my device is not rooted anymore. When {I click on supersu it asks me to update normal or from twrp/cwm...
Everything seem to be a mess so I'd like some advice is it better for me just to restore everything back to factory settings and root the device again? Sorry for this long and noob post I'd really appreciate if someone can help me out. Thank you so much!
Edit: Hey Ashyx thanks for replying so fast, I can't reply due to not enough post.
Just to make sure, I just need to go back to download mode and use cf-autoroot-twrp-t800 with odin to root it again. (then it reboots)
After it reboot, turn off and go back to download mode again and install the tar you provided with odin similar to rooting it? Is there any specific options I need to tick or untick in odin?
Thanks again!!
Just reroot that's all you need do.
The same way you did it the first time.
For permissive mode. You need a kernel that allows it.
I have built a stock kernel that will allow you to set permissive mode:
https://www.androidfilehost.com/?fid=24052804347765648
Install with odin.
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for
Hey Good Morning folks.. I bought a new phone J6+ and I didn't care for warranty and I decided to void it and root my device. I updated my phone to the latest software from Samsung through Odin and everything went well. I downloaded Magisk Manager after that then pulled the boot image from the stock room I have using 7-zip and patched it then flashed it to my phone through Odin. As in such case it was supposed to work as it worked with all other Samsung devices I rooted.
After that I downloaded Solid Explorer and I tried to remove some apps from my /system/apps as a simple test to see if my root works. it was Youtube it wasn't a dangerous critical app. But then my phone hanged and restarted then I found Youtube is back.
I went to Magisk again and downloaded BusyBox from there and installed an app called "Uninstall System Apps" and I used it to remove Youtube also as a test it removed it and the restarted the phone flawlessly then I went to remove "Facebook" then restarted my phone then Gosh Youtube is back and also Facebook.
I found out if I try to modify anything in /system the phone will restart then undo what I've done.
what is the reason? is it Defex? is it RMM? is it Knox? is it DM-VERITY? I just wanna know what is wrong with it to see how I can fix it.
Edit:
Phone: SM-J610F/DS
Software Build: M1AJQ.J610FXXU1ASA3
Magisk version: 18.1
I keep reading other threads and posts. I can see there is a way using Ashyx Method https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
I just wanna know why it fails if I install Magisk with "Patched Boot method" only.