[ROOT] SM-G532F/G532G/G532M - Galaxy J2 GRAND PRIME PLUS (2016)

[ashyx]

Below you will find my procedure to root the SM-G532F/G532G/SM-G532M Galaxy J2 GRAND PRIME PLUS/ Mediatek MT6737T.
This will root your device with SR3-SuperSU-v2.79-SR3-20170114223742

This procedure may work for previous and future firmware releases or it may not, however it is intended for the firmware versions as posted below. If you encounter issues simply flash the stock boot image included with the download.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.


STATUS: Tested working



DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED

NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.


Instructions:

◘ 1. Download the respective files below:

For SM-G532F based on AQD1 firmware- root_and_boot_sm-g532f

For SM-G532G based on AQC4 firmware - root_and_boot_sm-g532g

For SM-G532M based on AQD2 firmware - SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_31517

ODIN 3.12

SAMSUNG_USB_Driver_for_Mobile_Phones

◘ 2. Install the USB driver and ODIN to Windows.

◘ 3. Boot your device to DOWNLOAD mode then connect your USB cable.

◘ 4. Run ODIN and place either SuperSU-v2.79-SR3_rooted_boot_sm-g532f_AQD1.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532g_AQC4.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_3151 as is in the AP slot. Don't change any options and hit START.

◘ 5. Wait for the device to flash and reboot.

◘ 6. Install the SuperSU apk from Play store and you should be rooted.

◘ 7. Have fun!



Credits: ME, @Chainfire and my tester @ShaDisNX255


PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.


IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU

 

[ShaDisNX255]

I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!

 

[ashyx]

I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!

There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.

 

[ShaDisNX255]

There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.

I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"

 

[ashyx]

I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"

AQD2 is the latest.
Leave it with me.

 

[ShaDisNX255]

AQD2 is the latest.
Leave it with me.

Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing

 

[ashyx]

Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing

Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954

NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.

.

 

[ShaDisNX255]

Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954

NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.

.

I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes

---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------

After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?

 

[ashyx]

I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes

---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------

After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?

Are you using magisk or some other root application?

I also suggest to install V2.79 apk as the latest Supersu updates are having issues.

http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/

 

[ShaDisNX255]

Are you using magisk or some other root application?

I also suggest to install V2.79 apk as the latest Supersu updates are having issues.

http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/

Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.

---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------

Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.

Also, this seems to have broken my IMEI. I got IMEI unknown

 

[ashyx]

Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.

---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------




Also, this seems to have broken my IMEI. I got IMEI unknown

The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165

To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.


Regarding the IMEI issue. This is related to a kernel/firmware mismatch.

You should be running the AQD2 firmware.
Which firmware are you currently running?

 

[AlexEvans6]

Not work for my phone
Everybody help me please

 

[ashyx]

Not work for my phone
Everybody help me please

What does that actually mean?

 

[ShaDisNX255]

The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165

To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.


Regarding the IMEI issue. This is related to a kernel/firmware mismatch.

You should be running the AQD2 firmware.
Which firmware are you currently running?

I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.

 

[ashyx]

I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.

Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?

 

[ShaDisNX255]

Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?

I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?

 

[ashyx]

I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?

OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?

Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.

 

[ShaDisNX255]

OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?

Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.

By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?

 

[ashyx]

By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?

Data is the internal storage. It's separate from the system partition where the OS resides. Wiping data basically makes your device factory fresh as it wipes all user apps, settings and media.
In stock recovery it's labelled factory reset.
Every firmware has a recovery even the one you mentioned or your device just wouldn't boot.

If root apps are reporting not rooted then there is an issue somewhere. Quite likely it's encryption on the data partition that's causing the issue.
To remove encryption it is required to wipe data in recovery after flashing the boot image.

If it still doesn't work without encryption then I'm a little unsure of what the issue is as this procedure works just fine on Snapdragon and Exynos devices. It may be some kind of mediatek weirdness.

In any case I have an alternative method which should work, but involves an extra step.

At some point I will be looking at compiling twrp for this device, but I'd like to work out this root issue first.

For fast downloads go to updato.com

 

[AlexEvans6]

What does that actually mean?

Idk help me please