• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017)

Search This thread

NiEb

Member
Feb 3, 2016
26
8
I'll try :)

edit 1: it works
@ashyx,
thank you ! Magisk works, data is available.

edit 2:
SecurityLog Agent -> colour orange- > Device is not authorized :( please restart


 
Last edited:
  • Like
Reactions: Pat750

Pat750

Senior Member
Sep 12, 2016
593
258
I'll try :)

edit 1: it works
@ashyx,
thank you ! Magisk works, data is available.

edit 2: device safety -> orange not authorized :( please restart
Hey thanks for testing.
But I don't understand edit 2, is orange your carrier? Or is the message in orange colour?
Maybe that message can be ignored because it is normal when you flash custom stuff on the phone that it says not authorised? I remember having that message with custom ROMs and it may affect banking apps or pokemon. But I don't use those.
Does the ROM function normally?

Sent from my cigarette break.

I see you edited edit 2, so do what ashyx says.
 
Last edited:

NiEb

Member
Feb 3, 2016
26
8
Just disable Knox and the securitylogagent.

yes, securitylogagent is disabeld (Titanium)
warnung is deleted :)

ROM function normally,
but magisk saftey net status -> the answer is invalid

edit 1: restore older data backup - > works
edit 2: Warnung in Device Maintenance --> Device security = Device not authorised
(knox and security logagent are frozen with Titanium)
 
Last edited:
  • Like
Reactions: Pat750

Jaxxxev

Member
Jan 18, 2014
17
0
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!
 

Pat750

Senior Member
Sep 12, 2016
593
258
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!
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.
 
  • Like
Reactions: Guyllheaume

Harry2o

New member
Aug 18, 2018
2
0
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?
 
Last edited:

McFy

Recognized Developer
Aug 31, 2016
549
1,473
19
Angers
mcfy.fr
[/COLOR]
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?

Sure, you need to install twrp 3.2 in order to can flash oreo zip :)
 

Harry2o

New member
Aug 18, 2018
2
0
[/COLOR]

Sure, you need to install twrp 3.2 in order to can flash oreo zip :)

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 :)!
 

Spartan42

Member
Dec 23, 2015
36
12
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.
 

SnowFuhrer

Senior Member
Apr 5, 2018
1,621
467
Spirit River
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's don't have fastboot.
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,892
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.
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.
 
  • Like
Reactions: Spartan42

zogoibi

Senior Member
Aug 18, 2011
372
50
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?
 

Bhimkarki

Member
Jul 10, 2018
5
0
Doha
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 47
    Unofficial release -TWRP recovery for the Galaxy A3 SM-A320F/FL/Y, Exynos7870

    teamwin-recovery-project-twrp-logo.jpg


    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://forum.xda-developers.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

    Screenshot_2016_03_05_08_13_44_1.png


    DnoCrqh.png


    VAm49c4.png


    ytBFf13.png


    ONLSkMi.png



    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



    .
    .
    7
    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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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
    5
    Since I'm porting LineageOS to this device I'd very much like to have a look at the source code of this.
    3
    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.
    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.
    3
    Hi @ashyx I don't want to bother you and maybe you already know about this qouta support thing TKKG1994 wrote here
    https://forum.xda-developers.com/s7...ficial-twrp-hero2lte-3-0-0-0-t3334084/page223
    Maybe that's why our TWRP can't mount data on Oreo Stock ROMs with Magisk?
    My knowledge is too limited to understand this.
    Would be so cool if you or @McFy could take a look at this (don't know how much you guys work together though).
    Please ignore this post if it is useless.
    Hello, I yet tought about adding it due to force encrypt, It's an oreo flag for fstab, I planned to add it for my twrp build because as I fixed encryption in lineage I took a look around twrp as well, but I have no Idea about stock oreo, I never flashed it .. but problem could be solved by this, wait next twrp offiical build.
    Sorry to make ads about mine version, it's not the aim :) , and no, ashyx sources are not released so mine trees are totally different,
    Regards