[recovery][twrp 3.3.0] A3 2017 [Official]

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
TWRP 3.3.0 For A3 2017





Disclaimer


Code:
/*
 * Your warranty will be VOID after installing a custom recovery.
 *
 * Get notified yourself that I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed.
 * Please do some research if you have any concerns about features included in this recovery
 * before flashing it!
 * YOU are choosing to make these modifications,
 * and if you point the finger at me for messing up your device,
 * I will laugh at you.
 */
This is for A3 2017 only

Download

TWRP Unoffiicial for a3 2017 : host.mcfy.fr
TWRP Offiicial for a3 2017 : twrp.me




Instructions

With Odin : download the .tar file and flash on AP case of Odin
With Twrp : download the .img file on your phone and flash it throw the older twrp by the image installation menu


Credits and sources

@TwrpBuilder Our team :) check our project ! twrp buider
source : https://github.com/TwrpBuilder/android_device_a3y17lte


Changelog
Code:
- 5th March 2018 : Initial build : TWRP 3.2.1-0
- 10th March 2018 : Fixed ODIN ZIP format
- 26th June 2018 : TWRP is now official
- 8th august : TWRP 3.2.3 
- 18th Aprile 2019 : TWRP 3.3.0
 
Last edited:

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
THANK YOU

McFy, amazing contribution!

i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.

searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.

Code:
[1]: https://teamw.in/Devices/Samsung/
[2]: https://samsungodin.com/
 

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
McFy, amazing contribution!

i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.

searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings ;)
 
Last edited:

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings ;)
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.
@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?

[1]: https://glassechidna.com.au/heimdall/
 

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.

@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?

[1]: https://glassechidna.com.au/heimdall/
Maybe, but twrp is not a large file, large file would be a rom, what do you mean by merging my change to twrp code base ?, I didn't edited source code twrp, just build it for a3 2017
 

xtracter360

Member
Nov 14, 2012
9
1
0
For me Odin gets stuck at: NAND Write Start!!

Complete log:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery_a3y17lte-050318.img
<ID:0/006> NAND Write Start!!
When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?

UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
 
Last edited:

Pat750

Senior Member
Sep 12, 2016
586
256
73
For me Odin gets stuck at: NAND Write Start!!

Complete log:


When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?

UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
And you have to flash the .tar file in Odin. It seems you tried the .img file.
 

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
Maybe, but twrp is not a large file, large file would be a rom
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:

Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...

@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
 

5K0RVP4

Senior Member
Dec 29, 2012
152
250
0
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:

Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...

@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?


https://desktop.firmware.mobi/device:141/firmware:15535 there you can download latest stock recovery :)
 
  • Like
Reactions: black_tiger1

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:

Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...

@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?


Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin. Samsung are pretty safe from hardbrick, you will everytime have access to the download mode ;)
 
  • Like
Reactions: vwtc6yc8e

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin.
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so :)

@McFy: thank you for answering so many questions. deeply appreciated.

tar it and use odin.
i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
 

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so :)

@McFy: thank you for answering so many questions. deeply appreciated.


i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
md5 doesn't matter, you can still extract it as a tar archive, then you will get the recovery.img,
trust me it will not happen :)
 
Last edited:

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
in the developer options i've enabled usb debugging and oem unlock.
i installed samsung usb drivers and adb. using
Code:
adb devices
i was able to detect my device.
using oding v3.13.1 i tried to flash twrp but i got the following error:

Code:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 19 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery_a3y17lte-050318.img
<ID:0/004> Complete(Write) operation failed.

tried again on a different usb port, and got a different error:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 19 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery_a3y17lte-050318.img
<ID:0/005> Unassigned file
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)



could someone please shed the light on the issue?
 
Last edited:

vwtc6yc8e

Member
Mar 5, 2018
39
10
0
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.

@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
 
Last edited:

McFy

Recognized Developer
Aug 31, 2016
549
1,473
0
19
Angers
mcfy.fr
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.

@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
1. I think it's impossible
2. You can look at them on sources
3. It's yet set in true