yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] xdaA3:
Well, first I was sticking to instruction, and tehn just tried : CWM do not propose to use internal storage !

---------- Post added at 02:08 PM ---------- Previous post was at 01:58 PM ----------

Thank you for the precision. I did a wipe and yet still failed to mount/Sd card (I/O error) :(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] xdaA3:
How did you get by the "can't access external storage card" issue ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] methoddon1:
Deodexed files in case anyone wants ⤵️⤵️

https://xdaforums.com/showthread.php?p=71119582

Sent from Galaxy Beast A5 (aka Ferrari) Powered by Stock Rooted Firmware

---------- Post added at 03:46 AM ---------- Previous post was at 03:37 AM ----------

https://xdaforums.com/showthread.php?p=71095046

Sent from Galaxy Beast A5 (aka Ferrari) Powered by Rooted/Deodexed Firmware
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
There wasn't any "can't access external storage card" issue :p

Make sure to format the microSD card properly as FAT32 and have no hidden partitions on it. Use partitioning software like MiniTool Partition Wizard to wipe the SD card and properly format it. I learned this a long time ago with some primitive "recoveries".

[IMG="Mini Tool Partition Wizard - FAT32 SD card example"]http://i67.tinypic.com/2py0opf.png[/IMG]

Also make sure the contacts on the bottom of the SD card are clean, the SD card is placed correctly on the tray (read the instructions) and the tray is properly inserted. Optionally try without the SIM card as is not required. This and make sure you flashed the CWM Recovery that I used (download from my first post).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] xdaA3:
Thank you very much for your help ! I dis all you mentioned step by step, unfortunatly its doesn't work. I guess I will wait for another method if there is one...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] patci32:
Got super Su working but strangly not two reboots as mentioned... Anyway, it's working fine. Any chance to get xposed? To soon?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] jnflos:
Xposed will work fine when they will release a compatibility update. The latest Xposed framework for arm64 wich should work on SM-A320F generates an erorr:

Wrong platform: arm

This file is for arm64

Please download the correct package for your platform/ROM!

SM-A320F is arm64 device so the compatibility issue must be at the ROM level.

So we will wait and see.

The other Xposed framework version for arm installs fine but make the device freeze at boot - because is incorrect version of course.

There is clearly some confusion in the Xposed framework for now regarding A 2017 series ROMs.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] sniff007:
cannot start CWM

Hi,

I cannot make the CWM working. I am able to successfully upload A320F_cwm.tar via ODIN (PDA, uncheck Auto Reboot, uncheck F. Reset Time), got green PASS, but after the reboot (VolDown+Power) and entering Recovery (VolUP+Home+Power), I am getting a blue screen with an "Installing system update..." message and then the original Android Recovery (MMB29K.A320FLXXU1AQA6) appears. Tried several times without success. Any hint, please?

Thanks
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
Not sure about this one, but did you enable the "OEM unlock" option in the "Developer options" Settings?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] patci32:
Just a quick feedback regarding my new phone : I am very happy with it so far. It's my second day with it, the battery is at 39% with 4h45 sot and 1d3h total since unplugged. In a night of 9 hours, the phone just lost 3%.

I have noticed though that wifi is constantly detected as running by betterbatterysats, even if it's turned off. Any idea how to fix this?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
So... the root went smooth at the first attempt... but then, after removing all the crapware, setting up everything perfectly I switched off the development options by mistake, so I switched it on again, BUT that switched off OEM unlock (I checked with another phone)... so at the next reboot I got a:

**** Custom binary locked by FRP lock ****

Crap!

Trying to flash the stock recovery failed.

Now, the Smart Switch app does not recognize the model and serial number pair, complaining that is not in the database, so I cannot initialize the device!

I need the stock firmware of SM-A310Y/DS (it is a dual sim), and flash it with Odin.

No avail on internet, so could anyone post it somewhere?

Thanks!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] methoddon1:
dont say "it's not available" because there is 100 of them on sammobile.com

Sent from Galaxy Beast A5 (aka Ferrari) Powered by ProtaX Rom
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
Tanks but all them are for the A320F, not A320Y/DS
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
http://updato.com/firmware-archive-select-model?q=Sm-a320y&exact=1
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
BIG Thank you!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
Just found... not sure if it works;

http://www.androidinfotech.com/2017/02/root-samsung-galaxy-a3-2017-sm-a320y-marshmallow-twrp.html
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
Is it possible after flashing SuperSU to flash the stock recovery ( I just want to root the phone and don't want to keep a custom recovery ) ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Yes it should work.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
I miss the point why you would do that. Please could you elaborate on the advantages? Thanks.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ponkz:
Nothing.. u cant event get official update

So why bother with stock recovery
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
Why, mainly because there are a lot of little problems with these custom recoveries. I use Flashfire to do all my stuff , and this product really works without any problem. ( If you don't use this great tool from Chainfire , you should. )

What I really would like is a CF-Auto-Root for the A320F so that I will not have to use a custom recovery at all. ( I have posted the request on the CF-Auto-Root thread )
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
You've obviously never had your device crash leaving you with an unbootable system. Especially when you're not at home.

Flashfire won't help you when you can't boot and you will then wish you had a twrp backup to restore.

Zero advantage to having stock recovery on a modified device.

It's a pointless bit of software that can do nothing except factory reset your device.

Also you shouldn't be having issues with any of my TWRP builds. I endeavour to ensure they work correctly, so I'd like you to expand on what doesn't work correctly with the ones you have used?

Regarding cf_autoroot, I could port this, but there's no point, in a few months maybe less it'll probably stop working.

Due to Google's and Samsungs security updates cf_autoroot often ceases to function after a short time and you end up with a soft bricked device if you attempt to use it after one of these security updates.

Chainfire is concentrating his efforts fighting a battle to keep SuperSU updated(the heart of what cf_autoroot actually is) to keep on top of the security updates that break root.

Because of this CFautoroot is always behind in updates, sometimes far behind.

If you want the latest Supersu update then you need a custom recovery if you don't already have root.

Flashfire only works with root.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aconger:
Dear Ashyx, thanks a lot for your comment.

It was the answer for my PM to you.

Best Regards,

Anton
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
Thanks for your comments on my post.

I never manage to get a Custom recovery working with my Galaxy S5 mini , if you look at the posts on several forum you will see that noboby found a fully working recovery for this phone .

The CF-Autoroot worked at first try and even after upgrading to MM two months ago. With Flashfire you can upgrade keeping your root, that's great.

I understand from your post that flashing a custom recovery ( your trwp builds ) and then flash SuperSU is the way to go and will not bring some strange side effects on my A3 2017 A320F . No need to flash the stock recovery on top of that and the nandroid backup and restore will work without problem .

thanks

btw : the Smart View problem is a side effect from the SuperSU or from the CWM recovery ?

Is this your good build for the A320F : https://bitbucket.org/Serverbee/downloadbee/downloads/twrp_3.0.2-1_A3_2017.tar
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
I agree flashfire is a great software and can do pretty much everything you need, but there are certain times when you need a custom recovery. Twrp preferably.

It seems the recovery above is mine but it's not intended for this device? I've just released twrp for this device here:

https://xdaforums.com/samsung-a-series/development/recovery-galaxy-a3-sm-a320f-t3562302

Also what's the smart view issue?

.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dd9:
Why the build of TWRP available for A320* is based on version 3.0.* instead of a more recent version like 3.2.* for example? (I have that version on my S7 since one year). Thanks.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
In the #1 message :

You won't be able to use Smart View (Miracast, project the screen to smart TV)

Envoyé de mon iPad en utilisant Tapatalk
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It's version 3.0.3-1, which is the latest.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
A big Thank you , I received my new A3 2017 saturday and with your help, it is rooted OK ( with SR3-SuperSU-v2.79-SR3-20170114223742 ).

Everything working great and I kept your TWRP recovery on it (twrp_3.0.3-1_sm-a320f_24217).

respect :highfive:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] patci32:
Any chance to get xposed working soon on this device ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Just flash the wanam version of xposed.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] patci32:
Which one is this version, do you have a link ? Are you sure it's working on this device ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Why wouldn't it work on this device it works on devices with the same platform?

You probably need the arm64 version.

https://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

Remember, twrp backup is your friend. ;)

Or you could always go the magisk route to install xposed.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
But after two days , during a phone call, the A320F just crash. It will not boot anymore with a red message : CUSTOM BINARY BLOCKED BY FAP LOCK.

I think , may be it is a security update that brick the phone ( I forgot to block updates after my root )

Impossible to boot the TRWP recovery.

I tried to re flash the recovery but it failed.

The phone was shipped with the A320FXXU1AQA6 firmware ( XEF ) , but I can't find it ( the latest firmware available is the A3 ).

I have to wait for the firmware to be available , and I hope it will be flashable .... :(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Just flash whatever firmware is the latest. Doesn't matter about being the same.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lop1:
But no XEF firmware available yet...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Try another like united Arab emirates until its released.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
I thought frp lock get disabled automaticly when oem unlock gets enabled.

I couldn't find any A320FXXU1AQA6 neither.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Baharul.mir94@gmail.com:
I need to root my phone
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] VictoSab:
[MENTION=8071470]jnflos[/MENTION] : Thanks for the tutorial ! Do you know if is it working on Samsung Galaxy A3 Dual Sim (SM-A320F/DS) ?

Thanks.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
READ the details given in the TWRP link.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] VictoSab:
"SM-A320F/FL/Y, Exynos7870"

I don't see the Dual-SIM "SM-A320F/DS" / SM-A320FZBDPAK ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It's an SM-320F? :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] VictoSab:
You know, when you're about to buy Galaxy A3 Dual SIM, root is a decisive choice, so even if it can be obvious to you, it is important for me to have confirmation.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
You will be fine. ;)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
So does this mean you can root the a3, specifically the duos SM-A320F/DS?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Correct.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
Thanks. Been using s5 on lineage and its really great but miss having slightly smaller phone. Wanted to give the a3 a try.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] rehanraza:
You can flash any single sim firware on dual. I don't have A3 but A5 dual sim from uae orginally came with uae XSG rom, flashed with BTU uk and NEE nordiac firmware and everything perfectly fine
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
Can you only flash stock roms or things like lineage as well?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] rehanraza:
If you are rooted with custom recovery then yes you can install linage os. For stock firmware you can flash any firm with odin
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zarite:
Thanks for the tutorial. Now I have TWRP + root on my SM-A320FL.

I've just one issue related to screenshot: Power and Home buttons don't work. Palm-Swipe gesture works :confused:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] paf22:
TWRP + root here too and no problem for screenshot with power + home button...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
What rom you guys using?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] paf22:
Since there is no custom rom available for the A320F, I'm using the original one.

Waiting for lOS!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] miss_p1nky:
Hello, if my target is installing Xposed, will it be achieved by doing this?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
I thought since had root there were custom roms. Not to sound like an idiot but what is purpose without custom rom?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zarite:
I've uninstalled bloatware and I'm going to install Xposed...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Root is the first thing to achieve to even be able to start development.

I haven't seen any aosp/los attempt for this device yet but I'm sure someone will start eventually. In the meantime you can always debloat, deodex and whatever you want to your stock rom.

Skickat från min SM-A310F via Tapatalk
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mario24601:
Oh got it, thanks!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
Thank you for this method. I'm rooted rooted now, but I keep getting "Google Framework services stopped" error, along with "TouchWiz Home" and whole MS Office Suite "stooped working" errors..I'm guessing I had to clear dalvik/cache before flashing SuperSU zip, but I'm not sure that's the real reason. Any of you guys have suggestion on fixing this issue other than clearing app cache/data or deinstalling/freezing system apps?

Thanks
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zydthegiant:
Need Modded Stock Rom For a320F
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
Is it normal not to be able to mount data in TWRP on rooted A3 2017? Should this be stated in OP "downsides"?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
No, because its fully stated in the TWRP thread.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Helelele:
So any updates if this will work on a SM-A320 FL? Title suggest it works for all "variants", but in the post it only mentions the F one. Same with the TWRP stuff.

Thanks
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] zarite:
Hi. Yes, it works properly on my SM-A320FL
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] The_Freshman:
what is "persdata" in the twrp and why does not it work to mount? Thanks
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] simo_zio:
I've FL version and i can't root it...:(

'

Failed to mount /data (invalid argument)

Failed to mount /persdata (invalid argument)

'
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
I'm on FL version and have root access. You just have to follow the steps. For some reason, data is mountable only after you format data in TWRP, and only in that TWRP session. Next time you're back in TWRP, data is not mountable.

From TWRP thread linked in OP:

To disable forced encryption and mount internal storage:

(Note this MUST be flashed after SuperSU if you intend to root)

1. Boot to Twrp

2. Format Data partition using FORMAT DATA button under Wipe options.

(Note: This will wipe the internal storage)

3. Check DATA is mountable.

4. Install SuperSU (if root is required)

5. Install boot image patch below.

6. Reboot
​
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] The_Freshman:
Ok, and what is the issue with: "failed to mount/persdata"? (sorry for my bad english)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
Apparently, the issue is that TWRP doesn't support Samsung encryption, so data partition stays encrypted... Workaround is to format data in TWRP, install SuperSU zip, than install boot image patch zip provided by ashyx, then reboot. More info in TWRP thread linked in OP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
I intend to try my hand at this today. I will be taking precautionary backups anyway but will my device be wiped if I root it?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
Yes, I'm afraid so. Backup all apps and files. You have custom apps for backing up sms, call log, etc. If you were rooted i would be easy to backup with one app(titanium backup or similar), but without root you will likely have to use more tools to back up.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
Yeah, that’s why I asked. Backing up and restoring on Android is a Herculean task. And I’ve found Titanium Backup to be pretty useless too. When I buy a new phone, I don’t usually root it on the first day (even if it’s possible, which it often isn’t), so the Titanium Backup goes to waste anyway.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Move all personal files to sdcard or PC, then backup with smartswitch mobile to sdcard.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
I found TB useful when switching between different custom roms, and for backing up sms, call log, wi-fi passwords..

Since A3 2017 has Exynos, I'm not sure that we will see any serious rom development here. So yeah, it's kind of useless for me too now. :crying:

Good luck!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
You mean copy the entire folder structure from the built in storage to the SD card, straightforwardly?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
No just your personal stuff you wish to keep.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
I followed the tutorial perfectly and have gotten to the point where I have TWRP installed and am trying to flash the SuperSU zip. En route to this, I had to try installing TWRP using Odin several times, because it would get stuck at the “installing system update” screen and load the stock recovery. After multiple tries, and a bricking scare, I’ve finally installed TWRP.

Now, when I try to flash SuperSU, after it says that it will do the first reboot and unmounts /system, I get three errors:

Failed to mount ‘/data’ (Invalid argument)
Failed to mount ‘/cpefs’ (Invalid argument)
Failed to mount ‘/persdata’ (Invalid argument)

I tried wiping data, cache and dalvik and it shows similar errors. I can reboot to the OS just fine but it keeps throwing up error after error alerting me that the Google Services Framework has stopped and a bunch of other things have stopped. The phone has become unusable and, to the best of my understand, is not yet rooted.

How do I proceed?

---------- Post added at 11:09 PM ---------- Previous post was at 10:15 PM ----------

In trying to troubleshoot it myself, I formatted the /system partition, and I guess that means I've removed the stock operating system completely, and it's still failing to mount the latter two partitions, though it's not giving errors for /data now. Can I use TWRP to install a new OS and get my phone working again?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Soaptk:
Having issues with superSU install, go to install from twrp and stops half way and reboots the phone any ideas what the cause is? any help would be great.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] cowboy_bebop:
It was rooted. You should have checked that before wiping system partition. I kept getting the same errors after rooting. I'm using package disabler and titanium backup to keep them under control... I've tried every possible technique I could find to get rid of them, but with no luck (I think these errors are common with MM). Best chance is to wait for custom rom, or get back to stock rom. I understand your frustrations, but if thought rooting is smooth experience, you were wrong.

You can always flash firmware with Odin and get back on track.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] potyqa:
I think that there are no ROMs for A3 2017 besides the stock one. Sorry
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] natsousa:
Might be a dumb question, but my teacher once told me there are no dumb questions.

The OP says this root method only works with the Exynos CPU. Everywhere I look I see that all versions of the phone(A320F/Y) have a "Samsung Exynos 7 Octa 7870"

Chipset

, and the

CPU

is always listed as "1.6Ghz Octa-Core ARM Cortex-A53." Do phones with the "Cortex" CPU not qualify for this root method? Or maybe the OP meant to say this method works with Exynos Chipsets?

Did the OP include this warning as a joke to mess with poor souls such as myself?

Any help is appreciated
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
CORTEX A53 is the type of core it uses in the SOC, doesn't matter if it's Exynos, Snapdragon or something else.

Samsung simply build the A53 cores into the CPU using their own chipset.

The architecture is the same regardless of who builds the CPU.

Maybe this will help explain : https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] aryayush:
Thank you. I am glad I got confused about whether the device was rooted or not and formatted the system partition prematurely. I was suffering from a ton of Google Play Services errors and other things crashing after unlocking the bootloader, and a fresh install of the stock ROM fixed everything. I then followed the same process for rooting as I had before and it worked just fine, despite the mounting errors.

Rooting the device was a great decision. It allowed me to enabled adoptable storage and install a bunch of really useful apps that I was having to go without before. The 16GB storage would have driven me nuts and led to immense dissatisfaction with the phone if I had failed at rooting it. Being able to Greenify a glut of battery draining system services has also made the already stellar battery seem much more generous.

I only wanted a link to the stock one, which I managed to find. Thank you.