yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hey thanks, works for me as well.

Have tried with that Minimal Stock Oreo ROM.

I flashed unSU.zip by Osmosis

https://xdaforums.com/showthread.php?t=2239421

then this new boot.img and Magisk 16.7 then wiped the caches all in one TWRP session.

Data can be backed up now :good:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Jaxxxev:
Hello All!

nice and helpful guide!

just 2 questions:

it's ok also for device with Official Oreo firmware installed?

in my previous smartphone root, i didn't find the step "check if DATA is mountable" after the wipe data entering first time TWRP.

What does it means?

thanks a lot!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
1. Should be OK

2. When data partition in TWRP does not show 0MB it should be mountable and you can backup.

I use TWRP 3.2 for Oreo.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Harry2o:
Hi McFy and folks,

My phone is an A3 2017 (A320-FL), it had Android 7.0 installed.

I tried to install TWRP (and want[ed] to install LineageOS 15.1) but this is how far I got:

1. I used Odin 3.10.7 to install TWRP 3.1.1-1 (this appeared to have worked, it said "PASS").

2a. accidentally I booted into download mode, where it still said "Warranty void: 0"

2b. booting into recovery brings up TWRP, which is unable to mount /data (and supposedly anything else)

3. I tried to install SuperSU v2.79, I do not remember the exact log outcome (I think it said it will reboot, maybe multiple times, but that was ok)

4. it booted with Samsung Screen, then said there was a failed integrity check and a factory reset had to be done with losing all data (which is ok) and the only button I can press is factory reset

5. it will then reboot into TWRP saying something about factoryReset() corrupt=4, do some logging, then reboots to step 4.)

Steps 4. and 5. will repeat forever.

At this point Fast Download Mode already says "Warranty void: 1 (0x030x)

6. I tried to get back into Recovery Mode manually (turning phone off and booting with keys pressed)

7. Since I remembered that /data could not be mounted, I tried to fix that (maybe I should have done in the first place)

8. Formatting /data with ext4 didn't work, so I tried formatting with FAT which worked, then ext4 again which worked!

9. still steps 4. and 5. are repeating however step 5 (TWRP) will do something with makefs_ext4 all the time (quickly) then reboot into step 4.

10. so I tried to do the same with System-partition: format with ext4 which worked!

11. phone will now boot with "Samsung Galaxy A3 powered by android" screen and stay there forever

11b. if turned off and plugged in with power cord, it will show the circle and lightning symbol (no colors, no percentage) and stay there forever even if plugged off

12. booting into recovery is still possible

13. I wiped System, Data, Cache, Dalvik

14. trying to install lineage-15.1-20180517-UNOFFICIAL-a3y17lte.zip will tell me this:

"E3004: This package is for device: a3y17lte,a3y17ltexc, a3y17ltexx,a3y17ltelk; this device is .

Updater process ended with ERROR: 7"

Looks like my phone lost its identifier. However Fast Download Mode still says model SM-A320FL

Can you help?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
[/COLOR]

Sure, you need to install twrp 3.2 in order to can flash oreo zip :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Harry2o:
Awesome, thanks for the hint. I installed TWRP 3.2.3-0 (with my mentioned existing twrp), after reboot into new twrp recovery I could successfully install the mentioned lineageos 15.1 image and reboot into the new system and follow setup :).

Thank you very much :)!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] pink0:
Is this patched version of twrp available somewhere?

I'm trying this version vith Magisk but with no succes (data is still encrypted) and the same with Mcfy's version
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] foluguy:
Please which method is good to root with Oreo I need a simple guide
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] folusmile:
I was on nougat just updated to oreo.. My FRP lock is OFF. and I didn't see RMM prenormal when I put phone in download mode OEM unlock is enable . I guessed it is safe to root
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Spartan42:
I have a bootloader unlocked, non rooted A3.

Is it possible to boot once in twrp per fastboot

"fastboot boot recoveryfile" and install system-Updates without the loss of data or the original recovery?

And will the system (frp off) still work if i delete system apps like Samsung mail during this step too, booting twrp once and keep the original recovery?

Thank you for feedback.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SnowFuhrer:
Samsung's don't have fastboot.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
As pointed out Samsung devices don't use fastboot.

Also it is utterly pointless to retain the stock recovery on a modified device as official updates won't work anyway.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
With this recovery I don't get options for flashing image to cache, hidden or radio partitions; only to the usual boot, recovery and system. ¿Someone else?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] samuel.caldas:
Works on a300m?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Probably not because it is device specific.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Bhimkarki:
TWRP backup

Hi

Anybody can help :( me i loss baseband & imei.

I am ready to pay for that...

I can share my twrpback data wich is nothig imei and basaband.

SM-A720F i have orginal purchase bill.

Now i am using costom rom without simcard working.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lastsaskatchewanpirate:
TWRP on SM-A320 with working /data (no encryption)

For anyone else struggling with inability to mount data in TWRP, I thought I would share the following info.

The key bit of information I was missing was:

The current latest version of TWRP on the offical site (TWRP for a3y17lte; twrp-3.2.3-0) does not support mounting volumes with "quota" enabled. Therefore if you retain the original stock boot.img which includes quota on the /data partition, it will not mount in TWRP. See https://xdaforums.com/galaxy-s7/help/twrp-issue-t3878565

Additionally the data partition is encrypted on first boot unless you disabled this.

Luckily Zackptg5 has made a package which can perform both actions (remove quota and encryption) and also prepare for installing Magisk. https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389 / https://zackptg5.com/android.php#disverfe. Rename the zip file to include "quota" somewhere in the file name in order to remove quota form the data partition.

The sequence I used (not all these steps may be strictly necessary, this just gives the configuration I wanted):

1. Flash stock firmware; A320FLXXS3CRK3_A320FLBTU3CRL1_BTU, using ODIN v3.13.1. Flash HOME_CSC to wipe data. Allow to reboot

2. Install TWRP using ODIN; flash in AP using older version Odin3 v3.12.10. Untick auto reboot, when complete power off with vol down + power, then force to recovery using vol up, home and power

3. Wipe data

4. Flash RMM-State_Bypass_Mesa_v2 (may not be necessary, but doesn't seem to cause any problems so better safe than sorry)

5. Rename Universal DM-Verity, ForceEncrypt, Disk Quota Disabler to include "quota" in the zip name (download from: https://zackptg5.com/android.php#disverfe)

6. Flash renamed Universal DM-Verity, ForceEncrypt, Disk Quota Disablers; Do not reboot after!

7. Flash Magisk 18.1

8. Flash Busybox (TWRP); https://xdaforums.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

9. Reboot to system

10. Set up phone and restore backups

11. Install Magisk 18.1 manager app

Hope this helps anyone looking for information on why data cannot be mounted in TWRP for this phone!

Jack
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] AK2H:
[MENTION=9836525]lastsaskatchewanpirate[/MENTION]

It worked!

But for me I flashed patched-boot.img created with Magisk Manager then flashed Zackptg5 zip file, because Magisk-18,1.zip resulted with error.

Thank you very much I have been waiting for so long for this to be possible.

[MENTION=7726355]Pat750[/MENTION][MENTION=4222902]zogoibi[/MENTION][MENTION=4602076]kaizokan[/MENTION]
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hey thank you very very much. Gonna test when there is free time.

Actually HOME_CSC does not wipe data but keeps it. Flash CSC without HOME to wipe data. :) But I think it does not matter for this procedure.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lastsaskatchewanpirate:
Oops, knew one of them wiped and one of them kept the data!

Good job it was this way (didn't wipe the data when i expected it to) instead of the other way around when i would expect it to keep my data and then find out too late that it was gone...

I will try and remember this for next time :o
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hey [MENTION=9836525]lastsaskatchewanpirate[/MENTION] thanks again for that find and your detailled steps.

I started with restoring a TWRP backup that was made right after flashing with odin (A320FLXXS3CRK1).

First I tried with april version of the zip (Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip) made by Zackptg5 for Magisk 19.

But no matter what I did it didn't work, everytime TWRP showed 0 MB after first boot (with quota added). I also tried patched boot.img created with Magisk 19.

Then I tried Disable_Dm-Verity_ForceEncrypt_04.03.19.zip with Magisk 18.1 and it worked right away.

My steps:

1. Untouched boot and system partition (I did swipe right after flashing TWRP)

2. Format data (where you type "yes")

3. Reboot recovery

4. Flash Disable_Dm-Verity_ForceEncrypt_04.03.19.zip with "quota" added "Disable_Dm-Verity_ForceEncrypt_quota_04.03.19.zip"

5. Flash Magisk 18.1

6. Wipe cache and dalvik (I allways do that after flashing or updating Magisk)

7. Boot System, do setup and flash Magisk Manager apk manually

I skipped step 7, forced reboot to recovery after welcome screen and restored a backup of data partition I made earlier.

I didn't need to flash busy box and I didn't need the patched boot.img created by Magisk like [MENTION=5752348]AK2H[/MENTION].

Before all that I used the above ROM with ashyxs kernel, but after flashing Magisk 19 device sometimes wouldn't boot anymore, no matter what I tried.

I'm still so happy to use the new kernel, testing Magisk 19 will have to wait...

Magisk 18.1 seems to work, but it's not my main device and time for testing is limited.

Thanks guys...:good:

Edit 1. In step 5 also flash RMM, just in case.

Edit 2. Upgrading to Magisk 19 also works. Did it a few days later.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] G1__User:
Thank you all for these detailed descriptions!

Unfortunately, it is not completely successful with my A320FL:

It encrypts my data partition every time it starts

Probably that's because I'm using this very new firmware A320FLXXS9CTK1 from October 28, 2020.

(Unfortunately I can't get back to older firmware with Odin as I get these annoying version errors: Kernel Rev. Check Fail. Device: X, binary: X)

My steps:

1. Flashing firmware A320FLXXS9CTK1

2. Flash TWRP twrp-3.5.0_9-0-a3y17lte.img.tar (and also tried twrp_3.2_recovery_a3y17lte-050318.tar and many others)

2. Format data partition (entering "yes").

3. Restart the recovery

4. Flash "Disable_Dm-Verity_ForceEncrypt_quota_04.03.19.zip"

5. Flash Magisk 18.1 (and also tried Magisk-v20.4.zip and a few other versions)

6. Clear cache and Dalvik

7. Boot System, Setup and Flash Magisk Manager apk manually

8. Have root access, good!

But this phone is always encrypting data which prevents me from doing TWRP backups!

Any ideas?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
I'm really sorry to hear that the above method doesn't seem to work for S9 firmware.

It sure worked for me with S5 firmware... but you can't go back now.

But your steps seem to be correct.

The last people who were playing oround with this (in the Oreo minimal thread) were @grampa2222, @Saeka and @starbright_ maybe you guys can help here?

My wild guess would be try a newer dm-verity file or use OrangeFox recovery?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] G1__User:
Finaly I managet it with OrangeFox-a3y17lte-stable@R11.0_1.zip

Thank you for the tip!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] jot.zet:
Hello,

i have a problem to flash twrp by odin on the A320FL. Bootloader ist unlocked und usb debugging on. I used odin 3.14 and the twrp 3.5.2_9 .tar file for a3y17lte.

odin stucks on "get PIT for mapping" (lock also at image)

before that, i tryed to flash via heimdall and fastboot. But it stoped always after some percents (11% or 22%). Then i got the "no command" screen and i had to restore the bootloader. So i tryed the way via odin...

Now i think about to use the PIT file in odin, that i found on "https://www.full-repair-firmware.com". But i'm affraid to brick the phone...

Are you have some hints for the procedure. My aim is to flash lineageos 17.1 ...

Thanks for all help

jot.zet
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
Hello

Does ADB work in this version, so I can connect to recovery from PC and mount internal FS?

That is all I need.

Thank you
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Should do. You won't be able to mount internal storage unless you format. See the OP.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
What do you mean "Should do" - you do not know, or no one tested it

Also, what do you mean "unless you format". Format what - internal FS?

Is it not possible to mount / to /mnt?

Or TWRP via adb doesn't see / or /mnt?

Can you be more specific, please?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
I don't have this device so I can't confirm if things work if no one can spend the time to report.

You will see I ask for feedback but no one does.

However there's no reason why ADB shouldn't work.

Internal storage cannot be mounted because it is encrypted.

To mount it, it needs to be FORMATTED and then my boot image patch applied.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
Thank you for your quick answer.

If all internal storage is encrypted, we can relatively safely format only DATA (because it can be restored later)

But what does your boot image patch do? Decrypt internal FS and never encrypts it again?

I check your boot patch - it turn of encryption.

And as long as I understand FS remains unencrypted.

So I hope on the next reboot it will be possible to see and mount it to somewhere?

That is why it is necessary to keep "UNLOCK BOOT" always on - because boot is not original

Am I correct?

Thank you in advance.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
The Data partition needs to be formatted to remove the encryption as twrp doesn't yet support Samsungs encryption method.

Formatting will wipe the internal storage after this the partition will mountable by twrp or adb if you prefer.

To prevent the partition from re-encrypting at boot the patch needs to be applied before hand.

After that it will stay unencrypted as long the boot image isn't replaced.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
Thank you very much for your explanation.

What about SYSTEM partition?

Can I mount it?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Yes, system is not encrypted so no issues.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
Great, because I only need to patch one file in SYSTEM and nothing else.

Thank you
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
Do you have any plans to update your version based on 3.1.0-0?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Possibly.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] badablek:
Thanks for your hard work ashyx

I Bought one A3 2017 SM-A320FL today, and root was absolutely needed for me (at least to be able to automatically put the phone in airplane mode with Llama and remove all those crappy Samsung bloatwares)

At my first attempt (I promise I wasn't drunk), I did not flashed the good one (I don't even remember where I have downloaded it)...my new phone was stucked with Power+Volume Up + Home :eek:

After a little time to find how to power off a stucked Samsung device :confused: (Power+Volume Down) and check my setup, I reinstalled your version of TWRP with Odin 3.1.2.3, flashed the latest SuperSu...and everything worked as expected after some reset (I had at least 5 or 6 quick reset), wonderful ! :victory:

ps : I had to format Data partition to gain access to it, like you said, but I did not have to flash your boot image patch...maybe because I did not enabled any protection after the factory reset ? (I don't care about this stupid knox nor any other "protection" bloatware).

TWRP is really a must-have on any SM-A320FL device. Thanks again...too bad you don't have a lot of feedback on it.

Now I have to seek some info on knox, like how to fully wipe it (if it's even possible).
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
recovery.log

Hello ashyx,

Thank you for your work which I appreciate a lot.

You can find my recovery log on pastebin as: MzLq2NSk

(I cannot post an outside link since I haven't post 10 messages on xda forum yet...)

Don't hesitate to ask me if you need further information :D

I really appreciate your work and if I can do anything that can help you to improve my A3 2017, I will be very pleased to ;)

Cheers
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Thanks, very helpful. There's a couple of little tweaks I can make which I'll include in the update.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] nimnull:
I tried to download

twrp_3.0.3-1_sm-a320f_24217.tar

from

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

And I got only: OOPS! no mirrors found.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
Just try again. 8 mirrors found here.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] VictoSab:
Thanks you very much for your job, all work fine one my Galaxy A3 2017 SM-A320FL.

The recovery log is here.

Compare to my old Galaxy S4, the vibrator is very strong and variable, too bad... the only defect I find one this amazing A3, someone know how can I adjust the intensity ? :confused:

---------- Post added at 11:04 PM ---------- Previous post was at 11:03 PM ----------

Have you tried to disable AdBlock Plus or similar ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cast-away:
Hi. It doesnt work for my a320fl. Recovery done with odin withuot error and restart normally. But when I went to the recovery nothing change I saw the stock samsung recovery there not twrp
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cast-away:
Its work for me after I following this step

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.

thank you a lot
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Thanks for clarifying that. Im so fed up of repeating it myself, I've given up. :good:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] poltrob:
Thanks a lot, brilliant work

Followed your work every step and it's working like a charm !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] balans:
twrp works !! but i`m having trouble mounting /PERSDATA wich gives me errors , i wonder if you`re patch will have anyeffect
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It seems to be a protected partition. Could be encrypted. There's not a lot I can do about it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] p00i:
Hi

Thank you very very much for your work. It is really nice that ppl like you actually invest their time to help develop and share stuff for phones they don't even own themselves.

I followed your manual at the start of this thread. But I can't get the TWRP recovery img starting properly. I get a warning on the phone saying "recovery is not seandroid enforcing". Can you (or anyone else) help me out on this one? I didn't find anything that helped me with this (with respect to my phone, which is a A3 SM-A320FL (2017)).

As suggested in your manual, I used ODIN 3.10.7, unchecked the "auto reboot" option (leaving all other options as was when starting Odin => only the "F. reset time" was checked when I started the flash process). After Odin stated "PASS" I rebooted to the recovery img as suggested and ended up seeing the above mentioned message above the samsung logo.

This is what the log tab of ODIN says:

<ID:0/016> Removed!!

<ID:0/017> Added!!

<ID:0/017> Removed!!

<ID:0/017> Added!!

<ID:0/017> Removed!!

<ID:0/017> Added!!

<ID:0/017> Removed!!

<ID:0/016> Added!!

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

<ID:0/016> File analysis..

<ID:0/016> SetupConnection..

<ID:0/016> Initialzation..

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

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

<ID:0/016> SingleDownload.

<ID:0/016> recovery.img

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

<ID:0/016> RQT_CLOSE !!

<ID:0/016> RES OK !!

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

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

<ID:0/016> Removed!!

<ID:0/017> Added!!

<ID:0/017> Removed!!

<ID:0/017> Added!!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] balans:
Did you oem unlock ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Something doesn't seem right, why does your device keep connecting and disconnecting, bad USB cable?

Also you shouldn't get the "recovery is not seandroid enforcing" with the TWRP recovery image. Are you sure you've flashed the correct file?

Which firmware build are you running?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] trytoshakeme:
TWRP version issue with A320FL ?

Hi ! Thanks for all the great work. I have installed this TWRP version on my SM-A320FL (purchased in France) in order to root my device (I used Odin). However I am not really confident for the next steps as TWRP does not seem to work properly : it fails to wipe partitions or do a backup.

When I do a backup, for example, the top title says "Backup complete. Failed", and the detail report starts with two identical yellow lines : Stock theme version does not match TWRP version.

Then, in red : E:String resource 'data_backup' not found. Using default value.

Could not mount /data and unable to find crypto footer.

Etc.

I took pictures of the error messages displayed and saved the log (although I don't know where to find it). Please tell me how I can proceed to make them available to you !

Best,
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Don't worry about the 2 warnings regarding the version, they are erroneous and won't affect anything.

The backup error and other warnings are caused by the data partition which is encrypted. You should read the OP, it explains what you have to do.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] trytoshakeme:
The warnings cooled my enthusiasm down indeed ^^ Especially since the nandroid backup does not work... Do you mean I should not care about it and format the DATA partition ? (as the original post says)

(Of course I understand the risks, but I just want to make sure something is not fundamentally wrong before I proceed)

Thanks,
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Just format the data partition and apply the boot patch all in one session.

Reboot, make a backup, leave out /PERSDATA it can't be backed up as it's protected.

If you encounter issues restoring then save the recovery log and post the file so I can check it out.