Help rooting cricket grand prime, sm-g530az - Galaxy Grand Prime Q&A, Help & Troubleshooting

I rooted through kingroot and when my phone turns off and I try to boot it back up I get kernel is not seandroid enforcing and then I get a message telling me to take it to cricket and they'll fix it, well I factory restored it but how can I prevent that and still have it rooted? I tried rooting 2 times and had to factory reset it each time. Is there anyway around this?

Flash this boot img. With flashify after rooting with kingroot
http://www.mediafire.com/?2fk19cadccq0xd7

What version of firmware are you, I can't get king root to work

Do you have twrp? You can get root with supersu flashable zip via twrp

Related

[Q] galaxy sm-g900f root issue

Ok so i tried to root my s5 with odin using cf auto root, odin fined but then i my phone would no reboot it said RECOVERY IS NOT SEANDROID ENFORCING set warranty bit.
I could not get the phone to reboot at all so i went back to odin and flashed cwm recovery and now the phone boots up but i have no root access and cwm recovery is not installed!
I tried to repeat the process a few times and still have the same issues!
Someone please call me an idiot and tell me what i am doing wrong?
Thanks.

Troubles installing custom recovery on Note 4 910G

I have a Note 4 - 910G (India) currently running 5.0.1
I have managed to root the device. I can confirm that I have root access with an app like root checker. And yes, I've managed to trip Knox. At the custom boot screen, it shows Knox status as 0x1 (4).
My problem is that I can't install TWRP or any other custom recovery. I have followed the usual steps to install a custom recovery with flashify, TWRP installer and adb commands. Each time I try, the device reboots into odin mode (high speed) mode only. I then have to flash a custom recovery with Odin and the device reboots. However, even then.. if I try to boot to a bootloader, it still goes into the odin mode.
Is my device completely borked? Can I still install TWRP and then CM12.x on the device?
Any help/pointers would be appreciated.
I too have a note 4 sm-n910G. I think ur TWRP file is corrupted or you got the wrong file. It should be easy to get custom recovery. I rooted my Note 4 using CF auto root and it had CWM recovery which i tried to flash in Odin but it wasnt working. So i changed to TWRP 2.8.1.0 and it worked perfectly. Maybe try changing the TWRP file, or use a different one like CWM or philz recovery. Good luck...

Unrootable Galaxy S4?

I bought a new S4 (GT-I9505) recently and have found it impossible to root.
I've tried the following methods:
Philz TouchWiz (various versions)
TWRP rooting
CF AutoRoot
Whatever I try, the flashing via Odin works, I can usually reboot into recovery and root it, and then the next time the phone reboots it's back to the stock recovery and root is gone.
Has anyone encountered this problem, and/or does anyone have ideas on how to resolve this? I've effectively got a new phone lying around that I can't use because I can't root it.
Thanks,
WA
When you root the phone, are you able to boot and have root access? If so, try that then download the TWRP Manager and flash TWRP using that app. See if that sticks on reboot.
Try this: uncheck everything in Odin except f.reset time. Copy supersu to the phone, flash twrp, when you see the word reset in the status window, remove USB cable, remove battery, boot into twrp, flash supersu, reboot.

[Help!] Tried downloading TWRP, went into Secure Fail: Recovery

I was trying to download TWRP so I could install Xposed framework and it went into Secure FAil: Recovery, where it just looped an error. I used Odin, verizon firmware, and a PIt file (from a guide on this forum) and it's back to right before I rooted it today. I rooted it again, but I don't know what to do...
Just rooted today with droidyemen's 1 click lollipop root. It worked. I installed SuperSU, titanium back up. This is everything I know about rooting. Someone did it for me before on my old Note 3, so I'm learning everything as I go. Sooo much info. I don't know what supersu or titanium does, but I know I needed it.
Verizon phones are locked out by bootloader. No chance for any TWRP or AOSP ROM for you I fear

Chainfire auto root FAILED Samsung Galaxy J3 SM-J320R4

Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
Yes please help
not sure what I did differently, but I seem to have root now by using Chainfires AutoRoot for my Samsung Galaxy J3 SM-J320R4. SuperSu is installed and working
LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
It took forever to reboot. apparently the kernel was trying to hang. Ive still to get TWRP recovery to load, but we were given a big hint. I am crunching files right now, but my phone says it"s rooted, and I'll check more later.
---------- Post added at 01:53 AM ---------- Previous post was at 01:49 AM ----------
Phone is working

Categories

Resources