yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] trytoshakeme:
Thanks, I see. Just one last question : should I flash SuperSU and then do the format/patch operation right away or should I reboot first ? In that case should I reboot system, shut down, then reboot in recovery OR reboot directly in recovery ? I am not so sure about the exact sequence order in the original post :

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

"Must be flashed after SuperSU"

But then "Install SuperSU" (my understanding is that flasing and installing are the same, but I may get it wrong)

Sorry about these details, I'm just trying to make sure we have a clear sequence of operations :) Can't wait to proceed and give you feedback !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
You need to follow the step by step instructions exactly as posted.

If you need to reboot it will state so.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] trytoshakeme:
Update :

Followed all the steps one by one and it worked perfectly fine. A few loops at reboot (as the patch mentions it), but didn't take more than 10 minutes total. Now reconfiguring my device and getting rid of bloatware.

Thanks a lot Ashyx !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HurlingFrootmig:
Apparently I bricked mine trying to flash this.

It's a SM-A320F/DS (dual sim variant). It's not going past the "SAMSUNG Galaxy A3. POWERED BY android" screen, anymore. Before flashing, I even checked the newest official 6.0.1 firmware that I just got offered for the build.prop , which says

ro.build.flavor=a3y17ltexx-user

ro.product.model=SM-A320F

ro.product.name=a3y17ltexx

ro.product.device=a3y17lte

I can still get into ODIN mode, which shows:

ODIN MODE

DOWNLOAD SPEED: FAST

PRODUCT NAME: SM-A320F

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

FRP LOCK: OFF

Secure Download: Enabled

CCIC =

WARRANTY VOID: 1 (0x030c)

RP SWREV: B:1 K:0 S:0

ODIN flash always goes through without a hitch and finishes with a green PASS:

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1100)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> RQT_CLOSE !!

<ID:0/003> RES OK !!

<ID:0/003> Remain Port .... 0

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

When trying to boot into recovery using VolUp+Home+Power I only get until the above screen.

Any ideas?

Cheers,

H.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Which firmware build are you running?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HurlingFrootmig:
I did an OTA to A320FXXU1AQD1 yesterday.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Can you post the recovery.img?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HurlingFrootmig:
It's here: http://s000.tinyupload.com/index.php?file_id=32481212651206871128

BTW, I managed to get the thing back to factory status by fully flashing the stock rom. Being able to root it would be nice, though, after all.

H.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Hi ashyx,

First off, many many thanks for the root! Successfully rooted my SM-A320F/DS following your guide, flashed the no encyption/verity patch and SuperSU. This is on stock A320FXXU1AQD1 rom, used Odin v3.12.5.

Done this a few times now, reflash stock rom and re-rooting, and successfully managed to install Magisk/Xposed+SuperSU aswell. Havent had an Android device for many years now.. so alot of trial and errors.

EDIT: By the way, any logs you need for your work, feel free to ask. I'll gladly oblige with information/logs you need to work out any bugs/feature upgrades.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] NiEb:
Hello,

i can't install Magisk/Xposed.

mounting /PERSDATA invalid argument. data is mountable.

Thanks for the good work.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Mounting /PERSDATA has nothing to do with your issue. Its a protected partition so cannot be mounted.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] NiEb:
ok,

thanks. :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kaizokan:
Thanks for this! :good:

I have not done much with it yet, only a backup (System image) and after that Zip install of SuperSU.

Here you can find the log file so far.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
thx! will tryt this soon

is there already a custom rom for our phone?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
Successfully rooted my SM-A320F/DS .now why i cant use otg usb flash?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
Thanks man, it worked!

"To disable forced encryption and mount internal storage"

what does this mean?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
Not too busy here
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] 1806:
A3 now running on Android 7.0 Nougat, any root for it?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
I'm downloading new Russia nougat rom ,will try rooting then report here.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] 1806:
This TWRP and SuperSU and Magisk works fine on Android 7.0 Nougat at A3 2017
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
where to download it?

i have root and internal update doesnt allow updating :(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] notthesun:
sammobile
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
These TWRP & root procedures works fine on new Android 7.0 Nougat .
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] notthesun:
sure it works but you will lose camera and softkeys backlight function...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Which version of SuperSU are you using? You should be using the latest V2.82. If you are using that version then you need to report that bug to Chainfire.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] notthesun:
my fault... i'm using 2.79 version.

where to download 2.82 version? EDIT : I've found it
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It's linked in the first post.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] notthesun:
Confirm 2.82 works really good.. thanks mate
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
there's only 6.0.1

https://www.sammobile.com/firmwares/galaxy-a3/SM-A320FL/
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nyllep:
Hi, are there source code for this port?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Since I'm porting LineageOS to this device I'd very much like to have a look at the source code of this.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Devilix:
I'm the only that get these errors? I have SM-A320FL, on stock samsung rom (even because custom type does not exixst for this model).

The recovery doesn't flash nothing, neither Magisk zip file.

Where i'm wrong? In this way i can't root the phone...

I have followed, read and read more times the instruction of the OP, but nothing changed...

Please, help me. Thanks!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
You can't have read the OP properly as you state, as it's posted quite clearly why you are getting the mount /data issues. I shall not repeat myself as it's there for you to read in the OP and several times posted in this thread.

/PERSDATA has also been mentioned several times. Ignore it, it's irrelevant. It doesn't mount because it's a protected partition.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Devilix:
[MENTION=4899305]ashyx[/MENTION] are you talking about this?

Edit: Solved! Thanks! ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] MaDaLiNoSt:
Works on nougat bootloader?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
yes
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
[MENTION=4899305]ashyx[/MENTION]

There is Nougat kernel sources at samsung's opensource site. Is it possible to bump your twrp up to 3.1.1 version along with new kernel sources? Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] awadh730:
please help

please help i need twrp for A3 SM-A3009
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] broky:
[MENTION=4899305]ashyx[/MENTION] and all

can t mount data in any case,and i think that i follow the steps as OP stated.

it just does not give the option to mount data.

any instruction on this,how you solved it guys?

should i flash the Boot image patch before mount and format data?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
first format data and then without rebooting it gives the option to mount data.so you can flash the Boot image patch.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] broky:
i think that this is exactly what i m doing but i never have the ability to format data.

i ll give it more tries,thanks.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
why you can't format data? you have important data in it? so that's better to do this after flashing new fresh rom.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] broky:
for some reason i can not spot,it does not allow me to format data,of course i want to do it.

failed to mount data/invalid argument is the message TWRP gives me
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] HAMID308:
which version of TWRP you are using? and exactly you type "yes" in format data dialog?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] broky:
just realized my mistake!

i was trying to format data from advanced wipe section of TWRP,that was not the right option.

i needed to type "yes" in format data dialog

..

solved,thanks a lot:)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] #Ozomatli:
Version 1.14
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
[MENTION=4899305]ashyx[/MENTION]

Since seems that you are not so interested at supporting of this recovery, please can you open the sources of all this project or at least device tree? You can save a lot of time for people by this gesture of good-will. Thanks!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
Anyone who has android 7 already?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It will be available at the weekend.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Clóvis sky:
I would like to download an xposed framework - (**Mod edit - google translate**)

Gostaria de baixar uma xposed framework
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
JFYI: "Source code of a healthy human" from here

SOURCE CODE

TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)

Device tree: https://github.com/jcadduono/android_device_samsung_j7xelte (android-6.0)

Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)

And back to this thread: your sources are still not compilable into your recovery without device tree.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Hi everyone,

I just thought I would post a clarification on what is required as far as source code on XDA.

Normally a rom or kernel needs the kernel source provided as it is covered by the GPLv2 license. Recoveries do not need the source code to be provided, as most of the code needed to make a recovery work is not covered by GPL.

If the OP decides to share his work and source code to get a working recovery, it would be highly appreciated, however it is not required by any license or rules on XDA.

Thanks

noppy22
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
Fair enough. Thanks for clarification.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
Switch from SuperSU => Magisk?

Hi everyone,

I'm using this release with SuperSU since months now. Thank you again to all the people who make it possible!! :D

I just discovered the existence of Magisk, which could get ride of my impossibility to use Snapchat for example (such app whose use is impossible/forbidden on rooted devices).

Question: Is there any way to install Magisk on my A3 without loss all the data/without operating the instructions describe in first post?

Many thanks in advance,

Cheers :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
UPDATE 11/9/2017:

TWRP 3.1.1-1 released, just need testing before adding to the OP:

https://www.androidfilehost.com/?fid=817550096634798596

.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
There is no "persdata" block device.

I'm using this recovery.fstab:

/boot	emmc	/dev/block/platform/13540000.dwmmc0/by-name/BOOT
/recovery	emmc	/dev/block/platform/13540000.dwmmc0/by-name/RECOVERY	flags=backup=1
/system	ext4	/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM
/data	ext4	/dev/block/platform/13540000.dwmmc0/by-name/USERDATA	flags=encryptable=footer;length=-20480
/cache	ext4	/dev/block/platform/13540000.dwmmc0/by-name/CACHE
/hidden	emmc	/dev/block/platform/13540000.dwmmc0/by-name/HIDDEN	flags=backup=1
/modem	emmc	/dev/block/platform/13540000.dwmmc0/by-name/RADIO	flags=backup=1;display="Modem"
/efs	ext4	/dev/block/platform/13540000.dwmmc0/by-name/EFS	flags=backup=1;display="EFS"
/cpefs	ext4	/dev/block/platform/13540000.dwmmc0/by-name/CPEFS	flags=backup=1;display="CPEFS";subpartitionof=/efs
/m9kefs1	emmc	/dev/block/platform/13540000.dwmmc0/by-name/m9kefs1	flags=backup=1;subpartitionof=/efs
/m9kefs2	emmc	/dev/block/platform/13540000.dwmmc0/by-name/m9kefs2	flags=backup=1;subpartitionof=/efs
/m9kefs3	emmc	/dev/block/platform/13540000.dwmmc0/by-name/m9kefs3	flags=backup=1;subpartitionof=/efs

Do you need 'ls /dev/dev/block/platform/13540000.dwmmc0/by-name' output?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
No, that isn't the fstab provided with the recovery.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
Of course it isn't. It's my own fstab, not yours.

Your fstab has "persdata" record, which refer to wrong block device
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Then I shall remove the entry from the FSTAB.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Kot_Ik:
Nope. You just should modify it, if you want to use it.

Look here:

a3y17lte:/ # ls -al /dev/block/platform/13540000.dwmmc0/by-name
total 0
drwxr-xr-x 2 root root 520 2017-09-11 16:43 .
drwxr-xr-x 4 root root 640 2017-09-11 16:43 ..
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 CACHE -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 CP_DEBUG -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 NAD_REFER -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 PERSISTENT -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 STEADY -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 SYSTEM -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2017-09-11 16:43 USERDATA -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2017-09-11 16:43 m9kefs3 -> /dev/block/mmcblk0p7

Not "PERSDATA" but "PERSISTENT". That block device neither formatted in ext4 nor vfat or smth else (may be i missed something when tried to mount it). Can't understand it's internal structure, and don't know whether it shoud be backed up.

Also (as far as i know) EFS should be joined with CPEFS and all m9kefs* partitions (subpartitionof=/efs, as i've metioned before) when are backed up. You can refer to j7xelte device tree by jcadduono which has pretty same hardware
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
I use whatever is in the stock FSTAB. If extra partitions are required as you have pointed out and they are essential then I will add them.

It isn't actually necessary to make all EFS partitions into sub partitions. They are still separate partitions either way, just combined under one name.

I'm not even sure if these m9kefs partitions contain any viable data.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SmartDroid01:
Twrp Recovery 3.1.1-1 for sm a310f please?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Thanks for the update! Tested with latest stock firmware (Nougat 7.0).

Install had one hicup which I hadnt seen in the earlier version, added snipit from recoverylog:

Running Recovery Commands
I:command is: 'install'
I:value is: 'CACHE:recovery/sec_csc.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Trying to find zip 'CACHE:recovery/sec_csc.zip' on '/data/media/0'...
I:Looking for zip at '/sec_csc.zip'
I:Looking for zip at '/data/media/0/sec_csc.zip'
I:Trying to find zip 'CACHE:recovery/sec_csc.zip' on '/external_sdcard'...
I:Looking for zip at '/sec_csc.zip'
I:Looking for zip at '/external_sdcard/sec_csc.zip'
Unable to locate zip file 'CACHE:recovery/sec_csc.zip'.
Installing zip file 'CACHE:recovery/sec_csc.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: Unable to open 'CACHE:recovery/sec_csc.zip': No such file or directory
Failed to map file 'CACHE:recovery/sec_csc.zip'
Error installing zip file 'CACHE:recovery/sec_csc.zip'

Boots up fine, dunno what that error means. One thing, which might not have anything to do with your root, but thought I'd ask anyways. Theres a lockscreen unlock delay after rooting, which isnt present before, any ideas why that is?

Thanks again for the work you're doing!

best regards

yass
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Wipe your cache to get rid of that error. That's the remainders of a previous install of something else.

If your suffering the lockscreen delay use supersu V2. 79 instead.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Ah right, that did the trick.

Thanks for the tip with supersu 2.79. Works, but sadly I need Magisk installed, and the two together dont work. Back to MM then.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] AK2H:
By the way if you installed Magisk you no longer need SuperSU or data partition force encryption disabler,

Because these functions and futures are already available and integrated in Magisk.

You even get a much more compatible Xposed created by the same Dev of Magisk.

P.S. Magisk Superuser doesn't slow down the screen unlock unlike SuperSU :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pondera:
This is wonderful, thanks. I have 2 questions.

- Does firmware changes anything? For example will it root on Nougat?

- This one might be kind of stupid but I see there are newer versions of Odin. Is that version on purpose? New ones may not be cutting it perhaps. Or can they be used?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
hope soon this will be available for Android 7!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
I installed Android 7. Now i wanted to root so i flashed twrp 3.1.1.1 with latest Odin. Now, when android starts and i need to enter my pincode, it says it failed intergrity check and i need to reset. When i click reset it restarts and same thing happens? :( Any ideas what to do now?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Remove encryption and flash patch.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
crap, i did it already but i forgot to format data.. and im normally always so careful. Now it stucks at Samsung logo. Cant even turn it off. :eek:

With volume down and power it reboot but i get same thing...

update:

im back in Recovery. But i cant format Data and i also cant mount it...what to do?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
FORMAT DATA not WIPE
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
ah crap... :)

thanks man, it worked!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lahsan:
[No message]
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
I got a message from Root Uninstaller. My phone is rooted, but it has no Write access to System folder.

How to fix this?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ScottHW:
Security / Encryption ?

(EDIT: This post is not correct. I confused the impact of Root and TWRP on encryption. See two posts down for further details)

[MENTION=4899305]ashyx[/MENTION]

Thanks for the work you've done to make this custom recovery available for us all. I have SM-A320Y, and just manually updated to Android 7.0 Nougat. I also wanted Root, and TWRP.

It seems after I used ODIN to flash CF-ROOT and then TWRP, the security / encryption changed. When I set up the phone, I enabled " Secure Startup" (see screenshot). That works as expected; each time I rebooted, I would see a prompt to unlock the encryption (I currently have a Pattern lock), followed by an spinning lock icon.

After flashing TWRP, the phone doesn't prompt to unlock.

The Settings option "Lock Screen and Security > Secure startup" is gone...

... but there is now a choice for "Encrypt device"

... which I did try, but cannot figure out how to verify whether it is working.

Is this expected behavior for a non-stock / custom recovery?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It's not something I've come across before. I wouldn't have an encrypted device using custom recovery anyway as you won't be able to access the data partition via twrp.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ScottHW:
I've been continuing to learn about encryption, and I think my original post was mistaken (I'll edit it after this, don't like propagating misinformation.)

When flashed on a stock phone, TWRP does NOT effect the encryption, Secure Startup, etc.

However, as you point out, if the data partition is encrypted, custom recoveries like TWRP cannot mount or access it, which severely limits the abilities of the recovery (e.g. can't flash .zip files)

Flashing CF-Auto-Root does effect encryption.

The install instructions are do this

- before initial setup of the phone (before the data partition is encrypted)

- immediately after wiping (formatting) data & cache (really should say FORMATTING, because a Wipe doesn't actually remove the encryption)

I did Root and TWRP back-to-back, and apparently confused which had impacted encryption.

I'm reading more about the tradeoff between root / custom recovery / encryption, and which are mutually exclusive.

These both suggest you can root, disable Superuser, encrypt, and then re-root

https://www.theandroidsoul.com/encrypt-android-root/

https://www.reddit.com/r/Android/comments/4110l3/encrypting_a_rooted_phone_running_android_601/

... but both are from a year ago, may or may not be applicable with Android 7 Nougat. And the severe restrictions in using a custom recovery would still seem to apply.