yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] samung frp removal:
SRS And Kingo Root Never Work on Bootloader Locked Phones Also Never Can Root higher than 5.1 android version phones...! in 6.0.1 all root software is failed..! if anyone want brick the phone they can use that useless root tools..!

for samsung as i know samsung made a special Firemware Which Called Enginire Firemware..! That Make Enable Permmison Of Root..! without Triping any Knox Or Void Warrenty..! All is safe If you use the File..!

yeah galaxy express j120a Enginire Root Kernal Safe Knox Is Ready..! Without Tripping Knox Also No Warrenty Void..!

100% Tested in Las Firemware Update Till april 2017
[Android Q&A, Help & Troubleshooting] N4cr2k:
* daemon not running. starting it now on port 5037 *

* daemon started successfully *

D:\platform-tools-latest-windows>adb shell mount -o rw,remount /system

mount: Operation not permitted

D:\platform-tools-latest-windows>adb shell mount -o rw,remount rootfs /

mount: Operation not permitted

D:\platform-tools-latest-windows>adb push SuperSU-v2.74-2.img /data/su.img

adb: error: cannot stat 'SuperSU-v2.74-2.img': No such file or directory

D:\platform-tools-latest-windows>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh

adb: error: cannot stat 'launch_daemonsu.sh': No such file or directory

D:\platform-tools-latest-windows>adb install -r SuperSU-v2.74-2.apk

Invalid APK file: SuperSU-v2.74-2.apk

D:\platform-tools-latest-windows>adb shell 0<supersu.cmds

The system cannot find the file specified.

shell@j1xlteatt:/ $ whoami

shell

shell@j1xlteatt:/ $ getenforce

Permissive

---------- Post added at 10:09 PM ---------- Previous post was at 09:18 PM ----------

repacked recovery

fail

secure check fail : (recovery)
[Android Q&A, Help & Troubleshooting] ashyx:
Has anyone got any idea what these random ramblings are about?

I expected the repacked image to fail now that you've stated sboot wouldn't flash.

I thought you'd said it had flashed OK.

At least it's a positive that the kernel is booting in permissive mode. This should at least mean it shouldn't block root.

Having said that it all depends on whether the bootloader will allow a modified pre-rooted image to flash?

In my experience on locked att devices, no.

What is your current firmware build?
[Android Q&A, Help & Troubleshooting] emilyrugburn:
I think that guy implied he could flash SBOOT. I was the one who couldn't flash SBOOT. Just to throw this out there, but KNOX/whatever security stuff kept trying to revert the boot.img for me. I had to disable it all with package disabler pro to get it to stick. At least thats what it seemed... it would pop up saying unauthorized changes blah blah and reboot into recovery and do something.
[Android Q&A, Help & Troubleshooting] ashyx:
That warning is simply because of the permissive kernel. It can't revert anything. Just disable 'security log agent' to get rid.

What is your current firmware build?

Has anyone yet managed to flash sboot?

Is anyone still running the PC1 firmware?

I guess the next step is to pre-root the system.img and we can see if it flashes.

Unlikely though because the bootloader is still locked.
[Android Q&A, Help & Troubleshooting] N4cr2k:
I seem to be able to flash sboot fine.

here is my build info:

D:\platform-tools-latest-windows>adb shell getprop | find /i "build"

[ro.bootimage.build.date]: [Tue Mar 22 11:31:54 KST 2016]

[ro.bootimage.build.date.utc]: [1458613914]

[ro.bootimage.build.fingerprint]: [samsung/j1xlteuc/j1xlteatt:6.0.1/MMB29K/FA60_J120AUCU1APC1:user/test-keys]

[ro.build.PDA]: [J120AUCU1APC8]

[ro.build.changelist]: [7662162]

[ro.build.characteristics]: [att]

[ro.build.date]: [Wed Mar 30 22:36:46 KST 2016]

[ro.build.date.utc]: [1459345006]

[ro.build.description]: [j1xlteuc-user 6.0.1 MMB29K J120AUCU1APC8 release-keys]

[ro.build.display.id]: [MMB29K.J120AUCU1APC8]

[ro.build.fingerprint]: [samsung/j1xlteuc/j1xlteatt:6.0.1/MMB29K/J120AUCU1APC8:user/release-keys]

[ro.build.flavor]: [j1xlteuc-user]

[ro.build.hidden_ver]: [J120AUCU1APC8]

[ro.build.host]: [SWHC3815]

[ro.build.id]: [MMB29K]

[ro.build.product]: [j1xlteatt]

[ro.build.scafe.cream]: [white]

[ro.build.scafe.shot]: [single]

[ro.build.scafe.size]: [short]

[ro.build.scafe.version]: [2016A]

[ro.build.selinux]: [1]

[ro.build.tags]: [release-keys]

[ro.build.type]: [user]

[ro.build.user]: [dpi]

[ro.build.version.all_codenames]: [REL]

[ro.build.version.base_os]: []

[ro.build.version.codename]: [REL]

[ro.build.version.incremental]: [J120AUCU1APC8]

[ro.build.version.preview_sdk]: [0]

[ro.build.version.release]: [6.0.1]

[ro.build.version.sdk]: [23]

[ro.build.version.sdl]: [2301]

[ro.build.version.security_patch]: [2016-04-02]
[Android Q&A, Help & Troubleshooting] ashyx:
So with sboot flashed is it still not possible to flash the repacked recovery?
[Android Q&A, Help & Troubleshooting] N4cr2k:
That is correct. This is with SBoot flashed.

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> recovery.img

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

at this point the phone shows

secure check fail : (recovery)

I have to pull the battery.

The stock recovery does flash fine.
[Android Q&A, Help & Troubleshooting] ashyx:
Bummer, was hoping the engineering sboot wouldn't be so picky!

I'll try patching the headers.
[Android Q&A, Help & Troubleshooting] ashyx:
repacked system image

Ok Ive repacked the stock system image, no modifications yet. No point rooting the system image until we find out if it can be flashed.

APC8_system.zip

.
[Android Q&A, Help & Troubleshooting] MRA85k_ARMv7L-LG-k371:
My version is like qb1

Revo.3

Should I not flash that system image?
[Android Q&A, Help & Troubleshooting] N4cr2k:
Didn't work.

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> system.img

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

secure check fail : (system)
[Android Q&A, Help & Troubleshooting] ashyx:
As expected, still can't flash unsigned images. :rolleyes:

I take it OEM UNLOCK is enabled in developer settings?

Some news, I have been helping out with the J320a and just been informed by someone that they have managed to get root using the engineering boot on that device.

Basically they tried Kingroot after flashing the eng boot which worked then converted to SuperSU with SuperSUME.

https://xdaforums.com/android/help/root-samsung-galaxy-express-prime-t3378684/page15
[Android Q&A, Help & Troubleshooting] N4cr2k:
That might of worked. I'll get a chance to test more later. It said root was successful. I tried to open adb shell and su but the phone hung.
[Android Q&A, Help & Troubleshooting] ashyx:
If it said success it likely worked.

Try one of the root checkers from play or simply try an app that needs root.
[Android Q&A, Help & Troubleshooting] N4cr2k:
Reboot fixed it. Looks like its working. Need to test actual root functionality yet.

D:\platform-tools-latest-windows>adb shell

shell@j1xlteatt:/ $ whoami

shell

shell@j1xlteatt:/ $ su

root@j1xlteatt:/ # whoami

root

root@j1xlteatt:/ #
[Android Q&A, Help & Troubleshooting] ashyx:
Yep defo working!

Are you converting to supersu so you can use flashfire?

---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------

I'll just post this here for anyone else.

Instructions to gain root:

1.Flash Eng boot with odin:

ENG_BOOT_J120A_PG1

2. Install and run Kingroot:

https://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

3. Install and run SuperSU me (not required) :

https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA

4. Please post your success.

.
[Android Q&A, Help & Troubleshooting] N4cr2k:
Yes.
[Android Q&A, Help & Troubleshooting] ViralThread:
So am I to understand that if I follow the above procedure on my box stock sm-j120a with Android 6.0.1 I will have root?

I just picked up another one yesterday NIB.
[Android Q&A, Help & Troubleshooting] ashyx:
Yes.
[Android Q&A, Help & Troubleshooting] ViralThread:
Most excellent.

I heard KingRoot was spotty. Do I remove that after I install Chainfires app or just leave it where it sits and ignore it?

Have they cleaned up their act?
[Android Q&A, Help & Troubleshooting] The192:
yes.. I did it also followed your instructions..

there seems to be some sort of security notice that keeps popping up ...

basically saying , "Hey... you weren't supposed to do that, take it back"". haha
[Android Q&A, Help & Troubleshooting] Jack_Rosen:
Which odin am I supposed to be using?
[Android Q&A, Help & Troubleshooting] jonpjingleheimler:
I used the latest Odin. I heard any would do. I have a rooted sm-j320a. hoping more will use the engineering boot ashyx posted and this phone can get closer to getting a custom rom.
[Android Q&A, Help & Troubleshooting] ashyx:
Disable or remove 'security log agent'

---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------

You should be fine removing it after installing supersu.
[Android Q&A, Help & Troubleshooting] ViralThread:
Very exciting will be trying this later when I get home. Will update. Tyvm
[Android Q&A, Help & Troubleshooting] ViralThread:
Rooted, but no Chainfire

Here is a summary of an arduous process resulting in a semi-optimal solution. To be clear, rooting the phone took little time at all. I've been wrestling with Chainfire's SuperSU and KingRoot for a few hours now.

As per instructions, I downloaded the files, fired up Odin on the Windoze laptop, tethered up the phone and pushed the new bootloader. Then I installed Kingroot on the phone and ran it. The phone was now rooted via rootchecker.

After a reboot, root persisted so I installed TitaniumBU, and made an adjustment to the build.prop because the phone wasn't keeping my wireless passwords across reboots anymore. This post here seemed to fix that issue.

Changes persist, so the phone is clearly rooted. But only with Kingroot. I cannot get SuperSU installed, because it whines about Kingroot being installed, Kingroot cannot be uninstalled as it has integrated itself into the system and only has a disable feature, disabling Kingroot breaks SuperSU and discontinues root access to the phone.

Suggestions welcome. Will update as I test the phone further. Plan to strip the bloat, install some apps, tweaks, etc.

All in all, super props to all involved. Excellent work, as always. :good:
[Android Q&A, Help & Troubleshooting] Jack_Rosen:
Did you try Super-SuMe?
[Android Q&A, Help & Troubleshooting] ashyx:
As posted above you seem to have ignored step 3.

You cannot install SuperSU with kingroot. Kingroot protects itself and cannot be replaced by simply installing supersu.

To replace kingroot you need to run SuperSU me.

Lastly you cannot uninstall kingroot by using application manager due to its protection mechanism.

It has its own uninstaller in its settings.
[Android Q&A, Help & Troubleshooting] MRA85k_ARMv7L-LG-k371:
Can OP copy and paste and make completed?
[Android Q&A, Help & Troubleshooting] MRA85k_ARMv7L-LG-k371:
It works... super awesome. Thank you guys. Now some editing.
[Android Q&A, Help & Troubleshooting] ViralThread:
Ok so a few brief Qs if you don't mind, mostly for completeness, I like completeness.

I mostly wanted root to clean up the mess and make a few tweaks to the build.prop, etc.

If I make those changes, then uninstall KingRoot and reset the phone will I be good to go?

Secondarily, should I choose to revert the phone back to stock for whatever reason I can simply use Odin to re flash the stock image and it will be as it was before I customized it, yes?

Thank you for your patience, I'm still merely dabbling in the phone rooting and tweaking dept.

Thanks again for the wonderful efforts.
[Android Q&A, Help & Troubleshooting] nook'r:
Debloated ROM

1st of all, This is really great news about rooting the J120A.

was looking online for a system apps remover but nothing is showing great result. then i came through this site that has ROMs for the J120A.

https://firmwarefile.com/samsung-sm-j120a

Is there a way to de-bloat or trim the rom from all the extra ATT apps that are not needed? and use ODIN to flash the trimmed ROM?
[Android Q&A, Help & Troubleshooting] ViralThread:
I used TitaniumBU to remove the bloat ware and AT&T apps. Some apps seemed stubborn and returned after a reboot but a second pass seemed to keep them from returning.
[Android Q&A, Help & Troubleshooting] ashyx:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB
[Android Q&A, Help & Troubleshooting] shirleys143:
OK, went round the world and bricked the phone and cannot flash the stock system with Odin(3.12 & PrinceComly). Also tried firmware link nook'r also found last night but to no avail. Tonight, found the system image you posted and tried that but still no success.

I tried both bootloaders, the stock and the engineering. Both allow me to get to fastboot and recovery. Tried factory reset and wiped cache.

With the Odin system flash, I get the message "SECURE CHECK FAIL : (SYSTEM)" on the phone. Am I missing a PIT file?

Tried Kies3 and SmartSwitch to do emergency recovery but phone not recognized. Uninstalled both and tried Odin flash several times and reboot several times. Here is the Odin message.

<ID:0/006> Added!!

<ID:0/006> Odin engine v(ID:3.1203)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> SingleDownload.

<ID:0/006> system.img

<ID:0/006> FAIL!

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

What am I doing wrong? Any suggestions?

Successes: Was able to flash the engineering bootloader, root with Kingroot, Super-Sume, BusyBox, SuperSU, Titanium Backup, Root Check and AppQuarentine. Quirk was I used a mid 2016 Kingroot as Super-Sume appears to have less problems with that. Also updated SuperSU and BusyBox. AppQuarentine to freeze KNOX and originally Kingroot. Stopped security popup. Bricked the phone or got into a bootloop when editing the build.prop to remember wifi passwords. Think I used the wrong editor or saved under wrong format. Otherwise, things appear to work. However could not read/see certain folders on phone SD in Windows Explorer.
[Android Q&A, Help & Troubleshooting] The192:
thanks for the update.

I will do it now
[Android Q&A, Help & Troubleshooting] ashyx:
So do you still need the firmware or not?
[Android Q&A, Help & Troubleshooting] shirleys143:
Yes please. The firmware you linked previously gave an error with both versions of Odin. I am not sure why.

I also would like to thank your very much for getting root for this phone. A phone without root is useless IMHO.
[Android Q&A, Help & Troubleshooting] ashyx:
It doesnt work because the bootloader rejects it as its an unsigned image.

https://firmwarefile.com/samsung-sm-j120a
[Android Q&A, Help & Troubleshooting] shirleys143:
Thanks but I think I tried these two firmware a couple nights ago and both did not get as far as the one you posted.. They did now even display a progress bar on the phone. I will try again now.
[Android Q&A, Help & Troubleshooting] ashyx:
One of them should work depending on which revision firmware your device was running as they are recent firmwares.

One is revision 1 - APC8 and the other is revision 2 -APJ2.

Revision 2 should flash on any device.
[Android Q&A, Help & Troubleshooting] shirleys143:
Thanks!!! It worked.

I think I should summarize for others. My original firmware is PC8. I used another computer. I used the link to get a new copy of ODIN. I had issue with Winrar so again I used the default windows unzipper. With the downloaded PC8, I got the following for the system.

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1205)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> boot.img

<ID:0/005> recovery.img

<ID:0/005> system.img

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

SYSTEM REV. CHECK FAIL. DEVICE:1, BINARY:0

For the bootloader, I got

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin engine v(ID:3.1205)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> sboot.bin

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

SW REV. CHECK FAIL. DEVICE:2, BINARY:1

I then used the PJ2 and was able to flash the system only. That was all I needed and the phone now boots. So I am not sure if new ODIN or new PC helped solve the problem. Tomorrow, I will go through the root process again.

Thanks a million ashyx!

---------- Post added at 04:36 AM ---------- Previous post was at 04:31 AM ----------

ashyx, would you have any idea on how to carrier subsidy unlock the phone.? ATT basically would not unlock my phone because my sim did not have an exclusive relationship with the phone for 6 month. I had used my sim in multiple phones. A commercial unlocker would charge more than what I paid for the phone. Thanks. again in advance.
[Android Q&A, Help & Troubleshooting] ashyx:
Unfortunately not, but I would still keep looking about for a cheaper unlock code, they are available.

Failing that take it to a phone shop. They have the equipment to unlock it there and then with something like Z3X box.

By the way is your device a j320a or j320az?

I'm a little confused as to why the firmware failed to fully flash as its correct for your device.
[Android Q&A, Help & Troubleshooting] shirleys143:
Thanks. Will keep looking for another unlock solution. I have had other Gophones unlocked by ATT but those phones did have a SIM with an exclusive relationship with the unlocked phone.

I have a J120a straight from ATT. I am not sure why PC8 would not flash but PJ2 would. It could be the new computer I used or the new version of ODIN from the link at the site. I will probably have time to narrow that down later as I am having other problems. Other XDA posts have pointed to OEM cables, computer, and 7Zip. WinRAR did not like the images so I used the default windows unzipping.

I did an OTA at the end of last year or at the begining of this year. Today, there appears to be another OTA. I might wait as that might introduce other issues.

Just an update, the firmware is working and booting and rooting. However, on this second round, Super-sume is having problem maintaining root. Like before Super-sume removes Kingroot, crashes and but root is lost. Thanks again.
[Android Q&A, Help & Troubleshooting] ashyx:
Honestly I would just take it to a phone shop, it doesn't cost much and is a simple process done there and then.

If supersume is having issues with kingroot use an earlier version of Kingroot. Someone else solved a similar issue this way.
[Android Q&A, Help & Troubleshooting] ViralThread:
So me device is APC8 is it worth it to move to revision J2 ?
[Android Q&A, Help & Troubleshooting] ashyx:
Its up to you,but once upgraded there is no going back and i cant guarantee root.
[Android Q&A, Help & Troubleshooting] ViralThread:
Understood. Ty
[Android Q&A, Help & Troubleshooting] shirleys143:
Thanks, will ask around the shops. As for Super-sume, tis was I that used an earlier version of Kingroot. I have all the files and screen captures from the successsful first round. For some reason, I am doing something differently this time. I will start fresh later on if I can get the SIM unlocked.

Just to clarify, your directions on the SecurityLogAgent (freeze) and the ro.securestorage.support=true to false (build.prop) works.

I am going to also freeze ATT updater and Knox.
[Android Q&A, Help & Troubleshooting] ashyx:
If you download bk package disabler it can disable knox and loads of other stuff without root. It also has an automatic debloater.
[Android Q&A, Help & Troubleshooting] shirleys143:
That it works without root is great to know.

Super-sume works but for some reason, the su handoff caused my root checker to be blocked. Hence the no root message I was fighting with. The new SU was blocking the checker. Otherwise the system appears stable. Now looking for another marshmallow sd card hack and root cloak as I don't think xposed appear to work.
[Android Q&A, Help & Troubleshooting] xglaivex:
I am on the latest firmware with root. Testing a different method of installing the SU binary. Will get back with results. Asap.
[Android Q&A, Help & Troubleshooting] ashyx:
Do you mean the xposed module didn't work or xposed itself?

You should always just run SuperSU to check root. It does its own comprehensive checks for root when run. Chainfire has stated if you're not rooted supersu will tell you. There is no need for flaky third party root checkers.

Also what issue with the sdcard are you referring to?
[Android Q&A, Help & Troubleshooting] shirleys143:
I took a quick look on how to get xposed on a samsung and the couple posts I saw referred to using flashing with TWRP or similar. So I just assume that it cannot run on the J120a yet.

xposed framework is great for root cloak and some of the other tweeks. Some games, enterprise applications, and financial applications will not run on a rooted phone.

I am a newbe so I just used the one button 3rd party check with nice big words saying "Rooted!" LOL. It was SuperSU that showed that it was rooted. Dooh. Stayed up too late fiddling with the firmware so was not thinking straight.

Also will look at FlashFire as per j320a thread you were helping on. Also tried to get one on line but ATT wanted a new plan plan. WTF.

Think kitkat and marshmallow had restrictions on allowing apps to write to external SD cards. MarshmallowSDFix. I like that even though external sds tend to crash.

There is a j120a security patch on 22 Feb. I did not do that one. If it was nougat, I will be willing to sacrifice the phone and test. :D

Once again, thanks for all your help. It is a great world phone for the price. Shame gophone is locking down the purchases and unlocking.
[Android Q&A, Help & Troubleshooting] ashyx:
Also

You can install xposed with flash fire. You need the wanam xposed build. Also be careful with security patches, they are not root friendly and you could end up being stuck without root.
[Android Q&A, Help & Troubleshooting] datder:
Cant for the life of me figure out how to replace Kingroot with Supersu. Tried the latest, and oldest kingroots available. I am able to root but once I try to replace kingroot with either a script or super sume 6.7 (the free one) it does not work.
[Android Q&A, Help & Troubleshooting] Whiso:
Hi Guys!!

Recently I did purchase this device, so would like to remove all bloatware by ATT

could Someone summary this? This is a very long thread and I need clarify some steps

AFAIK, basically I need to follow this steps:

1.- Download a boot file

2.- Use Odin to upload that file

3.- Use king root

But I'm new in this kind of actions, Could someone make a tutorial for Dummys (like me)?,

by sample, what steps I need to follow in Odin software to upload that boot file into device

And what about How to add Super Su app? because I read that King root doesn't allow to install it

I thank you in advance