yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.

I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.

Does anyone know what the problem is? Hopefully with a solution as well.
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
Just use twrp to install SuperSU.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.

I never actually got a real confirmation.

Check out the thread below, you will find a root method as yet unconfirmed!

https://xdaforums.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.

I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
If the bootloader is locked there's no way to unlock it.

What was the soft brick, gave you got details?
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
What is your current firmware build?
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Right now I am on Android version 7.1.1
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
No, please post the firmware build version in settings/about.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.

https://imgur.com/EL0E84O

https://imgur.com/46m4P8L
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Goodie! I'll try that out now and come back to confirm whether or not it works
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
OK. Ensure you make a note of what odin and the device screen reports.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.

Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
It's not TWRP its a rooted boot image.

Install the Superuser app from the Play store and hopefully you should have root priveledges.

After installing, open the Superuser app and report back its status.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!

I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
Finally a proper confirmation.

Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.

Just ensure EverRoot is enabled.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
I do want to go into detail on the steps to take. For future reference and for anyone who wants to root their Samsung J3 SM-j320w8. I will have links for things I used down at the bottom to keep this text organized and easy to read through for those who are following along. I apologize for those of you who are android veterans for making this idiot proof. But I feel since rooting the Samsung J3 sm-J320w8 has been a problem that many people have and I want to make this super user friendly.

--

Here are the links to the things you will need:

Odin - https://odindownload.com/ (Always make sure you have the latest version since it will be the most stable.)

Official Android Image file - https://www.sammobile.com/firmwares/galaxy-j3/SM-J320W8/ (Make sure you choose Android 6.0.1 with the PDA J320w8VLU2AQA1)

J320w8 Rooted Boot file - https://androidfilehost.com/?fid=817550096634776077 (If link ever goes down I will keep the file for reuploading purposes.)

--

(Skip this first step if your phone is already in Android version 6.0.1 "J320w8VLU2AQA1". Those last 4 digits are very important as the root is made for "AQA1" from what I can tell. That is the version I used and the only one I can confirm works.)

Edit: You will need to have OEM Unlock enabled for the root to work

To do so, go to your Settings > About Phone > Software Information and tap your Build Number repeatedly until a dialogue saying Developer options are enabled. You will then go to your developer options and enable OEM unlock.

First things first.

I downgraded to Android 6.0.1 (From 7.1.1) using the official android image in Odin. There was a slight issue where after the firmware was installed the phone would keep rebooting right after getting to the home screen. I fixed that by going into the Android Recovery and formatting the cache and factory reset. Then the phone booted up and took me to the setup.

(I think this was due to it trying to reload my old info from 7.1.1 which didn't work with this new (Old?) firmware. But I could be wrong. Anyways. Formatting everything fixed it and I guess that's all that matters... Right? Right.)

I went through the basic setup. Wanted to make sure everything that needed to be there was there before fiddling around with it. (The basic google set up when you first boot up the phone. Nothing special.)

(Start here if your phone is in the right Android version. This might not work if you aren't using the exact same version so try at your own risk)

After this we move on to the actual rooting.

First off. I Put my phone into download mode and opened up Odin. Added the rooted boot into AP and pressed start. After everything passed my phone rebooted and started as normal. Installed SuperSU from the app store. Let it update some things and success! For confirmation I downloaded a root checker and it confirmed that my phone is rooted.
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
I appreciate your input and detailed instruction on this, however I will create a more in depth thread regarding this method. I will use this thread as a point of reference.

It's a pity nobody could have been bothered to confirm the procedure working all those months ago when I first created the root file. There were many downloads, but no confirmation or credit given, as is always the way with XDA.

In reflection I should be able to create an updated method for Nougat. Also I will look at compiling a working TWRP for this device.

Enjoy your rooted device.
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
Having a detailed thread would be great. And if you need testing for the 7.1.1 version and the TWRP feel free to PM me and I will test it out for you. Would be able to get confirmation from me pretty quick. I feel credit should be given where it's due.

Thank you very much for the root file though. Been working on rooting my device for almost a week now. I'd be happy to test out any future things you do for this device.
[Samsung Galaxy J3 (2016) Questions & Answers] ashyx:
Can you just confirm which carrier your device is using?
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
My carrier is Koodo Canada
[Samsung Galaxy J3 (2016) Questions & Answers] LolHacksRule:
I had this problem as well, but here's a solution!

I tried to use CFAR at Firmware.mobi to try to root my J3 (2016, dm-verity fail, not affecting boot, but shows in recovery) (and change SEAndroid to Permissive so Xmod would work after I root), but this happened to me as well (on Android 7.1.1), I was able to boot correctly or into Download Mode, but not into recovery (the error forces my device to reboot and boot normally or into Download Mode if that combo is pressed during boot), I was also not rooted. I tried to flash TWRP for my device using Odin (still with the error appearing every time I try to access recovery mode), but after flashing TWRP my device was technically soft-bricked (with that error on both recovery booting and normal booting) and won't reboot a few seconds after the error appeared so I had to pull and reinsert the battery. I luckily was able to access Download Mode, so I decided to head to firmware.mobi to find my device image files for the latest OS. I downloaded the boot+recovery image as .tar.md5 (I didn't judge its file size: 19MB) then I flashed that on my device through Odin. My device booted straight into recovery (without that error message), I had to wait around 45secs to boot into the recovery options. when they appeared, I went to "reboot system now" and my device rebooted and booted successfully (without the error, still Knox flagged) and none of my data was removed or reset! The device status also changed to Official after flashing that package.

Basically if you encounter this error/soft-brick, head to Firmware.mobi to download the boot+recovery image as .tar.md5 or .tar (so it is flashable for Odin), then boot into Download Mode then flash that with Odin and Android will boot into recovery, then wait about 45secs then target "reboot system now" then Android will boot successfully (it may take a while) and all modified device flags (except that nasty Knox flag) will be removed! None of your data, app data and settings would be affected or wiped! Even your carrier will maintain contact with the device.

Now to try to root it then offer its solution for 7.1.1.
[Samsung Galaxy J3 (2016) Questions & Answers] Chap9k:
I apreciate her effort as well, but I wish she had mentionned about the mandatory step of enabling OEM unlock within Developper options. (Got FRP-locked following her howto post... til I read some other post clearly mentioning about the step.)

I don't mean to flame you @MissCherry1241, as your post definitely helped me a a newcomer (iOS->Android) , but please edit your post to add this step to avoid other user getting their device FRP-locked too.

@ashyx : Did you have time to make this more detailed thread regarding this method that you planned to do ? Do you know if this model still can't be rooted on Nougat+? (From what I understand from this thread, rooting this very device (J320W8), only works for Android 6.0.1 with the PDA J320w8VLU2AQA1, is that correct ?)

I'm totally new to this and i'm not sure at all what to avoid what source I can trust... For instance, this site here seems to provide rooting guide for Nougat for this model.. legit ?

Thanks
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
As far as I can tell there is nothing stopping it from being rooted on Nougat. I just haven't heard of anyone offering a root for the latest version of this device. Though I should preface by saying I haven't really been looking for one, so it may be available with a bit of digging.

Also. Thanks for catching that I haven't mentioned the OEM unlock. It's just something that I do naturally and forgot it had an impact on the rooting process when writing this. I will make sure to edit the original post.

Oh. And as for the website you linked to. I normally stay away from those since they are littered with ads and usually don't bother trying to help. They just throw in fancy keywords for your search engine so you can click on their site for the ad revenue.

I might do a bit of digging to see if I can find a root for the latest version. Will make a new thread for that if/when I do.
[Samsung Galaxy J3 (2016) Questions & Answers] Chap9k:
Great !

So, IIUC, this J320w8 Rooted Boot file by ashyx, is actually confirmed to

not

work on Nougat, right ? (aka it will not root a stock Nougat rom)

Thanks, and sorry making you repeat. I'm so new to this, and the web is filled with so much misleading, bot-redacted articles, bloat, etc.. stuff all over, it's getting hard to find good sources !

Thanks for your help!

Oh! some more questions for you if you don't mind:

Once rooting is complete, should I disable "USB Debugging" & Revoke USB debugging authorizations ? Should I Re-Toggle the OEM unlock option OFF ? and finally should I disable the Developer options & Mode as well ? If not, what are your recommended Post-Root's settings within Developer Options ?
[Samsung Galaxy J3 (2016) Questions & Answers] MissCherry1241:
The file provided by Ashyx is for 6.0.1, and will only work for said android version. You can downgrade from 7.1.1 (Nougat) back to 6.0.1 to then root from there, in the above steps you can see I actually did just that.

So in short. No. The file will not work for Nougat (Nougat being android 7.1.1 if I'm not mistaken. I'm better at remembering version numbers than weird names)

As for all the other settings like OEM and usb debugging that's up to you. Whether you have them on or off will not affect your device whatsoever after it is rooted. And incase you thought turning the settings off will unroot your device or brick it. It won't.

And don't be shy to ask things. I'm happy to help where I can. Everyone is new at some point.
[Samsung Galaxy J3 (2016) Questions & Answers] Chap9k:
Hi ashyx, can you confirm this by now ? (have you tested or found source indicating this is a working maneuver?

Yea I did just that as well (worked fine).

I feel you on that. I hate the codenaming versioning scheme as well .. It's so.. "proprietary'ish" (and harder to remember)
[Samsung Galaxy J3 (2016) Questions & Answers] Chap9k:
-Could someone explain to me why such guide even exist ? (what's their purpose, other than instructing J320W8 device owners how to update their device the latest STOCK firmware in a useless complicated way ? (rather than from the device itselft).. This guide is not providing, nor instructing about flashing a rooted Nougat, it's only about doing so for the latest stock one, the manual way... Why ? .. In what case this can be useful to any (even those not intending to root) J320W8 owners ? I feel like I'm missing a chunk somewhere..

-Is it normal Samsung's official Android USB driver for Windows download page provide an outdated version ? (v1.5.55.0 - Feb 2015) ..

I've seen this driver in v1.5.65.0 (yes, Samsung-signed) @ couple places... What version you get for this device ? the old one from the official page, or the latest from some other source ?
[Samsung Galaxy J3 (2016) Questions & Answers] deskwizard:
[MENTION=8880308]MissCherry1241[/MENTION] Good tutorial, worked perfectly, thanks!

[MENTION=4899305]ashyx[/MENTION] No luck with FlashFire sadly, thanks for the modified boot.img file, at least I have a starting point ;)

I'm having a play with 7.1.1 re: root, I have the big picture about how ashyx went about with it, I've tested modifying the boot.img myself and confirmed my changes are sticking, now I'll dive into the details ;)

I've played with that kind of stuff a bit, ages ago, like ICS days, with Chinese SoC BSP's, so don't get your hopes up :P

DW
[Samsung Galaxy J3 (2016) Questions & Answers] deskwizard:
Well, that's a day and a half I'll never get back ... lol

7.1.1 roots fine with Magisk (v.16 at the time of this post) using the "Magisk Manager instructions", in case anyone else hasn't figured it out yet :P

The only part missing in these instructions is the fact that you need to have WiFi connected for it to work (unsure about LTE and the like)

The boot.img file can easily be extracted from the ROM files at sammobile

(Protip: they're all the same, the network selection (and associated configurations and apps) is done with the CSC code, meaning if you want to switch provider, all you need to do is change the CSC code (the dialer instructions work); quite a smart system if you ask me, though a bit wasteful spacewise)

Tested with an adb shell and a couple file explorers successfully, remounting /system read/write works.

Now let's have fun *wink wink*

DW
[Samsung Galaxy J3 (2016) Questions & Answers] freddie.here:
Hi, do you mind sharing a more detailed "how to" with this Magisk@ 7.1.1 approach, that'd very helpful to me and I believe a lot of people! Many thanks in advance !
[Samsung Galaxy J3 (2016) Questions & Answers] naruto001:
Hi! I'm new here! :) I have try to root with odin using CF-auto root and it always give fail... My usb debug is enable and my oem is enable too. got a samsung sm-j320w8. can someone can help me there step by step, i,m not good at it. I got files to recover and i'm lost thx you ;)
[Samsung Galaxy J3 (2016) Questions & Answers] luckysnow:
can you help me with this screen shot,,, i read your post in downgrade from android 7 to 6.0

to root j320w8,,, when i was going to unlock using samsung tool pro "it says hwid mismatch,,,, security damaged
[LG V30 Questions & Answers] Marlon25:
Hi. someone to tell me some application for LG v30, to keep the screen on while I read. ROM EUROPE Spain at least does not bring as a possible option.

thanks from Spain
[Xiaomi Mi A1 Questions & Answers] heyfritzzapie:
Is there anyway to assign the camera shortcut? Like if i choose GCmod as the default app for the camera shortcut can i revert it back to the default mi camera?
[Xiaomi Mi A1 Questions & Answers] NITRO_100:
In settings - apps, there is default apps section, you can change it there.
[Xiaomi Mi A1 Questions & Answers] JaadiBooti:
Go to any camera app- info - and clear defaults

When you launch the shortcut you will be given a choice of cameras.
[Xiaomi Redmi 4X Questions & Answers] GoJo ^^:
Coming from the Redmi 3s, how did you feel with the 4x? I use RR room, so a feedback from people that used it on 3s and still use on the 4x.

How's the camera? YouTube compare show better pics from the 3s.. How about mic? I do make sound records with my phone and 3s was not so great for this..
[HTC Tornado] tjhammerhead:
Anyone have a factory Service Manual for the SDA?
[MTCD Software Development] PekeMM:
I have Dasaita HA2153-v640 4/32 Octa core device, still on stock.

There is a problem when Installing Viber https://play.google.com/store/apps/details?id=com.viber.voip&hl=en it goes ok but after it is activated using my phone it crashes.

Has anyone managed to find out why it crashes? I'm guessing that there is some issues on initializing main UI components like Contact Storage.

I also Noticed that Viber is not available in Accounts listing after installation like on my other devices.

Please help.
[Moto Z2 Force  Questions & Answers] Koohara947:
Hey everyone!

Just wanted to ask a couple questions and start another discussion thread for those of us that have Oreo installed on our devices.

Questions:

With twrp on oreo, what's the status on the flashable version?

Anyone currently or thinking about creating new roms, kernels, etc for the device?

Lastly, what are some things that the nondevs here can do to help us all out?

Hope to see some good discussions

Thanks in advance!
[Moto Z2 Force  Questions & Answers] davehasninjas:
Idk anything about the status of TWRP, so I can't help you there. Overall, I know there was an effort to get a device to a dev, and it was successful. Invisiblek now has one. Looks like he's working on lineage, which is super awesome.

The device now has a repo on the lineage github, so you can see work is being done. As for a timeframe, no clue, just have patience and know that it'll be released once it's ready. We're fortunate that Moto has already updated us to Oreo and it's a pretty stock interface. Only way they could've done better in my view would have been to update the device to support project treble, but that's an entirely different story.

That's about all I know, hope it helps somewhat.
[Moto Z2 Force  Questions & Answers] charlatan01:
Patience indeed. It'll move along at some point. Next to Sony, I think Moto has one of the cleanest implementations of Android, so it's definitely bearable.

Plus, with the price dropping into "steal" territory, I see more smart ppl coming this way.
[Moto Z2 Force  Questions & Answers] Koohara947:
Yea thank you guys! I'm being as patient as can be and I just wanted to have a thread here were any and all of us curious folks can have a place to talk about the upcoming of this device and the near future development holds for it. I didn't know it was on lineages repo so that's awesome to hear! That's a perfect example of why I created this post, just to spread the word into one forum and just have a couple chats with everyone about the moto.

Cheers guys, hope to hear more from others too!
[Samsung Galaxy S8+ Questions & Answers] acheney1990:
I need some help. I'm not sure where to go from here. Ok so I have a Canadian S8+ (SM-G955W). A couple weeks ago I flashed what all the articles said was a final release of Oreo just not released yet, meant for SM-G955U, with build number R16NW.G955USQU2CRA1. I've got a couple questions:

1. Is there any new update I should/can flash and where would I get it from?

2. Will I get OTA updates at all if I'm on the software for the unlocked version?

3. I've not had any major issues but my signal has been weaker then before, any way to fix this?

I'm not an expert at this so simple instructions are best. Thanks. ?
[Samsung Galaxy S8+ Questions & Answers] djcrystals:
If you want to update to the most recent Oreo release, not official yet, it's CRAF. You have to ODIN back to BQL1 then flash the update to CRAF.

https://xdaforums.com/galaxy-s8+/how-to/guide-oreo-beta-usa-snapdragon-s8-t3700907/post75263622#post75263622
[Samsung Galaxy S8+ Questions & Answers] acheney1990:
Will I get OTA updates after that?
[Samsung Galaxy S8+ Questions & Answers] djcrystals:
Negative. BUT, I'm on CRA9, which was released before CRAF and it runs GREAT, for me. I'll stay on this till official rolls out. Then I could (and yourself) flash back to BQL1 and take the OTA or wait for the ODIN files to be released and flash that way.
[Samsung Galaxy S8+ Questions & Answers] acheney1990:
Ok. Thanks. And to flash BQL1 in Odin, which boxes do I have to select again?
[Samsung Galaxy S8+ Questions & Answers] djcrystals:
Auto Reboot, F Reset Time

Was that what you meant? The options in ODIN?
[Samsung Galaxy S8+ Questions & Answers] acheney1990:
I got it, thanks! Running the latest beta now. ?