yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Just to clear things up. If you have any of these (BTU, CPW, DBT, ITV, XEF, XEO, XEU) csc now, you will have the same csc after flash as well.

If you're on another csc now and flash this, you'll get ITV as csc, since that's the default csc for multi OXA. You can still change to any of the other included csc's if you have root, but it also requires a factory reset to change it.

Certain csc's have different apps and features even if they are in the same firmware. That's how samsung customize their firmware for different countries/regions.

DBT most likely have some german app installed from the csc folder, while other csc's don't. Some csc's have settings for VoLTE, and others don't.

Another csc can have bike mode, which is not available for another country etc.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Menroid:
As far as i can tell you have to wait for the official DBT (Germany) to have an smooth working phone (and no tripped Knox fuse!).

Only if you want to experiment the PHN is the unbranded Netherlands version.

*warning you will trip Knox!*

Just Checked here: https://www.sammobile.com/firmwares/galaxy-a3/SM-A320FL/
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] simple_s:
Works on my Galaxy A3 2017 (SM-320FL) from Germany very well. No problem to flash with Odin. I used the normal CSC, not the Home_CSC because I'm a friend of starting from scratch with a new OS. I also rooted it without any issues and installed Magisk and Xposed. Now even the Nand Backup works in TWRP.:good:

Thank you!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] shiwan:
Hello, I have updated my phone (A320FL, French, Orange) with a Spanish firmware. And it worked perfectly. It didn't trip knox, everything works, no problem. All I did was select repartion in Odin. That's all you need. As long as you have the same model number, you won't have any problem at all.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Thanks for the firmware. I still have to wait for DBT so I flashed this on my 320FL since OXA works with DBT.

I just saw there is a new version for ITV with OXA available (BQI4).

One thing I noticed is that when you turn on the device it does not vibrate anymore (on MM it did). Is that normal?
[MENTION=3245411]tys0n[/MENTION] actually it is A320FXXU1 and not A320FXXU2 (I'm referring to the post in the other thread).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] khanvict90:
Any body else have lag with the patern unlock screen ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
YEEES :) but is a security feature that will prevent rapid succesive multiple pattern unlock attempts.

Try ultra power saving mode and see what happens... you might be unable to unlock your device if you use a dot pattern as backup unlock solution.

So it might be a bug also, something Samsung forgot about to properly integrate.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] y2kadir:
can you explain how did you do that exactly? I have official Andorid M with root. I want to use Android 7 from here is this possible? I have DTM / DDE CSC (TMOBILE). Can you explain me how to flash? also howto magisk and xposed. I dont want to loose my data files. thx
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Well I also have 320fl, but unbranded DBT (Germany) and it worked. BUT I don't think it will work on a branded version, because of the wrong CSC (OXA supports DBT). But I'm not sure, sorry.

But you may not have to wait long for your official version, just look at updato or similar sites.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] y2kadir:
thx for the informations but no risk no fun. I tried and it worked perfect on my csc. So can you tell me how you rooted this and xposed and magisk? is it also possible to update security patches?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Cool thing.

Well root it like you did on MM, I see no difference.

Xposed is an issue with Nougat, I didn't use it and can't help there.

And the patches, well I thought root means no updates, but I could be wrong.

Have fun.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] simple_s:
Sorry for the long wait. So here is the tutorial. I'm not responsible for any damage. My phone was not branded.

Make sure you read the whole tutorial before doing anything.

Make a backup of your data. It's very possible that you need to make a factory reset!

Also have a look at the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!

1. Download the following stuff:

Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n

Odin 3.12.5

twrp_3.1.1-1_sm-a320f_11917 thx to ashyx

Boot image patch no-verity-no-encrypt_ashyx thx to ashyx

[UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid

Magisk thx to topjohnwu

2. Flash Android 7 via Odin. There are enough tutorials on how to do that.

3. Flash TWRP via Odin; Thread with additional informations

4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.

5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.

6. Copy the Magisk-v14.0.zip file to your SD card and install it via TWRP. Reboot to System.

7. Open the Magisk Manager and enable root access via SuperUser within the Manager.

8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.

9. Now you should have root access, Magisk and Xposed up and running.

Quotes and additional information:

[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx

[UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid

[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu

[2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu

---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------

I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the "old flash the SuperUser.zip via TWRP" method.

After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Thanks [MENTION=4890708]simple_s[/MENTION]

BUT be careful with Xposed!!!

Especially on Samsung stock ROM.

You need permissive kernel!

When used as a Magisk module and you wipe the caches the device will not boot anymore (that's what I read).

Please people read read read and read about Xposed before using it on Samsung Nougat!!!

And make backups.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Sad64:
A320FL

Hello, dear friend. I have A320FL and android 7.0. I really want to root. I ask you to give me instructions. Thank you
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Please look two posts above there is a good instruction for example how to flash Magisk root with TWRP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Sad64:
there will not be problems? unlocking the screen and stuff ... I have an Android 7.0
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Seems like you just started. I suggest that you read about what you want first on XDA for at least a week and also take notes. Please inform yourself fist because it takes time to learn this!

And...only you are responsible if something goes wrong! Problems mostly occur, when people didn't read enough. I can't give more help.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Sad64:
Dear friend.

I settled the recovery.

After installing su, or no-verity-no-encrypt_ashyx the phone does not turn on.

LOGO - SAMSUNG 10-15 min

fap locx off
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Please follow the exact steps in the TWRP thread. You probably forgot to FORMAT data.

In TWRP --> wipe--> FORMAT data --> type "yes"

and follow the steps. You will loose your data so make backups with TWRP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Finally...a lot of new firmwares BQH7 are available to download, also DBT. I still wonder about that BQI4 for Italy ITV, if that is even newer or better?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Maxiking2312:
Hi I wanna root my sm-a320fl German

How did do that just inject TWRP with Odin and SuperSU or how?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
+1 (A320F, Nougat, rooted, patched, TWRPed)

A workaround for me is to disable battery saving, but that's definitely not the root of the problem.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Could be the combination of no verity and Magisk like some posted in TWRP thread. It is enough to just flash Magisk and not no verity.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] eiselfentod:
Does anyone have Batterydrain on A320FLXXS2BRA1 ? Since securitypatch 1.1.18 batterylife is terrible for ... and every attemp to downgrade fails. any suggetions ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Thanks! The thing is, I rooted with supersu, not with Magisk.

So, if I undo supersu/no-verity, then flash Magisk, shall that be enough for disabling forced encryption?

Bonus question: for undoing the no-verity patch, do I need to go through the whole TWRP process again, or is it enough to do a factory reset?

Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
I know for sure that Magisk disables encryption, did that last weekend with fresh FW flash DRA2.

I'm not sure if SuperSU does the same.

I'm also not sure about your bonus question, but I would do a clean flash. But I remember people posting that with only Magisk the PIN lag is gone.

And I'm not sure if A320 is affected by RMM state with the new bootloaders.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Bernique:
I was on an old build, rooted, and wanted to update. So I flashed the latest build and so unrooted. I wanted to root mack, but found out to have this RMM state. I tried to flash TWRP but got stuck on a warning telling me that my identity could not be retrieved and I had to wipe everything. I tried to re-flash the stock rom but without success. I finally could make it by flashing only the AP part of the rom. I am now waiting for 7 days before trying again.

What I flashed is:

A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Thank you again. That's good news. (Btw I made a mistake on my previous post: I didn't root with SuperSU but with superuser plus a patch, so I am "de-crypted").

As to flashing Magisk now, I've seen some un-rooting scripts around there that supposedly get rid of root plus any modifications and patches, but I'll definitely go for a clean flash as you suggest, just in case.

Fortunately my A320 firmware is not affected by the RMM state, but still, it doesn't harm to flash the anti-RMM zip circulating around there.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
OK, but the RMM skript didn't alter the build.prop line for me, had to change it manually with kernel adiutor before flashing new FW. And I also flashed HOME CSC so all data was still there. Then I could flash TWRP with Odin without issues. Then flashed RMM skript and then Magisk. Then immediately changed the build.prop line manually again with kernel adiutor.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
So the A320FL is affected by RMM state...damn...thanks for your post. I hope your prison time won't be too hard.

Do you know if its necessary to have a Samsung account as well besides the Google account? I never created a Samsung account, that's why I'm asking.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Bernique:
I don't have any Samsung account, and never had. I always dismissed the question. I've never heard it was mandatory. I hope to tell you soon.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Sorry if I haven't got it: do you mean that the RMM script was useless for you without editing build.prop? In such case, should it suffice to just manually edit build.prop and skip flashing the RMM script? Or are both things necessary?

I believe that my A320F is NOT affected by RMM; perhaps because mine is A320F/DS, perhaps because it's from some Arab country... But I'll doble check it and come back with confirmation.

Personally I don't have a Samsung account NOR even a Google account. I keep my Android devices totally Google-less. Might this be the reason why I don't see my device locked by RMM?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
1. The script deleted the Rlc folder with the app, but didn't change build.prop line. I flashed the script but changed the line manually. Before AND after flashing the new FW.

I flashed HOME CSC with the new FW to keep the data, booted one time into the ROM and then flashed TWRP, formatted data, booted into TWRP, flashed the script and Magisk.

2. I don't think RMM depends on model, but on the new bootloaders and the new boot.img, but I could be wrong. I read a lot, but for me it's hard to understand.

3. Since I think RMM depends on bootloader and boot.img I really don't know if living without Samsung or Google account prevents you from RMM. It could be since RMM seems to be a new security feature, but my knowledge is way too limited :silly:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Then I don't see that much use for the script. I mean: if you still have to manually edit build.prop, you can all the same manually delete the rlc folder. I would've hoped the script took care of everything. :)

This one, I don't quite get: if you flash HOME_CSC in order to keep the data, but you then format data after flashing TWRP, where's the point in flashing HOME_CSC and not directly CSC? Did I miss something?

I think that's right: RMM depends on the new builds and updates. My A320F does not have RMM because it's some August 2017 build (...U2BQI3), but as I get it, the January updates are already built with RMM, unfortunately. A strong reason for not updating, in my case.

Mine also is! But the way I understand RMM (as explained here), it becomes aware of the device's "legal" owner by storing his Google account information (the one set up when first-ever configuring the system) somewhere in a "secure FRP" partition, so when/if an "unauthorized" holder tries to wipe and reboot, since he can't provide the right G account and password he'll be asked for by RMM, he is locked out.

But then my question is: what happens if you NEVER set up a G account in your device and live without G happily ever after? What happens then with this RMM thing? Which G account information is RMM going to ask the offender for, in order to check his true ownership, if no G account has ever been introduced? :confused:

P.S.: attached is a screenshot of my A320F in download mode: no RMM anywhere.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Not even the wonderfulest security feature should be implemented at the cost of being utterly unable to unlock the device. :) In my opinion, it is a very dangerous bug... unless it only happens in rooted phones, in whose case it's not Samsung's responsibility. And yet.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
1. Yes you're right.

2. I don't know if a FW flash puts back the Rlc app, but by flashing HOME CSC I hoped that at least the build.prop line would still be 0 and it would be enough not to enter RMM. And by flashing the script right after TWRP at least the Rlc app is gone. I really don't know if this makes sense.

3. I was on August too. And with the steps explained I could update to January and flash TWRP right away.

4. That question is way above my knowledge, but you could be right. But I'm also confused...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Hmm... May I ask you if flashing the January update was worth the troble (and the risk) for you? I mean, what are the differences between the previous build and this one? New features? Better battery life? Improved performance? I ask you because I'm not sure I want to flash that update. I like to use the latest firmwares, but sometimes they only bring more trouble, more bloat, and nothing really positive.

[EDIT] By the way, forgive me a silly question I'm unable to find an answer for: if you're on a custom recovery (let's say TWRP) and you flash a stock firmware (let's say an update) via Odin, do you lose TWRP? Does the process revert your device back to stock recovery?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
1. Well, no risk no fun. And life goes on and Oreo will come, so I took the step.

2. Yes, stock FW will erase TWRP and replace it with the normal recovery.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] 220Fast:
hello guys. i need a bit help please

i tried to flash file from original post. it didnt worked so then i flashed only AP part through odin and voala it works.

now question is will i miss something ? wont this break my phone or something ?

thx for asnwers
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Thank you!

As to updating, I don't mean to question your motives, of course. I just try to decide whether or not it's worth the trouble for me; that's why I'd like to know what improvements, fixes and/or new features there are in the new build, if any.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Well, actually I don't see or feel any difference or improvements. Basically it is only security patches.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zogoibi:
Don't take my word for it, but I'm pretty sure it won't break anything.

Anyhow, if you've already flashed the AP, by now you must know if it broke something. :)

---------- Post added at 07:06 PM ---------- Previous post was at 06:53 PM ----------

All right. So, I'll share my experience. What I finally did was:

1. Reboot to TWRP and a) backup Data partition, b) wipe everything (probably step b is unnecessary, since step 2 will wipe everything all the same).

2. Reboot to Download Mode and flash a clean stock ROM (August build; no need for Samsung's extra s**t :) ) via Odin (AP, BL, CSC and modem). Reboot to system and check that everything works.

3. Reboot to Download Mode again and flash TWRP.

4. Reboot to TWRP and a) restore Data partition backup, b) flash Magisk.zip

That's it. On next reboot to system everything worked fine: all my user apps and settings were there, device is rooted, there is no lockscreen lag. So far, so good.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Pat750:
Any news? Did the 7 day waiting help? I flashed the same file when I got this device and had no problems.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Bernique:
I have tried again, but I got blocked on a screen "your device has been encrypted" or something like that. I reflashed stock room, but lost all my data. I will not try again, I am waiting for a somehow stable lineageOS to get rid of all this.

Thanks for your interest in my problem. I was not able to download the previous build either.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Janarsam:
Hello, I tried to remove frp lock but my phone (A320FL, vietnam) not working with these methods
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] reza5261:
SM-A320FL Official Firmware Android 8.0.0

hi, free download a320fl firmware oreo update with Direct Link!

free download stock rom a320fl >>>> Direct Link

Build Number : A320FLXXS3CRK3

OS : 8.0.0

Date : 08.01.2019

Region : XEF (France)

Download Odin 3.13.3
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cjlallana:
Why this?

You have sammobile.com with already all the official and latest stom ROMs.

Check here
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] WiwiPouPou:
Nous thanks for that speed...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cjlallana:
Still, why reviving an old thread with a not so up-to-date ROM?

You have even newer ROMs, and they are all already 8.0, not as the thread's title says.
[Galaxy Note 4 Q&A, Help & Troubleshooting] IIABODEII:
Hello everyone.

I had a note 3 for about 3 years and I just bought a used note 4 910c. I have been desperately trying to remove ongoing notification (Power Saving), which was usually an option for most Note 3 custom roms.

However, I can't find a ported custom rom with this option. I have power saving mode on 24/7 so it's really annoying to see the notification every time I pulled down the status bar.

Before I post this thread, I actually spent 5 days learning about (XML, Tickle My Android) and followed this tutorial But no luck :crying:

I am currently using Electron Rom ROM.

I appreciate the help in advance :highfive:
[Galaxy Note 4 Q&A, Help & Troubleshooting] Kinsman-UK:
On stock with GoodLock, currently have power saving mode on and don't have any notification (just turns status bar grey).
[LG G5 Guides, News, & Discussion] Xygote:
Disassemble LG G5 using the link below.

https://www.youtube.com/watch?v=hveXdJLJEeU

Disconnect the Wifi Cable (Black One), Rear Camera, Front Camera.

Now with just the logic board, place it on a surface that won't melt.

It should look like the picture below. Warning don't take off anything else

https://imgur.com/a/gmp9Z

Turn on your heatgun and apply left right motion only concentrating on the cpu metal plate for around 15 seconds.

Do the same thing on the opposite side of the cpu plate.

Let it cool down for around 10 minutes.

Put it back together and it should work.

I did it atleast four times, first time it worked but failed after few minutes.

Second and third time was not working at all.

The fourth time I did it, it was working.

It's been a while and it still going.

Credits to the poster.

http://bit.ly/2f1knOL
[LG G5 Guides, News, & Discussion] edwardbp:
I don't have a heatgun, could a hairdryer work?

Thanks for your post. Hairdryers go up to 140 degrees. Could this be enough? If not, can you share what setting the heat gun should be put to for this repair? Thanks again. :)
[Galaxy S6 Q&A, Help & Troubleshooting] dragonovak:
Hello everyone I am new here.

I have a problem. I need help. I accidently bricked the phone. Samsung galaxy s6 (smg920F) with wrong version of android. :crying:. I used odin3, i dont know how to see build number and version when the phone is bricked. Thank you in advance :D
[Galaxy S6 Q&A, Help & Troubleshooting] GuestK0076:
http://cdn.droidviews.com/wp-content/uploads/2015/03/Odin3_v3.12.7.zip Odin 3.12.7 (latest)

https://xdaforums.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 SamFirm 0.3.6 (latest)

http://samsung-usb-driver-for-mobile-phones.en.lo4d.com/download Samsung USB Drivers 1.5.63 (latest)

Install latest USB drivers, unpack lastest Odin3 and SamFirm. Use SamFirm to download latest firmware for your model, so put "SM-G920F" in "model" check "Auto" under that, put CSC code for your country in "Region", download it and then just flash it in Odin ;)

Here you got full CSC codes list and also short guide how to use SamFirm :P

https://www.androidsage.com/2017/07...specific-product-code-csc-and-country-region/

How to root then? > CF-Auto-Root

How to get TWRP then? > latest TWRP

Customize? > Look my signature ;)
[Galaxy S6 Q&A, Help & Troubleshooting] dragonovak:
thank you, it works as it should be :good: :victory: :D
[Galaxy S6 Q&A, Help & Troubleshooting] GuestK0076:
No problem... I think that post will help in future to another no experienced users xD
[Galaxy S6 Q&A, Help & Troubleshooting] dragonovak:
I have another question. which program you recommend for rooting samsung galaxy s6