yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] steber04:
Or is their some sort of way to temp root , use emoji switcher and then unroot? I know a problem like caring about emojis is small, and although I don't use them much it does just bug me for whatever reason.
[Google Pixel Questions & Answers] carm01:
I am not a big fan of Google's emoji's myself, i use to flash EmojiONe, much better IMO worked great with Gboard on my 5x. I been wanting to do this myself, but I know there is no way to pull this off without out being rooted.

So until Google pulls their head out of the sand and makes changing Emojis more friendlier... Google is not know for catering to the masses like Apple is unfortunately.
[Google Pixel Questions & Answers] steber04:
Thanks for the reply. So is it not possible to root, flash emojione or emoji switcher and then unroot without doing a factory reset?
[Google Pixel Questions & Answers] james59802:
I believe in theory it would be possible to unroot your device easily with SuperSU

by going into settings and selecting the completely unroot option
[Google Pixel Questions & Answers] k.s.deviate:
You could temporarily boot TWRP and flash this

For credit you can find the XDA thread here
[Google Pixel Questions & Answers] steber04:
Thanks.. I went ahead and temp boot twrp and installed superuser with root and was able to download emoji switcher which i used in the past. Worked just fine.. Whether or not i'll still get OTA updates is questionable. I guess i'll wait and see when the next security update comes out.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Unofficial release -TWRP recovery for the Galaxy A3 SM-A320F/FL/Y, Exynos7870

Update 11/9/2017

TWRP 3.1.1-1 MM build released.

Current status: BETA

Features:

MTP

ADB

SEANDROID warning fix

TWRP and Kernel built from latest source

Factory Image flashing(see below)

NTFS support

F2FS support >> To be added

TWRP Official APP support

New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)

Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.

This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.

NOTE: To flash the modem, first it needs to be renamed to modem.bin.img

You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.

Instructions:

Flash with ODIN 3.10.7 in the AP slot.

Put your device in DOWNLOAD mode.

Uncheck Auto reboot.

Load the respective file below into the AP slot and hit start.

After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.

As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.

You should now see TWRP recovery.

NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:

Settings -> Developer Options -> OEM unlocking

AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.

DOWNLOAD:

twrp_3.1.1-1_sm-a320f_11917

To Root:

Flash the latest SuperSU release with TWRP:

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/

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

Boot image patch

no-verity-no-encrypt_ashyx

Twrp Source : https://github.com/omnirom/android_bootable_recovery

Kernel source : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-a320f

PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST

Credits: Me, Teamwin

Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.

FEEDBACK IS APPRECIATED PLEASE.

THANKS.

DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

.

.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Reserved.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
If anyone has successfully installed this, I'd appreciate if they could post the recovery.log so I can look it over.

Log can be pulled in twrp under ADVANCED/SAVE RECOVERY LOG or on a rooted device go to cache/recovery/last_log

Thanks.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Blimey can no-one find the time to help out here? :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] F157:
I'd love to test this, but first I have to figure out why flashfire isn't working for me. :(

It only restarts after 20 seconds or so of white text and black background scrolling down, but no backups are written, only a log.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It's already confirmed working I just need someone to post the recovery.log.

40 downloads since posting but no-one willing. :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
Hello, thank you very much, it worked for me. It was important so I can make a backup of the system. How can I post the recovery log? If you give me the procedure I'll do it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Thanks, you're the only one to have made the effort!

You can save the recovery log from TWRP if you go to ADVANCED> SAVE RECOVERY LOG or you can boot to android and go to cache>recovery>last_log.

Please don't post the output here, post as a file or save the output on pastebin.com.

Thanks.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
Here it is.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Nothing there? :confused:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
Yes sorry, it says network error when I try to attach the file!

---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------

I can send it to you by email
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
You can post it here :

http://www.tinyupload.com/
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
Here you go : http://s000.tinyupload.com/index.php?file_id=17704648158807479484

Thanks for your work. An information about my use : when I made a backup, I got a lot of errors like unable to mount the sd card and in the end "back up failed". But the 3 GB file has been created in the right folder, I think I got my backup.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
No idea what's going on with tiny upload. Clicking the download link just downloads the html data of the web page not the actual file! :eek:

Thanks for trying any way.

By the way you can't back up data until you remove encryption.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
You mean I can't use the save file right now ? How do I remove encryption?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
See the OP.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
I dont get it I'm sorry. I got the save file, you're saying that I can't use it? I should be able to use the file with the restore section no ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
If the data partition is encrypted then it wont have backed up. The rest of the partitions will have been backed up.

This is the failure you saw when backing up.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] patci32:
OK understood. Data partition is the sd card or the internal memory ? I assume that the encryption exists for security reasons. Is there anyway to backup everything without desactivating it?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It's internal memory.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Galaxiez:
A3-A320F stuck on the logo before Samsung...the one saying Samsung Galaxy A3(6)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Before flashing TWRP and no-verity you have to FORMAT DATA. Press wipe then button on bottom right, then type "yes" and swipe right.

Edit

It's after flashing TWRP... of course.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Galaxiez:
I can't enter recovery mode though:/

Do I only flash the patch through TWRP?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hmm, yes patch needs to be flashed with TWRP.

Please follow the instructions in TWRP thread. After flashing TWRP with Odin you have to boot into TWRP immediately with the button combo.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Galaxiez:
Just won't work,thanks anyway:(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Man, your picture shows A310F (if I'm not blind)!!! This here is for A320F. Can't help you with A310F.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] viewlife:
LOL [emoji23]

Στάλθηκε από το SM-A320FL μου χρησιμοποιώντας Tapatalk
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] tomri:
What is the purpose of No-verity-no-encrypt? Is it only needed to access internal data from within TWRP or is it needed for sth. else?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] PrinzWachtel:
I can't download the file. It searches for a Mirror and then says "Error."

Is there an alternative Download somewhere?

Edit: JDownloader did the trick.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Andy Obrianz:
Ask?

This work on samsung galaxy a320y 2017?:confused:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
It should, because the OP says so.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] folusmile:
Great dev, I don't know what I did wrong I can't flash trwp on A320f via Odin it take longer time at the end it won't install give failed message. Pls help me.

OS 7.0

Thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hmm, I used latest odin(. 7) I guess, opened as administrator, turned off my virus scanner, put tar file in AP, unchecked everything (like auto reboot) and it worked.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] folusmile:
I did still not flashing it take ages in Odin recovery hv to removed see attached file
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] folusmile:
It's a320f/DS
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
You're either using a bad/too long cable, have a bad USB or Micro USB port or possibly a bad download.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] folusmile:
Dev thanks for reply.. I got a bad file before the file didn't download very well. I hv to download Again the file. Thanks for ur good work.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Rampage_:
Ok, so a quick feedback.

First of all, I want to thank OP for the hard work, this community exists because the people like you ;)

To the root and recovery, I've got A320FL and I've tried it twice, the recovery works like charm, but the phone does not boot. I've followed the instruction and the thread comments very carefully, yet it just got softbricked. After restoring the firmware, I've tried it for the second time with the same result.

Unfortunatelly I do not know if the phone boots without installing the packages, since I've tried another rooting methot.

Cheers
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hi [MENTION=3384637]Rampage_[/MENTION]

Did you FORMAT DATA after you flashed TWRP?

After that reboot TWRP and flash no verity file, reboot TWRP and swipe right to allow modifications if necessary. Then reboot ROM.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Thanks for your work, do you think make twrp 3.2, this device will get Oreo, if you dont I Can make it, I just wont steal your work on a lot of twrp devices
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] karotrape:
Thx for your job!

Works like a charm on my A320F/DS.

I used Heimdall instead of Odin to flash recovery (I'm a linux user)

How to:

- extract recovery.img

❯tar xf twrp_3.1.1-1_sm-a320f_11917.tar

- reboot in download mode

- retrieve partition table info

❯ heimdall version
v1.4.2
❯ heimdall print-pit --verbose --stdout-errors --no-reboot

- flash twrp (i had to reboot in dl mode second time, because i got libusb error. Seems like only first command is working ...)

❯ heimdall flash --RECOVERY recovery.img

Done!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] theibrohim:
i have one question

will i lose OTA

and how to return oem recovery ??

thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
You will lose OTA unless you have stocks OEM recovery
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lê đình tài:
:rolleyes:u
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] apelamod:
okay can i use latest magisk in steps not supersu?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Yes
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] apelamod:
Okay I just flashed. After everything works my sounds lost or messed up I installed dual speaker mod and now they works also. Themed apps mod section...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] jessican:
Can some 0ne help me unlock my Samsung a320f bootloader. Please!need help.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Gueron:
First up thanks for this work on TWRP. I have a new A320F that I am just getting to grips with. I have been trying to maintain compatibility with OTA, so I only used TWRP to temporarily create a back-up for eventual future recovery from total crash. First time this worked, when I reboot to recovery I had the normal Samsung version and I could OTA update software. But in a recent attempt I end up with only TWRP and no Samsung recovery, so I lose OTA. Can someone upload a stock recovery.img that I can flash back with Odin, then I can completely reset the phone and start afresh ? My current software is A320FXXV2BQG4. I bought the phone via internet and I think originally it is intended for UAE.. Thanks for anyones help. Geuron
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Gueron:
So after much searching around, since Sammobile free server is down for maintenance, I managed to find a close stock ROM to download (2.1 GB) in 3 hrs on my (slow) connection. I extracted the recovery using 7zip as explained here : http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/. Hence I could recover my saved system image with TWRP, and after flash over the stock recovery, and got back my OTA capability ! Phew ! Gueron
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] theibrohim:
will i lose ota and can i use magisk su not supersu
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Yes, you will loose ota with custom recovery and yes, you can use Magisk SU. But only use one root method and not a combination like Magisk and chainfire.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hi @ ashyx, can you released twrp source ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Mohd Masab:
Dear Kindly Upload TWRP Recovery For Samsung Galaxy C5 Pro (SM-C5010).

Device Name : Samsung Galaxy C5 Pro

Model Number : SM-C5010

Country : HONG KONG (TGY)

Android Version : 7.0

Baseband Version : C5010ZHU1AQK2

Build Number : MMB29M.C5010ZHU1AQK2

Please?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
Hello!

I used SuperSU 2.82 SR2 with no-verity-no-encrypt_ashyx

=> Can I update it to SR5 without loosing any data?

=> Can I add suhide-lite to hide it without loosing any data?

Thx a lot!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] theibrohim:
one more question how to restore ota
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Knox1:
[MENTION=4899305]ashyx[/MENTION] can u compile twrp 3.2.1.0

It doesnt support oreo zips

Please
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ebi02:
Hello, please also make version 3.2 thanks

:)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
I'd also like to know the answer to this question. Do I need no-verity-no-encrypt? What's it useful for? Any cons?

Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Well there's not much point in installing a custom recovery if you cannot/do not intend to backup your data. :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Whatever you say. That's not what tomri nor I asked. :rolleyes:

Mine and tomri's question remains unanswered: what is the purpose of no-verity-no-encrypt? What is it needed for?

Somebody else, please?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Well I would have thought it be self explanatory and therefore my previous reply, in essence, answered your question.

From the OP.

What more do you need to know? :rolleyes: :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hi can you release your source ?, I built Lineage 15.1 and my own twrp didn't booted, I want focus on rom, can you do this ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Had it been self-explanatory, no reply, in essence, would've been necessary... unless (probably) you needed it yourself. :rolleyes:

How can I help you further?

Meanwhile, if somebody (ELSE) is willing to shed some real light on tomri's orignial question (https://xdaforums.com/samsung-a-ser...3-sm-a320f-t3562302/post74520338#post74520338), I'd appreciate it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Hi all.

I know that this is not a specific question for the A320F, but, since this device has only 16 Gb of internal RAM, and stock ROM uses no less than 6.2 Gb, there's only 9.8 Gb left for my files. Way too little for downloading navigation maps or storing videos.

Unfortunately, I can't increase my memory space by inserting an external SD card, because then I lose the dual SIM capability (my device is DUOS, A320F/DS, and the external SD slot is shared with the second SIM: either one or the other).

So, does somebody know if there's any way of gaining internal storage (free available space, emulated SD) at the expense of System; or should I have to resize partitions for that (which is very likely way beyond my knowledge)?

I'm planning on heavily debloating the ROM, thus freeing up (I guess) lots of System space. Any way I can use this space for my maps and videos?

Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Wrong thread for your question.

And that no verity thing is as OP says to disable force encryption and mount internal storage, because otherwise you can't do backups with TWRP.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Thx, but

please leave that bit for the moderators to tell. For personal opinions, pm me.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Okay. I've successfully flashed TWRP, rooted and applied the patch. Thanks to the OP for this thread.

Though, I'm facing two issues:

1st: When rebooting after setting request for unlock pattern upon restart to ON, the system wouldn't unlock after drawing (correctly) the pattern: instead, the screen goes black. Pressing home or power I get the dots back for the pattern to be drawn, but then same thing... ad infinitum. Worst yet: it didn't want to power-off either. So I got stuck, and had to randomly press buttons like crazy until it finally rebooted; and when it did... now system opened straight away without asking me for any patterns. I'm sort of puzzled. Needless to say I've deactivated the "secure unlock" for the moment, just in case.

Why may this have happened? Someone else?

2nd: For migrating between (rooted) phones, I normally back-up my apps (and their data) with ES Explorer, then reinstall them (and recover their data) on the new phone (obviously I install ES first of all). I've done it many times with different phones and always worked like a charm. However, now something's going wrong: with the rooted/patched A320F, half my reinstalled apps crash, over and over again, when trying to open them upon being recovered.

Someone else? May this be related to root/no-verity thing? (If need be, I can try to reproduce and provide more specific information.)

Thanks in advance.

[Edit:] I've found a workaround for issue #2: within ES, instead of using the option install app with cached data, first simply install the app, open it, then recover the cached data.

[Edit 2:] As to issue #1, it seems there are problems with screen-unlock in some Samsung A series. So, I guess it's not related with custom recovery, root or verity-encryp, after all.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Ok; so: TWRP, superuser and no-verity patch applied. So far, so good; yet there's a little problem:

I'm experiencing the unlock screen lag issue to the point that I can only unlock using my fingerprint (which is lightning fast); because if I try to unlock with pattern (or PIN) and battery-saver is on, the lag is such that the lockscreen doesn't ever unlock.

Now, searching around I've read that this issue might be related to Superuser and/or no-verity patch; so I think: no harm in trying Magisk.

But for that, I have a few doubts:

1.- For going the Magisk way, do I still need the no-encrypt-no-verity patch? I read people here writing about the "patched Superuser", but I don't know whether, by that, they mean the Superuser+no-verity-patch coupling, or whether the Superuser link in the OP's instructions is somehow already patched, AND the no-verity-patch is yet another patch for attaining a non-encrypted internal storage.

In other words, does Magisk by itself prevent stock's enforced encryption?

2.- Since I'm already on Superuser+no-verity-patch, for going the Magisk way can I simply and merrily now install the Magisk zip via TWRP, or must I fisrt uninstall Superuser? Must I ALSO uninstall the no-verity-patch?

3.- In case I must uninstall Superuser/no-verity (or both), is there any way of doing it without having first to full wipe?

4.- This is merely a curiosity, but of some relevance: According to the OP, the no-verity-no-encrypt patch is needed for preventing forced encryption and making possible TWRP backups; however, according to this post in this thread, TWRP is able to mount and read internal storage, and do backups, without having applied the famous patch. Both assertions seem to contradict one another. Which one is true?

Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] AK2H:
As far as I know the unlock screen lag issue is related to new versions of SuperSU, I'm not sure about Superuser.

1. Magisk has it's own no-dm-verity patch enabled.

2. I really think you should delete Superuser first, not sure about no-verity patch.

3. The best thing to do is take a backup for the (Data) partition in TWRP --> Flash the AP part of the ROM via Odin so you get a clean System and Boot --> Flash TWRP again via Odin --> Format the (Data) partition as instructed in OP --> Install Magisk.zip (now you have root and no-verity patch) --> Restore the Data partition backup.

P.S your internal storage will be wiped during these steps!

4. Disabling dm-verity is mandatory to disable forced encryption and making possible TWRP backups.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Thank you! That's a great idea for not losing data. I'll try it that way.

Btw, I can confirm that the unlock screen lag also happens with Superuser.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
And if you use any Substratum overlays it is not a bad idea to disable them all before doing the data backup you are going to restore.

What I also did was to write all the steps on a piece of paper... helped me a lot.