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!
Related
any one know the changelog this firmware? the changelist is very changed....i found here http://live.samsung-updates.com/index.php?device=SM-P605
p.s sorry for my english
Has anyone flashed this yet? I flashed it and it goes thru the entire installation process and the fails to complete the "write bla. bla". But it installs all the parts of the firmware. So I tried to boot it and it failed with an message saying that I should use Recovery mode in Kies bla. bla. I flashed it again thinking it might have been just a one time error but no, same thing again. It seemed like stock recovery stopped my device from trying to boot, so I flashed TWRP and rebooted. To my supprise the device went in to boot process and BOOTED!!! No issues, well stock keyboard kept chrashing, it runs just fine. SO I boot in to recovery and let TWRP install Super SU for root and boot. No messages from Knox what so ever!! Not when starting root apps, not when it asks for root access and not when Super SU prompt shows up asking me if I want to grant this app superuser rights. I have not frozen any Knox apps and Knox apps is installed. It`s been a while since I rooted a stock firmware but as I remember there was Knox alerts everytime when apps asked for root, untill Knox was deleted or froozen.
If the install fails for the rest of you, just flash a custom recovery and theres a big chance it will boot for you also. But thats when Odin completes the install of all parts and fails to complete. Would be nice to hear if someone have installed it with out issues.
nickwarn said:
Has anyone flashed this yet? I flashed it and it goes thru the entire installation process and the fails to complete the "write bla. bla". But it installs all the parts of the firmware. So I tried to boot it and it failed with an message saying that I should use Recovery mode in Kies bla. bla. I flashed it again thinking it might have been just a one time error but no, same thing again. It seemed like stock recovery stopped my device from trying to boot, so I flashed TWRP and rebooted. To my supprise the device went in to boot process and BOOTED!!! No issues, well stock keyboard kept chrashing, it runs just fine. SO I boot in to recovery and let TWRP install Super SU for root and boot. No messages from Knox what so ever!! Not when starting root apps, not when it asks for root access and not when Super SU prompt shows up asking me if I want to grant this app superuser rights. I have not frozen any Knox apps and Knox apps is installed. It`s been a while since I rooted a stock firmware but as I remember there was Knox alerts everytime when apps asked for root, untill Knox was deleted or froozen.
If the install fails for the rest of you, just flash a custom recovery and theres a big chance it will boot for you also. But thats when Odin completes the install of all parts and fails to complete. Would be nice to hear if someone have installed it with out issues.
Click to expand...
Click to collapse
could you give us a changelog (multiuser support ?) , multitouchscreen fixed ? ; ....
I've downloaded the B2 firmware from SamMobile (I tried first on your samsung update website but the flashing didn't work), the "Baltic" one with odin 3.09 and the flashing worked. I've only used it for a couple of minutes and the only difference that I can see is that the the OS runs smoother, less lag and no more wake up lag. I'm not saying the lag magically disappeared, it's just much less noticeable. But of course it's definitely worth flashing it if, like me, you couldn't stand how laggy the previous firmware was.
EDIT: nickwarn, could you please explain me how you rooted your P605 with the new firmware? I'd like to do the same (I've already installed TWRP btw). Thanks
EDIT 2: Never mind nickwarn, I re-read your post and understood that you simply booted TWRP and let it install SuperSU when it asked you to install it. Thanks anyway
I'm trying to migrate from 4.4.2 to at least 4.4.4 if not 5.0 while keeping root - all of this on a VZW S5. Every how-to I find says to install Safestrap as part of the process. I rooted with towelroot, SuperSU, and Root Checker is happy. The problem I'm having is Safestrap-KLTEVZW-NCG-3.75-B03 says it's doing the install, but the final state remains "Not Installed" and rebooting doesn't show the Safestrap splash screen. I have 4.4.2 NCG so I should be right with Safestrap but obviously that's not happening. Now what?
I tried B02 - ya never know... Now I know... no change. Feh.
ADDED:
Yes, I have BusyBox installed, and granted Safestrap SU status.
I re-installed Safestrap from Playstore after reinstalling NCG (after trying yet another attempt to carry root to at least 4.4.4) and still no joy. BusyBox Pro is installed, and Safestrap seems to think it did the installation, but it also says state: not installed. ???
Bump.
The problem remains with 4.4.4. Safestrap goes through all the motions but doesn't state the install really happened.
Sigh... installing BusyBox via Play Store isn't enough. It kinda helps to run the internal install process, too. Duhhhh... Anyway, end of problem.
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?
Hello everyone,
this is my first time posting on the XDA forums after doing a lot of research, so please bear with me if I've missed something painfully obvious. My issue I'm looking to get help with is my AT&T GS4 i337.
Here goes the problem, initially I had the FNJ4 (4.4.4) baseband and build number. I was really excited to try custom ROM's like CM11 or 12. I ended up reflashing the phone via odin with baseband and build number FNB1 with a rootable kernel (titled I337UCUFNB1_TWRootable_Full_Odin.tar 4.4.2). This successfully worked as did using TowelRoot (v3) to root. Since the reflash, I cannot seem to load CWM or TWRP much less access even the factory recovery mode on startup (it goes to the "unable to boot into normal mode" screen). And today, I was messing around with the "Disable Service" app and accidentally unchecked the box to turn off the service for SuperSu (even though I re-checked the box, I still lost root). And now I cant even run the tr.apk file to successfully root again - what I mean is the tr.apk installs and says I have root, but then when I check the root with root checker basic it says the phone has not been successfully rooted.
On a side note, I did find a flashable recovery .zip version of SuperSu (2.46) app to get the app back except now, shortly after startup, the app service turns itself off and I loose SuperSu again. I really don't know what to do.
I have tried messing with Terminal Emulator, Flashify, TWRP manager, ROM manager, ODIN and Titanium Backup to try and get SuperSU (to get root) and the factory recovery mode back (I also tried using Safetrap to install CWM and TWRP without success). The only program I haven't messed with is flashing with Heimdall. Oh yeah, I also tried using SELinux Mode Changer (changed mode to permissive) without any success.
I know this is getting super long, but my initial intent was just to be able to run CM11 or CM12 and customize the phone the way I want it. Any help would be greatly appreciated as I'm not sure how to prioritize these problems.
The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.
creepyncrawly said:
The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.
Click to expand...
Click to collapse
Got it. Thank you very much for responding so quickly! I'm new to this whole thing (the world of installing custom ROM's and the like) and I'm finding that so many details (Root/firmware/baseband/kernel/ROM compatibility) are so much more dependent on carrier and model number than I ever imagined. Thank you for pointing me in the right direction by helping me understand my limitations. Now its time to do a little more research.....
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?