I hope this is the right section I am posting in and I hope this works for you guys trying to be rooted while still having the option to enjoy the allshare cast dongle on the new MA7. (The dongle is pretty cool ) I have spent about 13-15 hours straight trying to figure things out. This process should take you less than 40 min.
First I must say the Note2toolkit is great but will always leave the system status "modified" and a binary count.
What I have tried and won't work:(notetoolkit options)
1)Using the notetoolkit I have tried simple root option without changing the recovery=Allshare Fail
2)Changed to TWRP recovery and Triangle away = Allshare Fail
3)Back to stock recovery and triangle away = Allsharet FAIL
4)Reflashed stock rom using TWRP and the Triangle away= Allshare FAIL
5)stock rom and stock recovery flashed by the kit= Allshare fail (I have no clue why it failed here and I was pretty mad because I didn't back up my data, and I never used a custom rom)
(basically the toolkit somehow changes something and the triangle away app (even paid version) will bring a high counter to always show counter as 1, causing the allcast not to work correctly)
What worked for me
I odin flash the stock recover/rom (non-toolkit), then I did the system update multi window update (not the MA7), Allcast working, then root using CF-ROOT METHOD, now I am rooted with status saying modified (allcast won't work). I installed Triangle away (paid version) and selected "system modified workaround". Rebooted and now I am rooted with allcast working. System status= NORMAL and Bootloader shows no sign of being tampered and every thing looks stock with root and allcast working
Now I wanted the MA7 update:
1) I downloaded OTA ROOT KEEPER
2) make sure SuperSU is updated!
3)In triangle away app I unselected "system modified workaround" (DO NOT REBOOT YET)
4)OPEN OTA rootkeeper, backup and unroot
5) download and install your update (if you need the promt again, just clear the google service framework data under all apps and then check for update)
6) the update will reboot the phone
7) after update I just went opened up the OTA root keeper app and clicked root. WIFI Tether works
8) I realized I didn't use ANY triangle away app's setting and the bootloader shows everything official and 0 count and the system status showing normal!!!!!!! So don't enable or even use triangle away's app after step 7.
Now I am on MA7, Rooted, not using triangle away, Bootloader shows everything as OFFICIAL with 0 count. If I need warranty, I am assuming I just have to remove SuperSu and that will be it, without having to restore anything
I hope this helps.
For those with data and the allcast not working and want it to work with stock rom:
1)just titanium backup everything (root if you haven't done so already)
2)Follow the steps above "what worked for me"
3)titanium restore
Related
On my Verizon Gnex before the OTA to 4.0.4 I was rooted but still on the stock ROM and I ran the Voodoo Rootkeeper to make it easy to get back root afterwards. Once I got the OTA I restored root and the existing programs I had been using still seemed to work, but I was no longer getting screen notifications when one of those apps was granted root. I also applied the few updates to superuser and it's now fully up to date.
Last night I went to the approved apps list in superuser and saw multiple entries for one of my apps, so I figured I'd delete them all and reauthorize it again, but now I never get a prompt to add it, it just fails.
So it appears that either the current version of superuser is hosed or not installed properly. Voodo indicated that root permissions aren't granted in its status screen, but gives no indication on how to fix this. So I'm wondering how I should fix this. Is there a way to uninstall/reinstall the superuser app easily or do I have to go back through some part of the rooting process over again, or should I wipe and flash all the way to stock and start over?
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.
OK, so I did something stupid.
I was running 4.1.2, Rooted with a Perseus Kernel until I got "ambitious" and downloaded 4.3.
Everything went really well and the device rebooted fine and is working really nice and fast.
But, of course, I lost root, and the binary counter indicated "1" which didn't worry me.
So anyway, a couple of hours I decided to try rooting again with the same process that I used before since I still have the Windows Partition on my Mac and that went well too. Took all of five minutes. Now, the Binary Counter reads '2'.
BUT comma... None of my rooted apps will work. I keep on getting the dialogue... "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
After downloading 4.3, I didn't enroll in "The School Of Hard KNOX" and didn't install it, or whatever it is that you have to do to activate it... the window came up, but I didn't go for it. I just bypassed it, and it's not running (At least it's not under the running apps column).
This might be connected, but I also got this message after rebooting earlier, having to do with Google Play Store.
"Samsung is continuously working to improve the security policy on your device. Make sure you update the Security Policy on yur device.
Make sure your device is protected by updating the Security Policy to the latest version from Samsung.
And then I got a message having to do with the "XPrivacy App".
I just uninstalled Titanium Backup and The Titanium Backup Pro key, and reinstalled from the Play store, but it still gives me the same no access message.
Custom Binary Download: Yes (2counts)
Current Binary: Custom
System Status: Custom.
This just happened when I booted.
SuoerSU
"There is no SU binary installed and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
Kinda stumped.
How to root Samsung galaxy Note-2 N7100 < Android 4.3 >
Hello bro ..
i have solution for you ..
Contact me . [email protected]
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.
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.