Chainfire auto root FAILED Samsung Galaxy J3 SM-J320R4

[LeviathaninWaves]

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:

 

[FainterStreak]

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:

Yes please help

 

[marsb455]

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

 

[marsb455]

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:

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