Develop Bugs

[Q] SuperSU not updating, etc

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.

root issue

Hi, hope someone here can help?
I recently rooted my N7100, using CF Auto root – great instructions, easy to follow, and it rooted perfectly
All was good, except that it would not of course, run SkyGo. After downloading voodoo and superuser, I managed to get the phone to temporarily disable root, but Sky Go still wouldn’t work. So, I un rooted, and Sky Go worked - and then re-rooted, with the aim of trying to temporarily disable root again.
Noooooow, my binary su counter has gone to 3, root checker says it’s not properly rooted, Sky Go won’t work because it says it IS rooted, Titanium Backup and Triangle Away won’t work because they say it’s not rooted – and I’m stuck!
Tried re-rooting yet again, via the same method, and it seems to work, but again, root checker says it’s not rooted ‘properly’, and no apps requiring root will work. Also, in spite of supersuer and superSU not being installed (as far as I can see anyway), superSU doesn’t get installed during the root process, as it did the first time I did it.
I seem to be stuck on some sort of root limbo – does anyone have any ideas?
Thanks for reading.

Try downloading SuperSU from market and check if it works

Well, feel sure I did actually do this and it wouldn't run, due to not having 'proper' root. Just downloaded it now though and what do you know, it worked! Thanks for the suggestion, it's appreciated. Just need to find some way to temporarily disable root now, to enable the running of Sky Go!

Try this
https://play.google.com/store/apps/details?id=com.marutian.quickunroot
Sent from my GT-N7100 using xda premium

Thanks for the suggestion. I installed it, but it didn't work. I'll continue looking, but thanks again anyway, for taking the time to reply.

[Q] GS3 update error and Superuser pro issues.

So, my sprint GS3 is rooted with SuperSu pro. The Android version that is on my phone is version 4.1.1 I never had a problem with the phone until one day it prompted me to upgrade the software and I accepted. The update was never successful. I have a picture attached that shows error message it gave. SuperSU pros' icon also doesn't show up anymore on my phone. My phone is still rooted because I can use Titanium back up pro. It has been acting up more and more ever since that first error message.
I've tried searching for similar problems on this website as well as on others but haven't found anything that's similar. I hope the picture helps and someone else who's experienced a similar problem can shed some light on mine because it's driving me crazy.

Have you verified Root, like with Root Checker ? It's Free in the Play Store. Have you tried to Update SU ?

It sounds like you were rooted and tried to get the 4.3 update. Luckily for you it didn't take. If you want 4.3, I would suggest you flash the Knox free version. Just follow the install instructions in the OP and it'll get you back rooted. If you want to stay on 4.1, try flashing super su update through cwm if it won't install from the play store.
Sent from my SPH-L710 using Tapatalk

[Q] Tried rooting using Towelroot and chainfire but no joy

Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled

tried another method
Also tried using the casual method but that also failed with the error "Unsupported device" here is the url for the log file:http://pastebin.com/vZRvYH3g
I followed the follwowing thread:
http://forum.xda-developers.com/showthread.php?t=2189536
amti366 said:
Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
Click to expand...
Click to collapse

After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.

DocHoliday77 said:
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
Click to expand...
Click to collapse
Hi Doc, I was able to follow one of your other treads at "http://forum.xda-developers.com/galaxy-s3-att/help/att-bricked-s3-help-please-t2817566/page2" and install TWRP. I think my issue was that the firmware had got upgraded to the NE4 and I was not flashing the correct bootloaders.
I do have one more question and I am not sure if it is a ROM related issue or a phone setting. I will understand if you think I should ask in the ROM thread. I flashed CM11 on the phone after installing TWRP and rooting with superSu. I noticed that the led buttons on the bottom of the phone are disabled(the back and the setting buttons) do you know if this is a changeable setting(pic attached)? I would hate to loose the screen-space at the bottom to the buttons and even though that's standard Kitkat layout I wont mind being able to use the phone led buttons to go back and change settings.
I installled the follwoing version of cm11: cm-11-20140805-SNAPSHOT-M9-d2lte.zip from (http://download.cyanogenmod.org/?device=d2lte)
Thanks for your help and guidance.
Matt

Im not sure about that one. I don't use CM so im not very familiar with all of its different settings. Someone else may have the answer for you though. If not, then ask in the rom thread like you mentioned.

[SM-J610F/DS] I wanna know the reason for which my root fails.

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.