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.
Related
OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
Hi sorry I am new here, I looked around and did not see an answer to this
I rooted my S3 yesterday using Kingo Android root and as far as I can tell everything worked properly (other apps detect that phone is rooted) but SuperSu is not working because Knox keeps on blocking it. I read a few fixes like just uninstalling SU and reinstalling via the play store but Kingo installed SuperSu as a system app so I cannot do this.
Do I have to reroot or is there an easy way to reinstall SuperSU so that knox is not in the way (all none of the ways to deactivate Knoxs from within the phone do not work because none of my root apps have superuser), I am a bit of a noob when it comes to cell phones.
An suggestions? Also I am looking to keep the data that is already on the phone
EDIT: I got it working
For anyone else having this issue I went to chainfire's website and downloaded the newest version of SuperSU
I opened the Zip found the apk (found in the common folder) and uploaded it to my phone.
Using the default filemanager I opened and installed the apk.
Since it is a higher version then the one in the store it let me update the original failed SU install.
Upon starting SU it updated the binaries and also disabled knox.
Just tried this way and it worked for me thanks. I had same issues there was no option to update from store and Knox kept stopping such..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.
Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt
Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt
I'm also interested on this. Thanks for your efforts
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)
Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.
I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.
I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)
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.