Database Develop

[ROM][STABLE][SM-A520X][AXES ROM v1][DEODEX/ROOT/XPOSED/BUSYBOX & MORE!]

Code:
/*
* Your warranty is now void.
*
* We (The AXES Team) are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
*/
AXES Rom as in: "AlexsaderXxvirusElazarSystem", is a Stock Touchwiz Marshmallow Rom based on the A520FXXU1AQC3 firmware for the Samsung Galaxy A5 2017 Smartphone which is compatible with the following Model Numbers:
A520F (Europe, Global Single-SIM)
A520F/DS (Global Dual-SIM)
A520K/L/S (South Korea)
A520W (Canada)
FEATURES:
1- February 2017 Security Patch
2- Pre-rooted
3- Xposed Framework Pre-installed
4- XTouchWiz Xposed Module Pre-installed
5- Busybox Pre-installed
6- Samsung's Good Lock UI applied
7- Galaxy S8 Touchwiz Launcher set as the default launcher
8- Nova Launcher available as well
9- Multiple User Accounts (Main, Guest)
10- Advanced Reboot Menu
11- Pop-up View Gestures
12- Samsung Galaxy Note 7 Apps Edge
13- build.prop Tweaks
14- Viper4Android v2.3.4.0 (Make sure to use the: "Compatible Mode" option in the Viper app since we've inserted another sound mod)
For more info you can check out VIPER'S Audio Website here:
http://vipersaudio.com/blog/?page_id=127
And the Official Xda Thread here:
https://forum.xda-developers.com/showthread.php?t=2191223
15- eXtremeBeats Aural Maximizer 2™ Audio Mod
For more info you can check out the Official Xda Thread of eXtremeBeats here:
https://forum.xda-developers.com/showthread.php?t=2634729
16- S Health Available & Working
17- Knox removed
18- Comes in a 1.4 GB of Size Package
CREDITS:
@alexsaderxda ---> He's Rom as base for AXES Rom and he's help in the Development Area
@XxViRUsPRO ---> Lead Developer/Main Developer
@LorDElazAR ---> Ideas for the Rom and the Creator of this Thread along with it's Text
SPECIAL THANKS:
@samsung for their Firmware & Good Lock UI
@SuperR. for he's Linux Kitchen
@JustArchi for he's ArchiKitchen
@rovo89 for Xposed
@wanam for he's XTouchWiz Xposed Module
@Chainfire for Superuser
@viper520 for Viper4Android
@Ben Feutrill for he's eXtremeBeats Audio Mod
VERSION INFO:
Status: Stable
Current Stable Version: AXES Rom v1
Stable Release Date: Sat, May 13 2017
Hello A5 2017 Users,
Thank you for taking a look at what modified software (Rom) we have to offer for your device. In return we welcome you into considering joining our Galaxy A5 2017 Whatsapp Group.
If your interested, don't hesitate to check out the Original Xda Thread here:
https://forum.xda-developers.com/samsung-a-series-2017/how-to/galaxy-a5-2017-whatsapp-t3561455
Best Regards,
The AXES Team
Don't forget to thank the Lead Developer/Main Developer @XxViRUsPRO in he's post down below for making all of this possible!
Also we'd love to hear from you through your feedbacks and ratings as it is much appreciated and it's what keeps us going into providing new updates and a better overall experience. So be honest above all else.
DOWNLOAD LINK:
https://mega.nz/#!4phlVZyT!oJDhCQyDqldlRSnALTF2itmZ_8p4eUZ_-7wudTUZLI4
Screenshots & Installation Instructions are available in the other posts down below.

Changelog:
[Sat, May 13 2017]: Initial Release
----------------------------​

Screenshots:

Requirements for installing AXES Rom:
1- A Human Brain
2- A PC/Laptop running Windows OS
3- Samsung USB-C Cable (USB-C to USB-A) which obviously comes with your phone in it's retail box.
4- Patience & Time at hand
Make sure to backup your files, contacts and so on before attempting to tamper with your device unofficially as the data residing in your phone's storage will be wiped!

Instructions on installing AXES Rom:
1- Go to your devices Settings ---> About device ---> Software info and tap on it's "Build number" several times in a row till a message appears saying that you have unlocked Developers mode.
Go back one step and you'll find a new option defined as: "Developers mode".
Without further ado select Developers mode in Settings and turn on: "OEM unlock".
2- Make sure the above step is fulfilled before you move on to this step. This guide is case sensitive and your device is on the line in case you do not follow the necessary steps provided in the right sequence and way.
Turn Off your phone completely and press and hold it's Power Button along with it's Volume Down Button & Home Button to enter: "Download Mode".
After the Samsung phone name logo, you will see a blue screen with a warning sign.
Proceed by simply pressing the Volume Up button once as seen on the screen.
Now you are in the: "Download Mode" aka: "Odin Mode" for flashing firmware files using the Samsung flashing tool called Odin.
3- In this step we will be attempting to Flash a Custom Recovery entitled: "TWRP" which stands for: "Team Win Recovery Project".
To do so we will need to download the Odin Windows Application as described above in Step 2 for flashing the custom recovery file.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
Odin v3.12.3 Download Link:
https://forum.xda-developers.com/showthread.php?t=2711451
You'll find the link in the attachments section below the thread.
TWRP Recovery v3.0.2.0 (ONLY for SM-A520F/DS) Download Link:
https://www.androidfilehost.com/?fid=745425885120710156
Once you've download both files from the given links above, extract the folder: "Odin3 v3.12.3" from the Odin3 v3.12.3.zip file to your desktop and move the: "A5-SM-A520F-TWRP-3.0.2.0.tar" file to the Odin folder you just extracted.
Run the Odin3 Application within that folder.
Click on the: "Options" Tab after Log and uncheck: "Auto Reboot" and make sure that: "F. Reset Time" is checked.
Go back to the: "Log" Tab and click on the: "AP" button and select the: "A5-SM-A520F-TWRP-3.0.2.0.tar" file you just moved to the Odin folder in your desktop.
In order for Odin to detect that your phone's connected to your PC/Laptop make sure you have the Samsung Usb Driver for Mobile Phones installed onto your PC/Laptop.
If you already have it installed then simply skip obtaining it from the download link below.
Samsung Usb Driver for Mobile Phones Download Link:
https://yadi.sk/d/uubiaKw6j8bug
Afterwards connect your phone to your PC/Laptop using the Samsung USB-C Cable.
Once Odin displays that your device is connected, hit the: "Start" button below and wait for the file to be done flashing. You will notice above a green progress bar filling up towards the end and also your phone's screen will display a white progress bar to go along with it.

4- Odin will display a green: "Done" box above when it's done flashing TWRP Recovery.
Afterwards we will reboot our phone normally by simply pressing and holding the Volume Up Button and Power Button for a few seconds (around 10 sec.) and then we instantly press and hold the Volume Up Button along with the Power Button and Home Button before we see the Samsung Galaxy A5 Bootlogo in order to successfully boot to TWRP Recovery.
5- You will reach a TWRP Recovery screen asking you if you want to allow system modifications. Swipe right and enable modifications and select: "Don't show this again".
6- For the Internal Storage or Data to work in TWRP Recovery we will have to go to: "Wipe" then "Format Data" (not advanced wipe) and type: "yes".
Go to: "Reboot" and select: "Recovery".
7- Your phone will reboot to TWRP Recovery once again.
If you have the Rom zip file available in your External SD Card then skip Part 1 of this step and move on to Part 2.
Part 1: While running TWRP Recovery on your device, connect your phone to your PC/Laptop using the usb cable and copy the Rom zip file to your phone's Internal Storage.
Part 2: Finally go to: "Install", select storage and select: "Internal" or "External storage" wherever you copied and stored the AXES Rom zip file.
Locate the Rom in either storages, select it and swipe to the right to flash it.
Wait for the Rom to be flashed entirely and then select the reboot option.
Rebooting to the system will require about 5 minutes so be patient and don't forget to report back to us with your experience!

Does this rom flash thru odin or???

No You Can Flash It Only Via Custom Recovery Like TWRP and CWM

in testing.
thanks for the rom.

Is it safe to flash this rom to a SM-A520F??? not duos

Kargi said:
Is it safe to flash this rom to a SM-A520F??? not duos
Click to expand...
Click to collapse
This ROM Is For SM-A520F/DS

LorDElazAR said:
Screenshots:
Click to expand...
Click to collapse
Whats up with this UI?

argoitiaangeel said:
Whats up with this UI?
Click to expand...
Click to collapse
This Is Samsung Good Lock UI and This Can Be Modified By User So He Can Change Colors,Clock And Lock Screen Effects

Guys Any One Need Help Or Have Any Question PM Private Or PM On WhatsApp (+96176406231) And Dont Forget Give Me And LorDEazAR Thanks If You Like This ROM

NO OS INSTALLED .. after flashing through TWRP ..
XxViRUsPRO said:
Guys Any One Need Help Or Have Any Question PM Private Or PM On WhatsApp (+96176406231) And Dont Forget Give Me And LorDEazAR Thanks If You Like This ROM
Click to expand...
Click to collapse
can u make a video how to flash this rom successfully. tnk u /

Nougat Comming.... All Test :good:
For Now! For More Helping [Press Thanks Buttom & Go Try My ROM]

xAce4 said:
can u make a video how to flash this rom successfully. tnk u /
Click to expand...
Click to collapse
Hello xAce4!
Make sure to follow the Instructions in the posts above you for Installing the Rom successfully.

Samsung theme work on this rom?

mcvisster said:
Samsung theme work on this rom?
Click to expand...
Click to collapse
Yes it's available.

reserved

[Recovery] [V3.0-006] Red Wolf Recovery Project

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/* Your warranty is now void! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the flashlight 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. */
Click to expand...
Click to collapse
Introduction
Red Wolf Recovery is alternatovní recovery based on the source code TWRP.
The main objective of the Red Wolf Recovery is to provide the features that were for some reasonrefusedto add to the official source code Winu Team (besides the maximum utilization of hardware options that device ...).
Hence Recovery supports password protection, since Team Win rejected this method of security because users generally do not read any kind of warning, then it was just a mistake on the part of Team Winu that somebody got into the facility despite a recovery password protected.
For this reason, therefore, I warn that the red wolf is secured in such a way that nobody could get into recovery without the user's password, but no recovery willnot safeguardagainst reinstall the device via Flash or Mi fastboot. So please take a note!
Acknowledgments:
Ray Li: For his help in modifying the source code TWRP.
osm0sis: In the video below scripts which also runs most of the functions recovery.
z31s1g: For the base material. theme.
And all the other developers of the various scripts and installation files as Chanfire,topjohnwu,cofface,etc
Features recovery:
- Brightness can be reduced to a minimum fair value. (TWRP only supports a minimum of 10% Brightness).
- Support for more than 50 sections (including "subsections").
- Possibility of installation of paintings in section Modem and Boot Logos.
- Adjusted ADB - for security reasons already does not start automatically at boot recovery, but now it turns in the recovery
- Recovery allows you to set and remove a password
- Torch phone is now going to turn right in Recovery
- Automatically Block stock recovery
- Recovery contains settings regarding Governor where recovery is currently running. If, therefore, not in a hurry, so just switch to performance and processes such as backup, restore or installation will be up almost 20% faster.
- When you confirm the installation file on the screen appears and warnings checkbox for the finished installation. This recovery will automatically notify the completed installation using the notification LED.
- For safety reasons deactivated TWRP theme engine.
- Official TWRP application was replaced for Snap Camera HDR.
- Access to the folder with zálohama and setting recovery is blocked. Access to these files is only possible from the recovery. (This is only an internal storage)
- The first recovery that is built on OMNI ROM code purely for Kate.
- Folder screenshotama of recovery has been moved to /sdcard/WOLF.res to already screenshots of recovery are not confused with the other screenshotama ..
- Updated Czech translation - Slovak translation can be translated from the strings provided below.
- new terminal supports three commands: unpackbootimg, mkbootimg and zipper (so they may also be retrieved from the script, of course).
- Recovery supports Tap To Wake Engine (dt2w is not supported yet ...)
- Support for "night mode".
- Built AromaFM supports Czech language.
- User can set custom name for the folder backup & ID at the ADB.
- Create backup can also be erased at once (not therefore been deleted one by one as it is in ofiko TWRP).
- Recovery is assembled on AOSP 7.1.2 / TWRP 3.1.1-0 / Omni 7.1.2.
Built-in installation files:
Supers
Magisk
Nitrogen UNROOT
substrates Rescue
Deactivation dm-verity
substrates Rescue Legacy
- Built-in scripts community:
Fix-fp-scanner (script to fix the fingerprint reader if the ROM reports "hardware can not be found")
ramdisk- cleaner (the script automatically cleans content boot from custom kernels and thus need not be renewed when switching to a different kernel stock kernel. However, the script still only supports ElementalX kernel, Radon kernel and Franco kernel.Warning: After cleaning the content boot must just to flash a new kernel - certainly attempt to restart the device to the system !!)
rm-pass(script to remove security currently installed ROM.)
NOS-before-flash-other-kernel(script recently found on 4PDA - deactivates the post-script Nitrogen boot ROM and thus allows better compatibility custom kernel).
Community scripts can thus be understandable added community. If you have your script / tip on a script about it here let me know.

Known Bugs
- The search engine of the camera HDR Snap is momentary assembly inoperable. TWRP still finds the application and if the application is installed TWRP and even prevents installation Snap CAMERA HDR.
The problem is mainly that I do not have complete access to that search engine - probably even if I somehow repaired and recovery will still prefer ofiko TWRP search application. So it probably could not be correct function ofiko TWRP applications not installed. However, definitely I do something in the next builds I make.

Link to download
latest build released: official
https://www.androidfilehost.com/?fid=889764386195913594
Update Changes
Update!
RedWolf-V3.0_006-Kate_Kenzo
Major changes;
- After clicking on the main menu icon coffee displays a new button "folder backups." Here you can now rename your current folder & zálohama or even set a new ID instead of the serial number at the ADB.
- Clicking on the Main Menu button to restore the icon appears at the top "bones". Using this button you can now delete all backups currently displayed. Therefore no longer need to delete one by one separately.
Current info
Version recovery: V3.0
Current build: 006
Number of community scripts: 4
Number of installation files: 6
Date of latest released build: 05-7-2017

Strings of recovery can be download here:
Strings for any translation AromaFM:
Extra Links
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
https://github.com/TeamWin
All Credit to ATG Droid
Source

Ss pls

not in a hurry but will have to remind you that source is not updated.... please add
~peace

AxeCORE said:
Ss pls
Click to expand...
Click to collapse
here!

adithyan25 said:
not in a hurry but will have to remind you that source is not updated.... please add
~peace
Click to expand...
Click to collapse
Visit our Forum - https://androidforum.cz
měj hezký den

Can i flash any rom on this type of recovery ?

xN00Bx said:
here!
Click to expand...
Click to collapse
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution

cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
+1

filipino guy said:
Can i flash any rom on this type of recovery ?
Click to expand...
Click to collapse
Yes you can flash it on any roms
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!

xN00Bx said:
Yes you can flash it on any roms
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
Click to expand...
Click to collapse
Yaa now working don't know why it didn't worked at first he he he thank you bro

I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system

anandumohan said:
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
Click to expand...
Click to collapse
Same thing

Recovery was withdrawn because its not yet ready to run on the variant Kenzo fully,
only kate is completely functional!
we will back to you when it's gets fixed
~thanks

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy A5/A7 (2017)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy A5/A7 (2017)​Only for exynos variants - A520F (Europe, Global Single-SIM); A520F/DS (Global Dual-SIM); A520K/L/S (South Korea); A520W (Canada), A720F (Global Single-SIM); A720F/DS (Global Dual-SIM); A720S (South Korea)
Disclaimer
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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
A5 2017 - https://twrp.me/samsung/samsunggalaxya52017.html
A7 2017 - https://twrp.me/samsung/samsunggalaxya72017.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A5 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a5y17lte
A7 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal7880/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible

Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Thanks
like!

bootloop
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:

e.ahangari said:
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
Click to expand...
Click to collapse
What device and what method of flashing did you used?

a7, when installing Odin, bootlooр

bootloop
corsicanu said:
What device and what method of flashing did you used?
Click to expand...
Click to collapse
A720F oreo stock rom - I wanted to update from twrp_3.1.0-1 to 3.2.2

cant flash in a7 2017 (a720f)using odin

on my a7 bootloop too, flash via twrp. flash through odin previous version helps

A520F, zip downloaded and flashed in TWRP, It's perfect, no problem (bootloop) at this time!
Thank you corsicanu.

Well done.

Works great for me, flashed .img in TWRP,A520F.

Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases

Thanks
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
Thanks a lot.
Its now fixed and work properly.:highfive::highfive::highfive:

Thanks

A7y17lte
is anyone installed root succesfully?

corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
I'm about to receive a new A5 2017 and update it to official OREO right out of the box.
After having updated, there's the TWRP step and I just wanted to know of I have to also flash the usual encription thing (opt verity or something like that) I have almost always flashed after a fresh twrp install.

Works fine for me so far... I will test with the official fw to know if the /data is decrypted. We appreciate the work corsicanu. :good:
@edit
For me, everything works fine! including support for all languages.

A7y17lte
corsicanu said:
Unofficial TWRP 3.2.2-0 For A5 / A7 2017​Disclaimer
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.
Special features:
Code:
- built from Oreo kernel source
- built in full 64 mode
- updated TWRP source
- fully compatible with all Oreo roms
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.zip, push it into phone storage and flash it as normal zip in your current recovery.
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/twrp_android_kernel_samsung_universal7880
Credits:
@Dyneteve
@TwrpBuilder
Click to expand...
Click to collapse
is anyone installed root succesfully?

Hey,
I have a problem and I don't know how to fix it, cuz I never had that.
I've installed TWRP successfully and I can start it normally, but TWRP don't have access to any Files in Internal Storage.
I installed TWRP on A520F (with Firmware DBT, Android 8.0)
Kind regards,
DasNuddel // Charles

[RECOVERY][OFFICIAL] TWRP 3.6.0_9 [N8000 N8010 N8020]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Odin
- Odin3 v3.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 10.1
How to flash TWRP with Odin
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 10.1").
How to flash TWRP within a previous version of TWRP
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power and Volume UP simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 10.1").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n8000 repository
- n8010 repository
- n8020 repository
- TWRP repository
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 10.1
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-1
Stable Release Date: 2021-02-14
Created 2021-02-14
Last Updated 2021-10-12

Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.

CurbThePain said:
Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.
Click to expand...
Click to collapse
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media).
But if you made a factory reset, then the internal memory shouldn't be deleted.

html6405 said:
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media/0).
But if you made a factory reset, then the internal memory shouldn't be deleted.
Click to expand...
Click to collapse
Well previously using TWRP 3.3.1 I would do the advanced wipe and only select the /data partition not the internal storage. Then it would say "wiping /data without wiping internal storage". But if I did the same thing in TWRP 3.5.0 it would say "wiping /data and internal storage". I stopped using the basic factory reset many years ago because it always wiped my internal storage. But I will give it a shot and let you know if that works for formatting just the /data partition.

CurbThePain said:
factory reset many years ago because it always wiped my internal storage.
Click to expand...
Click to collapse
This was a faulty behaviour, because the factory reset should wipe only /data withoult /data/media.

Off topic, but it seems like emojis need to be disabled in the 1st post.

TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.​

got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7

noobody168 said:
got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7
Click to expand...
Click to collapse
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.

All image sizes are fixed,
new builds are up!

html6405 said:
Все размеры изображений фиксированные,
новые постройки построены!
Click to expand...
Click to collapse
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)

html6405 said:
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.
Click to expand...
Click to collapse
Works fine with with revised version now, thank you very much

SteelK said:
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)
Click to expand...
Click to collapse
Are you sure? I've tested it, I will check on this later.

Yes, I'm sure I tried the latest version from TWRP site for N8000

Now I've tested the files again from both servers, and it is working in my case.
The file size is lower then our border size.

Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.

SteelK said:
Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.
Click to expand...
Click to collapse
I have no idea, actually if the md5 is the same, it must work.
SteelK said:
recovery partition?
Click to expand...
Click to collapse
Yes, but they are equal for all of us.

I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?

xtoad said:
I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?
Click to expand...
Click to collapse
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.

html6405 said:
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.
Click to expand...
Click to collapse
I believe it is ext4. Or whatever the default is. I have not changed it on my own.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy M31s (Exynos)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
04.06.2021 - Initial Release.

vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.

withwaves86 said:
vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.
Click to expand...
Click to collapse
file updated

afaneh92 said:
file updated
Click to expand...
Click to collapse
It works, thank you. I'll be test this

Is it working on One Ui 3.1 on M31?

Atharkhan101 said:
Is it working on One Ui 3.1 on M31?
Click to expand...
Click to collapse
You can test

afaneh92 said:
You can test
Click to expand...
Click to collapse
In not here to test. I don't want to screw my phone.

Atharkhan101 said:
In not here to test. I don't want to screw my phone.
Click to expand...
Click to collapse
Then dont

TWRP works in ONEUI 3.1. I flashed it but after it boots to the system and I reboot it or shut it down I get only official binary are allowed to be flashed, and I have to go back to stock. Latest U3 Android 11 M31S. Do you have any kernel for this model?

Working on M31s One UI 4.1

afaneh92 said:
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
Click to expand...
Click to collapse
does this mean I will have to wipe my phone's entire data?

CosmicSavage said:
does this mean I will have to wipe my phone's entire data?
Click to expand...
Click to collapse
yes

The device is not going into recovery mode instead getting stuck at samsung logo after flashing vbmeta using odin

afaneh92 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hello Bruh..it worked.. i had issue earlier with the
KG State and/or RMM state prenormal then i reflashed using the official m31S ROM then i unlocked the OEM and flashed the above two files at the same time using odin

afaneh92 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks

Hangrylion said:
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks
Click to expand...
Click to collapse
You don't need all this hassle just connect to internet and open browser then check kg status, must be checking.

are the links updated?

Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?

osama_blythe said:
Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?
Click to expand...
Click to collapse
M31s, android 12, OneUI core 4.1,
working perfectly with no any issue with TWRP and magisk.