yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
So, you got rid of all "...has stopped" errors?

If yes, could you please write a step-by-step list of things you did (and links to rom/firmware) after accidentally formatting system partition? Thanks!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
Sure, I'd be happy to. After wiping the data and system partitions, I downloaded a fresh copy of the latest stock ROM from Updato: http://updato.com/firmware-archive-select-model?record=1FB427E735D511E7963AFA163EE8F90B. Unlike other websites that host Samsung firmware files, this one has no fees, sign up requirements, slow speeds or any of a myriad other annoyances.

I then flashed that file using the latest version of Odin, following the instructions listed in the first post of this thread and a few other places on the Internet. I then flashed TWRP again and rebooted to recovery as described in the TWRP thread for the Samsung Galaxy A3 (2017) here on XDA: https://xdaforums.com/samsung-a-series/development/recovery-galaxy-a3-sm-a320f-t3562302. It worked in the first try.

Then I wiped the data partition, which got rid of the errors saying it failed to mount. The other two partitions continued to show mounting errors, but I ignored them. I flashed SuperSU, rebooted the phone, set it up and we were in business. I've not had a single crash since.

I've even gone ahead and enabled Google Assistant on it, with the help of a tutorial on Beebom: https://beebom.com/how-enable-google-assistant-any-android-no-root/. At one point while performing the steps described therein, I was getting Google Play Services crashes and the Play Store would refuse to log me in. I solved that by uninstalling all updates for the Google app, Play Services and Play Store, and updating them again, and it's been smooth sailing since.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] F157:
Can someone please share the necessary steps for upgrading firmware once rooted? The phone's software update states "the operating system on your device has been modified in an unauthorized way".

Thank you for your help!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
If rooted, you can either try to unroot (uninstall Super SU by using its own "Complete unroot" option in application's settings tab ) and then go to phome's settings > devoloper options and re-enable "OEM lock".

Restart the device afterwards and try to OTA update.

If you can get the OTA update as a zip file, you could skip all this and just use FlashFire to perform the update.

If nothing works, download Samsung Smart Switch and follow the software recovery procedure.

Samsung Smart Switch has the ability to reflash SM-A320F/SM-A320FL with factory software based on device's serial number S/N.

Alternatively just use sammobile/firmwares (or other sources) and Odin to download and flash a factory ROM of your liking.

This flashing procedures might wipe your data so make backups first if necessary.

You can not just simply do OTA updates if rooted :cyclops: The world in which we live is far from perfect.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] F157:
Thanks for the hints.

Isn't it so that re-enabling OEM lock while still having a custom recovery installed will result in a bootloop?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
You could try and see :cyclops: also make sure you saw my updated post.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
No, don't enable OEM lock with root or custom recovery. You will be forced to use download mode and to flash stock firmware.

Skickat från min Honor5X
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] F157:
Thanks, that's what I also remembered.

Is it possible to re-flash stock recovery from first post in this thread, then enable OEM lock and have OTA updates again?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
The OEM lock will check each firmware component to see if corresponds to some HASH table or something and prevent the phone from booting if it detects for example a custom recovery.

I would not say that by flashing the recovery from the first post you can expect 100% success, but you could try and see :cyclops:

The only other option is to flash the entire firmware with Odin or with Smart Switch so be prepared to do that.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Lucas.kobi:
Fail to mount /persdata with TWRP for lineageOS 14.1 installation

Hey Guys,

I need your help since I failed to flash lineageOS 14.1 (lineage-14.1-20170525-UNOFFICIAL_a3ltexx_a3ultexx_a33gxx_vlw)

on my Samsung Galaxy SM-A320FL Marshmallow 6.0.1

I used Odin (v3.12.3 by Skyneel.com) as recommended and wanted to install Lineage as zip with

TWRP (twrp_3.0.3-1_sm-a320f_24217.tar.

I format all Data (under WIPE) and afterwards I was able to mount /data but unfortunately it was not still not able to mount /persdata

Then we tried to flash SuperSU (SuperSU-v2.82-201705271822) with TWRP and didn't reboot afterwards.

Still we were not able to mount /persdata but tried to install lineage again.

After we rebooted the Samsung Android ROMS were installed again.

Can U please help me out?

Thank you in advance!

Lucas
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Don't try that zip again. It's for A300F/A300FU/A300H. A3 2015 model with Qualcomm.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Lucas.kobi:
Ok thank you. Is there a file for the exact Galaxy SM A320FL or I just have to wait?

And another question except from the wrong zip file I did everything right?

Gracias
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
I haven't seen any serious development like LOS, AOSP for A-Series 2017 here on xda yet but I could be wrong.

Quick search on github gave me a common device tree for Exynos7870 so that's a start.

When it comes to flashing it's always recommended to make factory reset to prevent boot problems and force closes.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Chemtrailer:
failed to mount /persdata error

Hi Devs,

at first i´ve to say "sry for my bad english"^^ and thx for your work <3

I´ve a little unsolved problem with my A320FL. I´ve rooted like the step by step tutorial on the first page.

While i installed the TWRP, i´ve become a /persdata mount error. i have ignored the error and have rebooted my phone.

Back in the android OS i´ve installed RootSU which worked perfectly

ok but since i´ve rooted my phone some apps (like afwall, adblock, kaspersky ...) stuck, so that i´ve to reboot my phone.

is this normal?

or comes this from the "/persdata" error?

it their a way to fix this?

thk u in advance
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] micko80fu:
I had same problem i needed to format sd card through actual device it was format exfat and for some reason unreadable twrp method could read same sd card though.... go figure anyway format sd card to fat32 and that might solve it for you... worked for me anyway hope it helps if so better than frustrating yourself
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] khanvict90:
maybe offtopic but is it possible to flash a a320F stock rom a320FL?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] notthesun:
yes it's offtopic and yes you can...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] khanvict90:
Thanks mate!!!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] notthesun:
Someone has tried this method on android 7 ??

Edit: works good on Android 7 but you Need to use supersu 2.82
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] scorpiongabi:
After I rooted my sm-a320FL does random restarts and the only error i can find is Failed to mount /data (Invalid Argument) in Recovery mode trying to install Supersu , and appear not rooted

Do you know what to do ?

Thank you
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Lexvox:
Google framework crashes

So i tried rooting my device just the way it was described in this thread , just like i did the countless times with my phones before that. So i flashed twrp with odin, checked if twrp was working properly and then rebooted my phone into android and here the crysis begins. Every framework app like google play services and co started crashing over and over again. My device is the SM-A320FL and not SM-A320F but after a bit of research the ony difference i saw was where it was sold, so i guess thats not the problem. I havent rooted it yet i just installed twrp.

Has anyone had a simmilar experience or even knows an awnser to this??

Help would be really apreciated.

-Lexvox
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
-Reboot into recovery and wipe cache, wipe data

-Reboot the device as normal

-Wait a few minutes for the initialization to be complete

If it doesn't work, this is what you do next:

https://www.youtube.com/watch?v=9QhJngOuLQ4&t=269s

-Download Samsung Smart Switch

-Enter firmware recovery procedure

-Use your device model and serial number to identify and download the firmware

-Follow the steps indicated and install the factory firmware

-Tur on your device as usual

-Wait a few minutes for the initialization to be complete

The firmware and apps should now be ok.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Utopie:
Hello.

I'm (re)rooting a SM-A320FL to enable Samsung Health app. I'm wondering if someone could help clear this up for me.

I want to root without having to wipe ANY data - internal or SD Card - and from what I've read, I understand that using:

TWRP = Internal Data Format *ESSENTIAL*

CWM = No need to wipe or format any data (that isn't cache, anyway).

Is that right?

Please also note that my SD Card says it is formatted as sdfat file system... would this cause any issues with CWR?

If sdfat is an issue, could I essentially just copy the sd card data to me pc, format it to fat32, copy data back, and have it work normally etc?

Thanks for any replies.

*EDIT* When I read the SD card on my PC, it says it is FAT32... The SD Card info app I installed says it's sdfat. I'm guessing it means the same thing (FAT32) but not much about this on Google.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] hatsikidee:
Hi, sorry if these are n00b questions, I read the entire thread, but am not sure how it works:

1. If I root using CF-autoroot, will this trip KNOX? If so, would it be possible to just root (no custom recovery) the device without tripping KNOX? (because of the warranty status)

2. If rooted without custom recovery, would I still need to re-apply the stock rom?

3. (a bit off-topic). If KNOX is tripped, does that have any affect on the fingerprint reader? I read that tripping KNOX results in a not working secure folder, and some other things. But I'm not sure about the fingerprint reader.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Utopie:
Don't know about the rest, but my Knox is tripped and FP Scanner works fine. Samsung Health and Secure Folders don't though which is why I'm looking at rooting it to get those working (I bought the phone used and it had already been tripped & network unlocked).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] AK2H:
Flashing recovery and rooting does not wipe any data neither on internal or external.

I think you have a misunderstanding.

Data wipe will only occur if you want to disable the internal storage encryption in order to be able to mount data and internal storage partitions.

3. Fingerprint reader will work flawlessly no mater what even if Knox is tripped or device rooted.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Utopie:
Got damn bootloop!! Grrrrr!!

Well... I think I'll just learn to live without Samsung Health for now... I hate resetting and restoring my phone.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Feanor88:
Hi everyone, I'm also very interested about this. Can I root my girlfriend's A3 using CF-autoroot without voiding warranty?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
No. Samsung's KNOX platform is hard-coded to only allow signed-by-Samsung software modifications. Any firmware component (recovery, kernel, etc.) that is not from Samsung and specifically for the device will trip KNOX, device warranty and advanced security services and apps like Secure Folder. Moreover, it is now said that KNOX is using an e-fuse that will physically burn and thus you will never be able to reverse the device to its original state by software means only.

The firmware has fixed components that KNOX is checking by digital signature at device booting. The user and the operating system have some flexible memory spaces (inside some partitions).

However, rooting, even with the least invasive CF-autoroot will patch a fixed firmware component, thus KNOX will detect it as foreign next time the device will boot.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] User540705538:
SM-A320Y

Tried this on the SM-A320Y

Twrp installed but failed to mount data

Any suggestions?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Menroid:
SuperSu for A320FL Nougat rom quick install!~Tested

For all the A320FL users using an Nougat rom most likely CF-autoroot wont work,

just use the old methode by installing TWRP and then flashing the given SuperSU ZIP!

And the Data mount patch is also working for TWRP, very nice.

Now you are good to go :good:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Menroid:
Please Check here!-> https://xdaforums.com/samsung-a-series-2017/development/recovery-galaxy-a3-sm-a320f-t3562302 :cool:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] BQON:
Succesfully rooted my A3 2017! Thanks for the tut.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zarite:
Succesfully rooted my SM-A320FL using CF-autoroot. It works properly and root is verified.

I've tried to unistall bloatware with "System app remover" but have had no success (Why?).

edit:

I can uninstall packages with ADB from pc.

System app remover still don't work...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] alexj610:
A320FD/S

Hi,

Thank you for you perfect work.

I've a A3 2017 dual sim (A320FD/S), do you think this procedure will work ? I've never rooted any device, can you tell me if all the datas and the phone will be wiped ?

Thanks for your help
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Megani:
Hello,

I have issue rooting my samsung galaxy a3 2017 (sm-a320FL)

If i didn't install the driver, my computer can recognize my phone and I can move, transfer files to my phone without any issue.

However, if I install SAMSUNG_USB_Driver_for_Mobile_Phones.zip (15.3MB), my computeur doesn't recognize my phone anymore...

Consequently, ID:COM icon is still the same.

P.S : I'm using official data cable givem by Samsung and I enabled Debogage USB option, and "Unlocking OEM" is enabled too before I switched off my phone

It's strange because if I removed samsung driver from my comouteur, my phone is recognized again.

Do "Secure Download" have impact ? Do Samsung blocking its phone to customization ?

Do I need install other driver with samsung driver ?

Sincerely,

Megani

---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------

No, your data will not be wiped
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Install the driver then go to device manager. Ensure that the MTP driver is being used when you plug your device in.

If not you likely haven't enabled MTP as a connection option on the device.

Swipe down select MTP.

If not install the MTP driver manually by selecting driver properties of the current driver being used and update it to use MTP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] gone66:
Sorry for silly question guys. I have A320FL, will rooting CF-autoroot via odin trip knox or not? I own galaxy Alpha and it was succesfully rooted, flag remained 0x0. Why asking, beacuse it's business phone, property of the company I work for.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] sciurius:
If it is company property, rooting it may get you fired for damaging company property.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
Not worth it to risk your job to root. Don't do it.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] gone66:
Thanx guys. Should have picked another brand than samsung, which can be easily root and where possible to reverse changes with no trace if it. Any sugestions? Xiaomi, perhaps?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] viewlife:
Rooting and tweaking the phone that your company gave you for jobs, is like pimpimg your ride that company gave you for transportation... Better don't mess out with that phone

Στάλθηκε από το SM-A320FL μου χρησιμοποιώντας Tapatalk
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] fightforfun:
After rooting (with first cf-autoroot method), lag appeared after unlocking phone with pattern. It freezes about 5-6 seconds then unlocks. Any suggestions, why?

A320F/DS Android 7.0
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] fahrul:
Someone mention it because supersu.

Here is the link to thread, its a5 anyway.

https://xdaforums.com/samsung-a-series-2017/help/screen-lag-unlock-t3672720
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] fightforfun:
Already checked it, author of the thread is still looking for solutions, because after installing twrp camera is not working, like in my phone
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It's not TWRP causing the issue. It's SuperSU on both counts.

These issues are already documented in the beta supersu thread.

The fix is to revert to an earlier version if you have lock screen lag.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Rootcarrot:
Same with me, I enter PIN code and press OK, then freezes for about 4 secs
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Is it the same if you root with magisk v14?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] sigbin:
will this work on A3-SM-A320F/DS with nougat?

will it work instead of supersu, ill root it with magisk?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Rootcarrot:
Not sure, I don't know how to root with magisk since I already patched the boot image file, but the thing is I root with cf-autoroot and later unrooted but still experiencing this issue. But everythings ok if I use fingerprint tho ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] nutsh:
I just have rooted my phone(a320fl nugat) with Magisk and the slow/laggly unlock is gone!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] PaowZ:
Thanks for the tuto. I successfully rooted my device (A320F/DS), I've got SuperSU installed. Though, I'm now getting scratchy sound with my A3.. I mean, level buttons don't operate upon volume and sound is scrambled and scratchy, like if sound chipset were driven with wrong sample bitrate, you see ?? Any clue ??

Edit: I reset to factory default (then I've lost all the rooting process (please confirm ?)), still have that crunchy sound. I then reboot into safe mode, played with Accessibility/Hearing settings, reboot again with no luck so far..

Edit2: I'm not sure, it seems PIN unlock lasts much longer than before rooting.. your opinion ??
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] nutsh:
Had same issue. Lag is due to SuperSU and sound I think is caused by the encryption removeal script.

To fix this flash stock firmware - bootloader, recovery everything - make it full stock. Flash TWRP 3.1x is fine. Then clear cache and data for good measure. Boot into os to confirm it is working. Reboot to TWRP and install magisk 14 - this will root your phone. Don't install anything else. Boot into os and install magisk manager - this will be your SuperSU replacement app. Gz you are done. Fully rooted phone with working sound and no lag on unlock
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] PaowZ:
Thanks Nutsh for your reply.

Below what I did to finally make it.

Once I'd softbricked my A3, I couldn't go any further.. I then put the phone into Download mode to flash a stock ROM (AP_A320FXXU2BQG5_CL11883096_QB14314807_REV00_user_low_ship_meta.tar in my case, which is a Nougat ROM). After 2 days of several ways of proceeding, I ended up realizing it was SuperSU that screws my fresh new ROM install.. (lagging, white background with Samsung logo, couldn't set luminosity and many more..). Thing is, I used SuperSU 2.79 as provided in first post of this topic. This release will just won't fit with Nougat. Just get SuperSU 7.82 (latest currently available..) and do you rooting as usual. And this time it'll works fine..

I did this:

- Flash stock rom with Odin 3.12, let it reboot so that it can fill /data with some first stage customizations, but do not start setting your phone yet, just switch it off (specially, don't set a google account or you're doomed..)

- Flash TWRP 3.1.1 with Odin 3.12 so that you gain access to recovery mode and install .zip. (your phone must be OEM unlocked otherwise => FRP lock error !!)

- Reboot into recovery mode and install SuperSU 2.82 and let your phone reboot twice (required by SuperSU install process..)

..now, while booting, you can notice background is black with Samsung logo instead of that white background you'd get with SuperSU 2.79..

- Proceed to your phone settings as usual and check you find SuperSU properly installed in Applications UI.. and enjoy how your Nougat release is not messed anymore..

- Get back to recovery mode and do a hell of backup with all of that..

- Reboot and do your stuff/settings/google account and so on..

Hope this helps.. took me 2 days to figure that **** out.. :eek::eek::eek:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Megani:
Hello,

I need to folow these instructions https://www.drivereasy.com/knowledg...-was-not-successfully-installed-in-windows-7/ ?

Here is a screenshot of my device manager

- When download mode is disabled https://ibb.co/eX5oam

- When download mode is enabled https://ibb.co/dqfwvm

And MTP is enabled on my device :

https://ibb.co/i1qJ86
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] s00L:
Hey so i'm having problems with this one.. this is the error i get <OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> CF-Auto-Root-a3y17lte-a3y17ltexx-sma320f.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

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

I get into downloading mode and all but when entering downloading mode i don't see my phone in my computer so yeah idk please help
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] leo31:
is it working for SM-A320DS/Y ? if cant, please close this thread. the title of this thread are confusing user
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Galaxiez:
My A3 got stuck on the Samsung Galaxy A3 (6)logo after flashing TWRP.Won't go any further neither boot to recover,please help:(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] fahrul:
Flash stock os with odin

---------- Post added at 03:55 ---------- Previous post was at 03:49 ----------

It work, im SM-320DS/Y user,

But im using magisk for rooting, latest supersu had some issue with lockscreen, it lag if u try to unlock with anything except fingerprint.

Sorry for bad english, i wish u understand what i trying to explain above
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] norberto26:
dear All, i have tried using the CF Root method on my Samsung A3 2017, SM-320Y/DS, 7.0 but the sound is gone (no sound whatsoever - calls, notifications, etc.) after rooting using CF Auto Root via Odin. I get back the sound when i boot to stock recovery and reset factory settings.

Please, to anyone who has similar experience or has the same phone - what am i doing wrong? Is the CF Autoroot version not compatible with my phone ? should i down-grade to stock firmware Marshmallow?

Thanks,

Rafael
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] HAMID308:
When no sound, just boot to safe mode then restart to normal mode. Sound will be normal.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] norberto26:
Thanks. How to boot to safe mode?

Ok, got it. Thanks. I will try your suggestion.