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

[RECOVERY][OFFICIAL] TWRP 3.3.1-0 for Galaxy A8+ 2018

Search This thread

BlackMesa123

Senior Member
Aug 29, 2015
1,682
3,276
Adrano
www.facebook.com
Team Win Recovery Project

Code:
#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* 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 doing this to your device
* 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.
*/

home.png
backupname.png


Disclaimer:
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.

What is TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.

Read more about TWRP here: https://twrp.me/about/

How to flash and setup it completely?
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and RMM Bypass v3 zip.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Power, Vol + and Vol - buttons together)
- Connect your phone in your PC, open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now copy the no-verity-opt-encrypt and RMM Bypass zip you downloaded before and flash them (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.

Download:
Galaxy A8 2018 (jackpotlte):
https://twrp.me/samsung/samsunggalaxya82018.html

Galaxy A8+ 2018 (jackpot2lte):
https://twrp.me/samsung/samsunggalaxya8plus2018.html

Sources:
Kernel Source Code: https://github.com/devkingsteam/android_kernel_samsung_universal7885/
Device Tree (jackpotlte): https://github.com/TeamWin/android_device_samsung_jackpotlte
Device Tree (jackpot2lte): https://github.com/TeamWin/android_device_samsung_jackpot2lte

Changelog:
Check Post #2.

A8 2018 Community Telegram Group:
Invite Link

Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ananjaser1211 and @McFy for their help and support
- @SaboorTheCool for testing out the recovery


XDA:DevDB Information
TWRP for Galaxy A8+ 2018, Tool/Utility for the Samsung Galaxy A8+ (2018)

Contributors
BlackMesa123
Source Code: https://github.com/TeamWin


Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-20

Created 2018-07-18
Last Updated 2019-06-17
 
Last edited:

BlackMesa123

Senior Member
Aug 29, 2015
1,682
3,276
Adrano
www.facebook.com
Changelog:

Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.

20180921 (3.2.3-0)
- Updated kernel source code
- Fixed USB OTG
- Enabled FBE support (general AOSP only, Samsung method is still not supported)

20180730 (3.2.3-0)
- Removed /preload from partitions table
- Added /system_image (raw system partition backup)
- Enabled software encryption support (general AOSP only, Samsung method is still not supported)

20180718 (3.2.2-0)
- First release
 
Last edited:

lrwjr1964

Senior Member
Sep 17, 2009
63
10
I lost mobile network?

Hi all. I have an unlocked A8+. I rooted when I had Nougat. I installed the oreo firmware from Columbia and the phone works great. I like the enhancements. I followed the instructions to install the new twrp. Took a bit but got magisk working and root explorer but had issues with busy box and titanium bkup. No biggie. The issue I had is the when I went to send a text I got an error and then I noticed I had no signal. So I checked and low and behold I had no mobile networks in the connections list. Does anyone have a clue as to why it disappeared? Did I miss something? I tried it 2 times with the same result. And help would be greatly appreciated.
P.S. OEM unlock is enabled as well as USB debugging enabled also.
 
  • Like
Reactions: Panda090

hackuletz16

Senior Member
Aug 4, 2013
112
20
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..


Same thing happened to me.
had to download and install the whole firmware.

downloaded from this
https://forum.xda-developers.com/galaxy-a8-plus/how-to/pie-a8-pie-a730fxxu4csb9-t3908703

probably happened because I still have RMM lock (can't do anything to unlock) in oreo. Bootloader got unlocked in Pie so I thought i can now flash custom binaries. Turns out, you still can't
 

mark0021

Member
Jan 16, 2013
38
8
Parañaque City
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its worst than frp locked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, system app we only need without those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies our needs but it comes with risk. Even we have same device model flashing custom rom in other but same device can experience bugs and some are not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and if something went wrong you're the one responsible and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
If you really want to start rooting your phone just like me, all you need to do is read, study and understand every aspect, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time of visiting xda, I have a positive feeling and also I'm completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing suddenly stop me to proceed.
(Read more)
To fully understand the procedure, it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need privilege access to these "four letters" R O O T.
We all know that with a stock os, accessing root surely not possible, it need the superuser (su) to grant permission to access the root and installing su ofcourse is not just like the ordinary apk that can easily be installed, it needs to be flash manually but not in odin. It will be flash in recovery mode but flashing it there still be impossible because that su.zip file cannot be flashed with the stock recovery, you need to modify the recovery mode... Do you how to mdofy it? Well, if you can, that's good and you will have a unique version of it, but me? No way I can modified it...
So, to those people like me who cannot make a customized recovery, NO WORRIES! good news for us because xda geniuses made us for free, custom recovery like twrp, hurray!
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
Next step to do is yet very simple and easy up to the last step of the procedure...
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its wosrt than frp lovked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, our only and always be our favorite to do... which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, having an app that we need and removes those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies your needs but it comes with risk. Even we have same device model flashing custom rom some device can face bugs some is not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
Like me, if you really want to make it happen, all you need to do is read, study and understand, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time visiting xda, I have a positive feeling and completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing stops me to proceed.
(Read more)
To fully understand the procedure and , it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need access to these "four letters" R O O T.
Accessing it is not possible, I need the superuser to grant me permission to access the root and su ofcourse is not just like the ordinary apk that can easily be installed, it will be flash, not in odin but recovery but flashing it will not be possible because that su.zip file cannot be flashed with the stock recovery, but custom recovery can like twrp.
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
***Next step to do is very simple and easy up to the last step of the procedure...
Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
Can do it with a couple of swipes to wipe (format data), reboot to recovery again flash su, flash no-verity and also RMM bypass zip just for sure... after that fun stuff can now be available, flash custom roms, blah.. blah.. etc. Boot normally without worries.
About the:
" ***Next step to do is very simple and easy "(above)
Yet very simple and very easy, that's the actual problem dive-in...
As I've mentioned above about having this device from such time and putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS"
The next step was about formatting and it's a must thing to do to make it work and using unrooted device is impossible to make NANdroid backup, the 64Gb internal storage were almost full and because of that it makes much harder backing-up...
Any advise?
Please help...
 
Last edited:

BlackMesa123

Senior Member
Aug 29, 2015
1,682
3,276
Adrano
www.facebook.com

Well the answer is no of course, if you don't wipe your /data partition it will be unreadable from TWRP, equals you can't flash anything that needs to write data in that partition, like Magisk itself. Was it necessary to write that whole post when all you're asking is just a way to avoid /data partition wiping? You basically blamed the "master XDA devs" (which I feel like I'm part of it, sort-of) because "they made the steps for root so hard". I imagine you know "we" aren't the "bad guys that wanna make you lose your precious time" and if I wrote all those steps to follow in the main post (that you copy-pasted twice in your post, without any sense I'd add since users can read the steps from there instead of reading a 1500 lines post) are there because... they are needed? You even noticed and wrote yourself that if you miss one you break something in the way and you get no TWRP if you don't follow all the steps correctly... Wanna blame someone? Then blame the OEMs that add all those security features instead of blaming people that dedicated their time to bypass those and bring you custom softwares for your phone.
 
Last edited:

Miikk08

New member
Jul 18, 2017
1
0
pls someone help me. Everytime I install TWRP through odin my entire system wipes, and in TWRP it recognizes as 0mb. How can I install TWRP without wiping the entire phone?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Team Win Recovery Project

    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * 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 doing this to your device
    * 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.
    */

    home.png
    backupname.png


    Disclaimer:
    - I am not responsible about any damage of any kind that this custom binary may cause.
    - Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
    - Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be resetted in any way, so think twice before flashing this.
    - Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
    - If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.

    What is TWRP?
    Oh come on, you know what it is - don't try to fool me!
    In case you're serious, though...

    Team Win Recovery Project is a custom recovery for Android devices.
    It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.

    Read more about TWRP here: https://twrp.me/about/

    How to flash and setup it completely?
    - First, make sure your phone isn't RMM Locked.
    - Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and RMM Bypass v3 zip.
    - Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
    - Do a backup of all your important data and files in your phone.
    - Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Power, Vol + and Vol - buttons together)
    - Connect your phone in your PC, open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
    - Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
    - Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
    - Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now copy the no-verity-opt-encrypt and RMM Bypass zip you downloaded before and flash them (touch Install and select each zip to flash it)
    - You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.

    Download:
    Galaxy A8 2018 (jackpotlte):
    https://twrp.me/samsung/samsunggalaxya82018.html

    Galaxy A8+ 2018 (jackpot2lte):
    https://twrp.me/samsung/samsunggalaxya8plus2018.html

    Sources:
    Kernel Source Code: https://github.com/devkingsteam/android_kernel_samsung_universal7885/
    Device Tree (jackpotlte): https://github.com/TeamWin/android_device_samsung_jackpotlte
    Device Tree (jackpot2lte): https://github.com/TeamWin/android_device_samsung_jackpot2lte

    Changelog:
    Check Post #2.

    A8 2018 Community Telegram Group:
    Invite Link

    Credits:
    - Samsung for kernel source code
    - TeamWin for their awesome recovery
    - @ananjaser1211 and @McFy for their help and support
    - @SaboorTheCool for testing out the recovery


    XDA:DevDB Information
    TWRP for Galaxy A8+ 2018, Tool/Utility for the Samsung Galaxy A8+ (2018)

    Contributors
    BlackMesa123
    Source Code: https://github.com/TeamWin


    Version Information
    Status: Stable
    Current Stable Version: 3.3.1-0
    Stable Release Date: 2019-05-20

    Created 2018-07-18
    Last Updated 2019-06-17
    3
    Changelog:

    Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.

    20180921 (3.2.3-0)
    - Updated kernel source code
    - Fixed USB OTG
    - Enabled FBE support (general AOSP only, Samsung method is still not supported)

    20180730 (3.2.3-0)
    - Removed /preload from partitions table
    - Added /system_image (raw system partition backup)
    - Enabled software encryption support (general AOSP only, Samsung method is still not supported)

    20180718 (3.2.2-0)
    - First release
    3
    Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.
    2

    Well the answer is no of course, if you don't wipe your /data partition it will be unreadable from TWRP, equals you can't flash anything that needs to write data in that partition, like Magisk itself. Was it necessary to write that whole post when all you're asking is just a way to avoid /data partition wiping? You basically blamed the "master XDA devs" (which I feel like I'm part of it, sort-of) because "they made the steps for root so hard". I imagine you know "we" aren't the "bad guys that wanna make you lose your precious time" and if I wrote all those steps to follow in the main post (that you copy-pasted twice in your post, without any sense I'd add since users can read the steps from there instead of reading a 1500 lines post) are there because... they are needed? You even noticed and wrote yourself that if you miss one you break something in the way and you get no TWRP if you don't follow all the steps correctly... Wanna blame someone? Then blame the OEMs that add all those security features instead of blaming people that dedicated their time to bypass those and bring you custom softwares for your phone.