• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[TWRP 3.2.1-1] [ROOT] A8 sm-a530f - 02/02/2018

Search This thread

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,087
9,899
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885

teamwin-recovery-project-twrp-logo.jpg



TWRP 3.2.1-0 Released

Dec 9, 2017

TWRP 3.2.1-0 is out now for most currently supported devices.

What's new in 3.2.1-0:

* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot



Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Beta


Features:

MTP >> not working
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support




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


Instructions:


Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY


NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.2.1-1_sm-a530f_020218


To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

To disable forced encryption and mount internal storage (/DATA):
(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




DEVICE TREE: soon


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


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

 
Last edited:

nimanwar

New member
Aug 2, 2017
2
0
AF1QipOkSvCK8oXOhEOTi23Nh6xHE6hwh3RSMHeNp5RK
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885

teamwin-recovery-project-twrp-logo.jpg



TWRP 3.2.1-0 Released

Dec 9, 2017

TWRP 3.2.1-0 is out now for most currently supported devices.

What's new in 3.2.1-0:

* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot



Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Beta


Features:

MTP >> not working
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support




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


Instructions:


Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY


NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.2.1-1_sm-a530f_020218


To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

To disable forced encryption and mount internal storage (/DATA):
(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




DEVICE TREE: soon


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


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

 

cuantonhonhoi

Member
Oct 31, 2013
6
0
only official release binaries are allowed to be flashed

HELP: Mine SM-A530F failed to be flashed: "only official release binaries are allowed to be flashed".
 
Last edited:

capskull

New member
Feb 12, 2018
1
0
Hi, I have the same problem, I cannot flash because of : "only official release binaries are allowed to be flashed"
RMM STATE : Prenormal
FRP LOCK : OFF
OEM LOCK : OFF
Also I don't know how to find a proper rom stock recovery because rom from updato fail in odin.

What can i do ?
 

dwane3

Senior Member
Apr 9, 2009
236
22
On my "only official release binaries are allowed to be flashed" too..
 
Last edited:

Davorkne

New member
Feb 14, 2018
1
0
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885

teamwin-recovery-project-twrp-logo.jpg



TWRP 3.2.1-0 Released

Dec 9, 2017

TWRP 3.2.1-0 is out now for most currently supported devices.

What's new in 3.2.1-0:

* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot



Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Beta


Features:

MTP >> not working
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support




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


Instructions:


Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY


NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.2.1-1_sm-a530f_020218


To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

To disable forced encryption and mount internal storage (/DATA):
(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




DEVICE TREE: soon


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


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



Cool
 

DziugsBugs

New member
Feb 16, 2018
3
1
As soon as i installed twrp and then rebooted device it's stuck on boot loop. Maybe the twrp version is not compatible or i did something wrong?
 
  • Like
Reactions: 587.saboor

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,087
9,899
Hey @ashyx , My teammate is using an A530F, we just want to let you know MTP/adbsideload/adb shell isn't working. (its not aswell in my a530f twrp with disabling MTP in makefile with fevax commit because there isnt that samsung_mtp flag we are used to) Hope you can take a look in to it if you have time. Thanks in advance.
Yes I'm aware of it. Samsung seem to be forcing their own MTP driver.
Also as I mentioned to someone in the A730f thread. Due to lack of responses I wasn't prepared to even tackle the issue until people could be bothered to post in the thread.

For ADB to work firstly try disabling MTP in TWRP.
 
  • Like
Reactions: ananjaser1211

Serp87

Senior Member
Feb 25, 2012
134
78
Moscow
what do I need to do to work properly twrp?
 

Attachments

  • FJIMG_20180217_155401.jpg
    FJIMG_20180217_155401.jpg
    241.8 KB · Views: 1,004
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885

    teamwin-recovery-project-twrp-logo.jpg



    TWRP 3.2.1-0 Released

    Dec 9, 2017

    TWRP 3.2.1-0 is out now for most currently supported devices.

    What's new in 3.2.1-0:

    * minui fixes (cryptomilk)
    * Better android-8.0 compatibility in ROM trees (Dees_Troy)
    * Fix missing library in android-8.0 (nkk71)
    * Fix inconsistent SDCard naming (DevUt)
    * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot



    Update 02/02/2017
    TWRP 3.2.1-1 NN build released.
    Current status: Beta


    Features:

    MTP >> not working
    ADB working >> to be confirmed
    SEANDROID warning fix
    TWRP and Kernel built from latest source
    Raw SYSTEM image backup
    NTFS support
    F2FS support >> To be added
    Twrp app support




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


    Instructions:


    Flash with odin in the AP slot.
    Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
    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 + VOL DOWN
    As soon as the screen goes blank change to POWER + VOL UP
    You should now see TWRP recovery.
    FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY


    NOTE: ON SOME ANDROID 5.1.1/6.0/7.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.2.1-1_sm-a530f_020218


    To Root:
    Flash the latest SuperSU or Magisk release with TWRP:
    SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
    MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

    To disable forced encryption and mount internal storage (/DATA):
    (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




    DEVICE TREE: soon


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


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

    5
    im gonna put this here as reference. just a more simplified list of steps.
    hope this helps anyone

    1. UNLOCK:-
    - enable oem unlock after 168hrs of uptime (RMM state)
    - Swith off and put your device in DOWNLOAD MODE. (POWER + VOL DOWN + VOL UP)
    - Flash TWRP in ODIN in AP slot (uncheck auto reboot)
    - DO NOT REBOOT DEVICE INTO ANDROID
    - reboot to recovery (TWRP) from download mode by pressing POWER + VOL DOWN and then POWER + VOL UP when the screen goes black.

    2. TWRP:-
    - swipe to "Allow modification"
    - Format DATA
    - Check DATA is mountable.
    - flash SUPERSU
    - flash Boot image patch (no-verity-no-encrypt_ashyx.zip)
    - flash RMM-State_Bypass_Mesa.zip
    - reboot
    3
    My phone is patchlevel March
    Hi guys. Its work and stable on my phone ! (patch level april. I have update first). Root a8 2018

    Step
    1. Make sure OEM Unlock is show and actif in developer mode.
    2. Flash TWRP via odin in download mode
    (vol -) and (power) to acces download mode, (vol +) to continuew flash
    (Uncheck autoreboot in Odin option) If u succes u get done in odin...
    3. Now go to recovery.
    In download mode. Press (vol -) (power)
    In black screen, move press (vol+) (power) now... U entered in TWRP.
    Format data first (input type "yes" to continuew format data). And reboot to RECOVERY again. (Im 2x format data for make be sure)
    4. Flash "SuperSU" ( i think superSU more stable . I get botlop with magis). clear cache
    5. Flash "no veryfi...". clear cache.
    6. Flash "RMM State asyx V2"... ? look ?V2? . clear cache

    7. Reboot to download mode an reboot to system (vol -)(power)

    Wait... this step can sow long time logos. System have preparing and installing app.
    Now u get root.
    Check in developer mode... OEM Unlock ready show again. And try restart device... wow its perfect

    Thanks all.. its my 4nd try root step and work...
    3
    I new with Samsung device, and I found development of A530F isn't much (probably because it's new device in 2018, I hope..). Do we have a telegram or whatsapp group?? I'd like to know more about my A530f.

    Check Swift Kernel Telegram Group. Actually Taif is working on Note8 port?
    2
    Did it

    Ok , let me post my findings here :)

    When I got the phone ( SM-A530F/DS , 1 month old ) and I inserted my SIM cards, it was of course ...... RMM State : prenormal :(

    Good to know : OEM Unlock is NOT shown in developer mode when RMM State is prenormal !!

    Patiently waited for 168 hours , copied the ZIP Files onto the SD, then went for it yesterday eveinng

    - Enabled OEM Unlock in developer options
    - Put the phone in download mode
    - Double-checked RMM State was no longer shown as prenormal
    - flashed TWRP via Odin as per instructions ( AP, no reboot )
    - rebooted into TWRP
    - formatted Data partition
    - flashed SuperSU
    - flashed no-verify-no-encrypt patch

    Up to there , everything went fine .

    Then I wanted to flash the RMM-State_Bypass_Mesa.zip , but got the message that this device was not supported :(
    As I didn't want to mess with a different Kernel , I thought I'd boot into the OS , and then apply the changes the RMM fix does manually ....

    ( Slight mistake at that point ..... )

    I believe that booting into the OS got me RMM locked again ... DOH ! ( developer options gone, and after enabling developer options, no OEM Ulnock shown )

    So, now .... I have root, and my phone is working ...... but as OEMUnlock is NOT shown in the developer options, i think I'd better not reboot my phone once more

    IF I reboot now ..... i'll be stuck because of that and I'll probably have to reflash stock and go thru the entire procedure again

    I DO THINK that if I leave my phone on now again for 168 hours, the OEM Unlock option should show without rebooting ( It did this time for sure )

    So my plan is to wait until I see the OEM Unlock again ( positively NO reboot till then) , then enable it , and apply the RMM Fix changes to be safe :)

    Wish me luck ..... ( or am I doomed anyway ?? ;) )


    Ashyx , thanks for your work and making TWRP / root possible , let's just hope that I can get thru with it without having to do everything once more