Hello,
So as the forum discussion I have the AT&T S3 I747 - Initially I rooted the phone to be able to use it at as a wireless hotspot and everything worked great the method i used was galaxys3root .com (I cant post the actual link <10 posts)
What I thought was a notification OTA triggered me to opening superuser and doing an uninstall/permanent unroot to ensure i didn't brick my phone, well I was wrong about the notification feeling like an idiot i decided to go ahead a reroot the phone again.
I followed the same procedure as linked above this time with problems, I have no Superuser Icon in apps tray, under applications manager it appears but only gives me the option to "Uninstall Updates" and that all
Things I have tried
- installing both versions onto the phone Clockwork mod simply just sits there under "Installing Superuser" Chain version installs but appears to do nothing.
- Used odin to reflash the stock rom then tried the re root process again
- reinstalled the wifi app to see if working but no longer is
I am not looking for a custom rom I like the default one I have I just want the Superuser app to show up again, anyone know what I could do to fix this?
Thanks for all your help
Flash the rooted stock version with Odin
mrhaley30705 said:
Flash the rooted stock version with Odin
Click to expand...
Click to collapse
Thanks for your reply I seem to have got it solved. I downloaded a File Explorer Went into system/Apps found the SuperUser APK opened it, let it install updates and what not after done the app showed back in my apps drawer, installed my wifi mod and superuser granted permissions so everything is good
Questions and help issues go in Q&A and Help section
Thread moved
FNM
Related
Update 2: Root was still acting wonky. I was getting multiple requests per app and it wasn't remembering my preference even with the box checked. I tried to allow all but it just wouldn't work at all that way. So I went to update the binaries just to be sure and I had version 3.2 while the latest (and I'm assuming stable) version is only 3.1.1. So if anyone has the problems I did, UPDATE YOUR BINARIES! That fixed everything for me.
Update: I uninstalled the Superuser apk via ES File Explorer, reinstalled it from the Play Store, and just let the phone sit while I was browsing and looking for an answer and when I went back to it Superuser opened and my root was back. I'm not sure if what I did helped but if anyone else has this problem then I can only recommend what I did. If someone can explain what I did wrong or why I lost root, that would still be helpful. If this post needs to be deleted then the mods can do so, I left it in case anyone else runs into this and searches the forums for it.
I have the At&t ion and I managed to get root on ICS on my second try. I was happy about it and decided to start flashing some zips after installing CWM so I deodexed, rebooted, and then flashed one of the status bar tweaks. When I rebooted again Superuser would force close as soon as it opened with the message "Unfortunately Superuser has stopped working". I still have root access in ES File Explorer since I granted it before Superuser stopped working. I cannot however grant any new root permissions since Superuser won't open.
I'm willing to reflash GB and start from scratch again, I'd just like to know what the reason is (was it deodexing? Flashing the zip for the status bar? Or is this just something that can happen?) so I can avoid it the next time. I'm not too excited about having to redownload all my apps for the 3rd time (I was living without root on ICS but decided to go ahead and get it) so if there's a way around it I'd like to find it. Any help is appreciated. I'll try to reply as quickly as possible, thanks guys.
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 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.
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 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.