This is my first time rooting. I have a Samsung Galaxy Note 3, model SM-N900P. It's running Lollipop 5.0.
I downloaded Odin 3.09, Samsung KIES Captivate, and CWM Recovery. I followed instructions from an article on android.gs, called "How to Root Galaxy Note 3 N900 on Android 5.0 Lollipop using Odin".
I'm pretty sure it went wrong when I had to put the CWM recovery file into Odin. Beforehand, when I tried unzipping the CWM recovery file, I found the contents to be corrupted, so I assumed I wasn't supposed to unzip it. So i left the CWM file unzipped. It was called "n9005-cwm-recovery-6.0.4.7-kk(0125).tar".
So when I ran Odin i just selected that file, and Odin said it worked. My phone asked me if I wanted to root and I said yes. Everything seemed to have been working like the instructions said. And when my phone booted up, and I opened clean master, I found that I could now disable apps from auto-starting, a feature that requires root access. (I didn't actually use this newfound feature, so I'm not sure it actually works.)
But SuperSU wasn't installed, so I found it in the Google Play Store, and upon opening it, I was left with the message: "There is no SU binary installed and SuperSU cannot install it. This is a problem!" and the app closes if I dismisses the message. Also, I downloaded Root Checker, which told me I had not properly rooted. I uninstalled both these apps.
Am I just one missed step away from a complete root? Maybe I unplugged my phone from my computer too quickly? Or have I messed something up? How do I fix it? Do I just proceed to root again normally, or do I have to un-root somehow, or do I do a factory reset, etc? I don't know what I'm doing. If I've given too much information or too little, sorry haha.
pacificpacifist said:
This is my first time rooting. I have a Samsung Galaxy Note 3, model SM-N900P. It's running Lollipop 5.0.
I downloaded Odin 3.09, Samsung KIES Captivate, and CWM Recovery. I followed instructions from an article on android.gs, called "How to Root Galaxy Note 3 N900 on Android 5.0 Lollipop using Odin".
I'm pretty sure it went wrong when I had to put the CWM recovery file into Odin. Beforehand, when I tried unzipping the CWM recovery file, I found the contents to be corrupted, so I assumed I wasn't supposed to unzip it. So i left the CWM file unzipped. It was called "n9005-cwm-recovery-6.0.4.7-kk(0125).tar".
So when I ran Odin i just selected that file, and Odin said it worked. My phone asked me if I wanted to root and I said yes. Everything seemed to have been working like the instructions said. And when my phone booted up, and I opened clean master, I found that I could now disable apps from auto-starting, a feature that requires root access. (I didn't actually use this newfound feature, so I'm not sure it actually works.)
But SuperSU wasn't installed, so I found it in the Google Play Store, and upon opening it, I was left with the message: "There is no SU binary installed and SuperSU cannot install it. This is a problem!" and the app closes if I dismisses the message. Also, I downloaded Root Checker, which told me I had not properly rooted. I uninstalled both these apps.
Am I just one missed step away from a complete root? Maybe I unplugged my phone from my computer too quickly? Or have I messed something up? How do I fix it? Do I just proceed to root again normally, or do I have to un-root somehow, or do I do a factory reset, etc? I don't know what I'm doing. If I've given too much information or too little, sorry haha.
Click to expand...
Click to collapse
1. The custom recovery you installed isn't for your device. Use this ONE.
2. You should downgrade your device coz Cf-Auto-root only is working till android 4.4.4 (KTU84P.N900PVPUDNH7). And root it with this FILE via ODIN.
Joku1981 said:
1. The custom recovery you installed isn't for your device. Use this ONE.
2. You should downgrade your device coz Cf-Auto-root only is working till android 4.4.4 (KTU84P.N900PVPUDNH7). And root it with this FILE via ODIN.
Click to expand...
Click to collapse
So I can't do this on lollipop?
Related
Howdy,
I am stuck and not sure what to do at this point. I have rooted this phone in the past with no problems with TowelRoot and I do not think anything has changed. I had JasmineRom installed but then I mucked up my SafeStrap install so I had to restore with Odin.
This is what I have done:
1) Flashed phone with NC4 firmware from: http://forum.xda-developers.com/showthread.php?t=2524572
2) Used the HLTE_USA_VZW_32G.pit file as well
3) Let Odin complete until it reached "Pass" state.
4) Pulled battery (as phone was stuck at the VZW logo), and booted into recovery mode then did a factory reset.
5) Booted phone fully.
6) Installed TowelRoot, BusyBox, SuperSU. TowelRoot said it worked. Neither SuperSU nor BusyBox will get me anywhere. By this I mean BusyBox complains about permissions and SuperSU eventually gets to the Disable Knox prompt but fails to do so then closes out. Check Root says device is not rooted. SafeStrap also fails of course, reports no root and busybox is not installed.
7) I did a factor reset from System. Let this completed and repeated the steps in 7) but with the same results.
I looked at TowelRoot thread, while I have not taken any additional updates after restoring with Odin, I do see that the dev has left his project to work for Google and fix such exploits. However, looking at other threads looks like people are still rooting with success so not sure what to think or what to try at this point.
Happy to provide any additional information if requested.
Thanks!
I've been trying to root my GP using the KingRoot and Odin methods, but came out empty with both methods
Summarized attempt
- Installed the newest KingRoot apk into my phone and installed
- Gave me an "Could not find root but try anyways" error and processed
- Finished successfully and confirmed root with Root Checker
- Ran SuperSume Pro and it stalls
- Reset phone and it bricks (infinite T-Mobile opening loop)
- Factory rest using Odin and stock firmware (from samsung-firmware)
- Try using pre rooted firmware (CF Auto Root Fortuna3a and another firmware I found) after, but both failed during the Odin process
If anyone would like me to go into more detail about my attempt, help me through a process, or link me to another root solution I would greatly appreciate it
I don't have the same model of grand prime, but I'm pretty sure you could just flash supersu.zip then install supersu.
Maybe wait until somebody else can verify I'm right, but I'm pretty sure it works on other models. You can find it along with other info here in the forums.
Hope it helps!
Edit; reread your post and had an idea, how about using the kingroot apk to root, verify with root checker, then try supersu or Super User from the app store?
Doubt it could hurt, if root checker is saying you have root, then it'd be safe to deduce that it's the rights management app and not the root process itself that's the issue
hiphop8004 said:
I've been trying to root my GP using the KingRoot and Odin methods, but came out empty with both methods
Summarized attempt
- Installed the newest KingRoot apk into my phone and installed
- Gave me an "Could not find root but try anyways" error and processed
- Finished successfully and confirmed root with Root Checker
- Ran SuperSume Pro and it stalls
- Reset phone and it bricks (infinite T-Mobile opening loop)
- Factory rest using Odin and stock firmware (from samsung-firmware)
- Try using pre rooted firmware (CF Auto Root Fortuna3a and another firmware I found) after, but both failed during the Odin process
If anyone would like me to go into more detail about my attempt, help me through a process, or link me to another root solution I would greatly appreciate it
Click to expand...
Click to collapse
Here this is how I rooted my g530t http://forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476
I figured out it was the Google FRP Lock that was the cause of the problems lol, after turning on the OEM unlocking (found in the Developer options in settings) the root worked fine using the TrapKernel MD5 with Odin
Hello. New here.
I rooted my S7 G930A running Nougat 7.0 following this guide: https://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
I actually found the guide somewhere else, but these are the files and instructions I used.
Rooting worked with no issues, and my phone works fine. Now I am interested in unrooting the device because of applications that won't work due to the safety net API knowing the phone is rooted.
I have already tried many things. There is an unroot.bat that comes with the files downloaded in the guide, but running that doesn't seem to actually unroot. SuperSU is still installed, and applications still don't work. I have also tried deleting the files using the ES File Manager, but I can only locate one "su" file which will not delete, and the superuser.apk or supersu.apk files are nowhere to be found. When trying to full unroot using SuperSU, I get the error "Uninstall failed!" I have also tried going back to the stock firmware using odin, but odin fails to install that as well.
Are there any current ways of unrooting that I'm missing?
Any help is appreciated, thank you.
Also, if this helps my baseband version is G930AUCS4BQC2
Okay, so I think I solved my own issue here. I was using the modified version of odin to install the stock firmware. Used the official odin and went back to G930AUCU4BQA6.
I have an additional question now. Since it reset the phone, any application that I made a system application is no longer a system app now right? But if I re-root the device, make the same apps system apps, and then use odin to upgrade to G930AUCS4BQC2 again it will unroot and my apps will still be system apps?
Thanks
Crossbows said:
Okay, so I think I solved my own issue here. I was using the modified version of odin to install the stock firmware. Used the official odin and went back to G930AUCU4BQA6.
I have an additional question now. Since it reset the phone, any application that I made a system application is no longer a system app now right? But if I re-root the device, make the same apps system apps, and then use odin to upgrade to G930AUCS4BQC2 again it will unroot and my apps will still be system apps?
Thanks
Click to expand...
Click to collapse
If you flash any ODIN file, it will wipe the system partition and then replace it with the one in the package. There's no way to get rooted system changes to persist through an ODIN.
I just got this S5, baseband G900VVRU2AOI1. In the same developer rom I think @FancyPantsu posted about but I don't know if it's from the same source or the exact same phone model. It was flashed on odin, COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5.
It has CID 11 so I know the bootloader is locked but I'm trying to get around it as it seems from tutorials I'm reading that it's possible. I installed kingroot and it's rooted successfully according to rootcheck, busybox is also installed without problems. But the point where my phone won't follow the tutorials is that I can't seem to make a supersu user. When I open it and try to update the binary, and press normal recovery, it goes for like 30 seconds before saying it failed and I need to reboot. Which I've done over and over and can't get it to work. I've tried flashing a SuperSu zip, still no changes. I'm trying to install safestrap eventually, but when I do it goes to 100% quickly, says install successfull but never activates. I also installed selinuxmodechanger and made sure it's set to passive. There was another solution I saw, that involved Kingo Superuser and removing root in the settings, but it didn't have the permissions.
As I understand it so far, I'm stuck in this circle. Like safestrap requires su binary to install, su binary requires safestrap to install, and any way to get one of those two requires the other first. Is there anything I'm missing or should try? It'd be much appreciated!
anyone there?
G'day,
I have followed the instruction using the download on this page for SM-G900I without success. https://forum.xda-developers.com/showthread.php?t=2696537
I found another Telstra user who used the kltezt version, so I tried with the version from https://autoroot.chainfire.eu/ even though the build version is different. This time SuperSU asked to disable knox, I did so, verify with Root Checker, doesn't work. Reinstalled using Odin without auto reboot, SuperSU asked for New user or expert, I chose New User, nothing.
EDIT---
When using Root Checker it would ask for permission to verify, I would try and click button which would not work.
I have just uninstalled SuperSU and Root Checker worked. I have reinstalled SuperSU updated binary and restarted and now Root Checker fails.
Android: 6.0.1
AP: G900IDVU1CQD1
Any suggestions?
Samuel
G'day sir.
CF-Autoroot is the old method of rooting the S5 and it will fail in some cases because it is no longer updated. The current method of rooting the S5 is to use either the SuperSU zip from the SuperSU XDA thread or magisk from the Magisk thread. What's the difference? Magisk allows to hide root, superSU works better with some apps and with xposed.
Go to the TWRP website, locate the files for the G900F (klte) and download the latest version to your PC. Then flash the .tar file in ODIN under AP/PDA.
Immediately after flashing, you must reboot to recovery (hold power button, home button, volume up button) until you see "rebooting to recovery". Once in TWRP, flash the SuperSU or magisk zip then reboot.
All the best, Saber
Thanks for your reply. Though had to go do some hard Googling to fill in the gaps of the installation process, like adding the SuperSU zip to the memory card.
I was about to say it didn't work again, but then it clicked why I may not have been able to grant access in the past. I use the night overlay app "Twilight" and I know the system doesn't like it running when doing certain tasks and asks you to disable the overlay. I disabled Twilight and it worked. Double checked and it is definitely the problem. All that for probably nothing.
Now I can install apps to the external SD, well that's the plan anyway. I've had enough manually moving them over manually to make space.
Thanks once again for your assistance!
Samuel