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

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A6+/A605

Search This thread

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,895
Unofficial release -TWRP recovery for the Galaxy A6 plus 2018 - SM-A605 MSM8953

teamwin-recovery-project-twrp-logo.jpg




TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here





Update 18/11/2018
Beta build released.
Current status - Beta (tested working)
Treble supported
Update 14/12/18 - OTG support added.


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.

NOTE: ON ANDROID 5.1.1> 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.



*****INSTALL INSTRUCTIONS:*****


Flash with ODIN in the AP slot.

1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot and hit start.
twrp_3.2.3-1_sm-a605_141218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795

NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.

5. Reboot to TWRP (Do not boot to the OS yet)



6. Move on to root instructions below. This is a requirement to get the device to boot.


*****OREO ROOT INSTRUCTIONS:*****


1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
A605_oreo_forced_encryption_disabler

2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

3. Enjoy your rooted device.


DEVICE TREE: soon


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




Credits: Me, Teamwin, @nebkas for initial testing, @BlackMesa123 for RMM bypass zip.

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

 
Last edited:

kes228

Member
Dec 15, 2017
25
1
Not sure what you mean by it mounts all partitions at once?

I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job

---------- Post added at 02:08 PM ---------- Previous post was at 02:00 PM ----------

I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job
you can follow the link https://t.me/joinchat/AAAAAElB-MiezOR9qbn4MQ
For communication
 

balanadi

Senior Member
May 28, 2012
75
51
Bucharest
www.facebook.com
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
 
  • Like
Reactions: ashyx

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,895
Thanks a lot @ashyx

I will try it out in the evening. 15:00 we have here now in Romania, I will be arround in 7 hours.

I recommend all testers, to patch the boot.img with magisk from their own localized firmware. Download your firmware from samsungbay.

1. Flash the whole firmware, all included 5 files with odin.
2. extract from the AP_ file the boot.img.lz4 .
3. unpack the boot.img.lz4 with a command line tool. I ran into problems and not patchable boot.img with extracting with 7zip.
4. Install magisk manager app and go to install. Choose the before extracted boot.img from the original firmware. Magiskt will now patch the boot img and you will be able to flash it via odin.
------------------------------------------------------
5. after all that worked fine, flash the recovery with odin.

Now you should have a twrp recovery and boot into it. Format the data etc. at mentioned in the inital post.
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.
 
Last edited:
  • Like
Reactions: an-_-dro

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,895
you are great ashyx. does this boot.img work with all the different regions firmware?
There's a good chance as the sources are the same for all models.
In my experience with other devices it will work without issue.

It's not strictly necessary to flash the patched boot image as Magisk may be able to patch the boot image. However not always which is why I provided it pre-patched.
 
  • Like
Reactions: an-_-dro

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,895
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
At least this indeed confirms this device supports RMM.
In that case I should provide a link to the RMM patch here.
 

nebkas

Senior Member
Aug 18, 2008
111
29
Bucharest
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.

I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM

---------- Post added at 18:16 ---------- Previous post was at 18:12 ----------

hi . when i wanna flash the pached boot in download mode it says only offical binaries are allowed to be flash
what should i do?

Delete the google account, and restart your phone to disable FRP LOCK. Also check in developer options, that you check OEM UNLOCK ENABLE
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,110
9,895
I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM
What you're suggesting is no different to flashing the Magisk zip with TWRP. Except using Magisk manager just makes it a more long winded process, as there are extra steps involved.
As long as Magisk and RMM patch are flashed before booting to system there shouldn't be an issue.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    Unofficial release -TWRP recovery for the Galaxy A6 plus 2018 - SM-A605 MSM8953

    teamwin-recovery-project-twrp-logo.jpg




    TWRP 3.2.3-0 Released
    Aug 6, 2018
    TWRP 3.2.3-0 is out now for most currently supported devices.
    What's new in 3.2.3-0:
    * Fix automatic installing of OTA zips on encrypted devices
    * Remove SuperSU from TWRP
    * Support both md5 and md5sum file extensions when doing MD5 checking for zip files
    Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
    We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
    You can track the progress of builds here





    Update 18/11/2018
    Beta build released.
    Current status - Beta (tested working)
    Treble supported
    Update 14/12/18 - OTG support added.


    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.

    NOTE: ON ANDROID 5.1.1> 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.



    *****INSTALL INSTRUCTIONS:*****


    Flash with ODIN in the AP slot.

    1. Put your device in DOWNLOAD mode.
    (Hold POWER + VOL DOWN + VOL UP)
    2. Load the file below into the AP slot and hit start.
    twrp_3.2.3-1_sm-a605_141218
    3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
    You should now see TWRP recovery.
    4. Flash the RMM bypass zip
    https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795

    NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.

    5. Reboot to TWRP (Do not boot to the OS yet)



    6. Move on to root instructions below. This is a requirement to get the device to boot.


    *****OREO ROOT INSTRUCTIONS:*****


    1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
    Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
    After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
    PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
    A605_oreo_forced_encryption_disabler

    2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
    https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

    3. Enjoy your rooted device.


    DEVICE TREE: soon


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




    Credits: Me, Teamwin, @nebkas for initial testing, @BlackMesa123 for RMM bypass zip.

    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

    3
    Ashyx is there a solution to the problem of connection with the pc? mtp application reports error
    I will update the boot image later with a fixed version.
    Alternatively download the stock boot image below.
    Flash it with TWRP then immediately flash the Magisk zip.
    Reboot.

    https://www.androidfilehost.com/?fid=11410963190603856376
    2
    there is a small problem here, i can't change brightness. it won't be darker or brighter.
    I need the path of the brightness file.

    If some one could do:

    ls -R /sys/devices > sdcard/devices.txt

    Then post up the devices.txt file.
    2
    Hi, does the problem of lock screen and fingerprint unlock still exit?
    No they fixed it
    2
    I need device tree, vendor tree, and kernel source
    Could you tell me how did you get those things?
    I want to build a rom
    You need to build a device tree yourself.
    You may be able to use parts from someone elses github as a starting point if you can find a device using the same platform.
    Kernel sources are downloaded from Samsungs open source release Centre.

    TWRP device tree is no good for compiling roms.