Hello guys, I just flashed TWRP on my Samsung Galaxy E7 running Lollipop. I'm in need of superSu.zip (flashable) to flash from recovery, so finally I can root my device.
Please suggest me a stable flashable su.zip.
Thanks in advance.
Use Cf auto root and install supersu automaticly
??
hacker812c said:
Use Cf auto root and install supersu automaticly
����
Click to expand...
Click to collapse
Now that i have already installed twrp recovery so if i use cf auto root will it work?
I already tried cf auto root befor installing twrp but after reboot the root was gone now i get yellow heading saying "set warranty bit kernel" on power on.
Secondly, when i boot into recovery i get red msg saying "recovery not seandroid enforcing". What does that mean?
Thanks for reply
Related
Hello guys,
I need help My Samsung note 3 n9005 was rooted before and i flashed the stock rom on it and try to root it again. i was able to finish flashing CWM by using odin no problems encountered, but when i tried to install supersu by booting my phone to recovery mode it shows . recovery booting.. seandroid enforcing and after the phone reboots and boots to normal mode.
I already tried different version of Odin and CWM, also tried TWRP and Philztouch but still no luck.
I know i can access superuser by using CF auto root by cf auto root comes with default recovery and wasn't able to install custom roms via zip file.
i hope you all guys can help me out here.
TIA.
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.
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...
Hi everybody.
I have a Samsung Galaxy A5 (6) 2016 (SM-A510F) with android 6.0.1.
I tried to root with CF-Auto Root and did everything as supposed to. But when the phone reboot it says always recovery is not seandroid enforcing.
So I did the same procedure again with the ODIN always and I unchecked the AUTO Reboot. But now ODIN says with green letters RESET. Did i just reset my phone?
I flashed the same file. I followed the procedure to the letter as said in the CF-AutoRoot thread. But I can;t understand whats wrong. I always use to root my phones but was Sony not Samsung. :crying:
What can I do?
The phone now suppose to be 6.0.1 or 5 android version? If it reseted it fully i mean.
Plus my knox warranty void number is 1. So that means that the first time worked but i didnt know what to do after that message.
Is the Ashyx method [TWRP 3.0.2-1][ROOT] GALAXY A5(2016) - sm-a510 - UPDATE 5/4/2016 capable of rooting my phone now? Or i have to put the stock rom inside and after try to root?
Save me please! I hope i didnt brick it.
Thanks a lot guys. I hope for a quick response! xx
Odin repack install
CF-AutoRoot making installation because brick device.
install twrp
https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip download supersu stable flash it
sorry google translate
Recovery is not seandroid enforcing
Dreamer62 said:
Odin repack install
CF-AutoRoot making installation because brick device.
install twrp
https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip download supersu stable flash it
sorry google translate
Click to expand...
Click to collapse
hI
I HAVE THE SAME PROBLEM OM A7-2016 SM-A710M but also fail with twrp
Samsung galaxy a5 2016 SM-A10F
''Recovery is not Seandroid Enforcing. yep i ****ed up. Really need some help
i have Odin, i understand i need to flash it? with what file?:crying:
EDIT:A510F
First U should enable developer option and then oem unlocking enabled. Then flash cf auto root then it will boot otherwise install stock recovery then do the above it will work.
Sent from my SM-J700F using XDA-Developers mobile app
Dreamer62 said:
Odin repack install
CF-AutoRoot making installation because brick device.
install twrp
https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip download supersu stable flash it
sorry google translate
Click to expand...
Click to collapse
If your device is bricked and not getting it back with Odin, try out the smart switch from samsung, there youll have EMERGENCY RECUPERATION, which leaves your device as it was.
ElCros said:
If your device is bricked and not getting it back with Odin, try out the smart switch from samsung, there youll have EMERGENCY RECUPERATION, which leaves your device as it was.
Click to expand...
Click to collapse
The smart Switch requires the S/N but I don't have it anymore! Is there any way I can find it?
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