Database Develop

Huawei P8 [ROM][6.0][EMUI 4.0.3]MagicArrow - Custom ROM European Firmware b398 based

{
"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"
}
Huawei P8 Custom ROM
* MagicArrow *
Version Two
Magisk Edition and Classic Edition
Teamwork by Tecalote and KangV
Based on the European firmware b398 - only installable, if you are already on Marshmallow Firmware (Android 6)
Developed on GRA-L09 C432 - but it should run on all GRA-xxx models and regions due to my modification
Thread for German Users: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-rom-6-0-emui-4-0-3-magicarrow-v2-by-tecalote.819399.html
Well, you've been waiting long enough I am pleased to present you the new version of Arrow under the extended name "MagicArrow"
1) Difference between Magisk and Classic Edition:
The Magisk Edition was made to have a safteynet capable device that still offers much more features than Stock Firmware ... It has the same features like Classic Edition, with one difference: Outward It looks as if you had not unlocked the bootloader .... Apps like Pokemon Go, various banking apps - which does not work anymore on rooted devices should work in this Rom
However, you can not install Xposed Framework in the Magisk Edition without losing the green safetynet! There is the systemless Xposed Framework by topjohnwu, the developer of Magisk and it works, can be easily downloaded and installed in the Magisk Manager via modules (SDK 23) - but - there is currently no way to pass safetynet with a modified custom Rom together with Xposed Framework! For this reason, the installation pool in K-Settings for Xposed is removed from its function.
Attention: Update the preinstalled Magisk with newer Version 15.3 flashable zip made for this ROM: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Then look in the Thread for new posts about future Updates.
The Classic Editon is rooted with SuperSU and has same features, but you cannot bypass safteynet check. However, who does not run apps depending on this "questionable" service will have the same joy with this Rom. The advantage of the Classic Edition is: You can install from K-Settings Wanams Xposed Framework 87.1 and use a lot of Xposed modules ...
2) Requirements and information for this Rom:
If you want to have the best of this Rom, then it would be necessary to start completely clean - means from Custom Rom back to Stock Firmware b398 - With the exception of devices for which there is no more recent firmware than b370. An EMUI Custom Rom is as good as the before installed Firmware in the background. In principle, only system, cust and kernel will be flashed with the Rom zip. The original Firmware update a lot more, like modem etc. Therefore, the Custom Rom works best if you start from latest firmware for your device on which the Rom is based.
If you have already latest official Huawei Stock Firmware installed, it is less work...
I really dont recommend to flash dirty this Rom directly from Arrow v1 or if you stay on older Firmware. System and Apps will be wiped with the installation script. So you cannot keep your previous apps and data, you have to install them new.
You need the latest TWRP:https://dl.twrp.me/grace/twrp-3.1.1-0-grace.img Do not use older ones!
The bootloader must be unlocked. Pick up the Huawei unlock code, because it is always valid for the same device. If you do not have an unlock code from Huawei and have problems to get it from Huawei Website, recently you can call regional Huawei service hotline and get the code by mail during 24 hours.
3) Installation guide for the MagicArrow:
1) Backup your apps and data from your current Firmware or Rom - but only User-Apps and not System-Apps. You can use Huawei Backup as well as TitaniumBackup. (Dont restore any System-Apps from previous system in the new Rom - example: if you use Huawei Backup dont backup Phonemanager, but you can backup desktop layout, sms, calendar, User-Apps etc.) Dont backup and restore Chat-Apps like WhatsApp, Viber, WeChat, Facebook and so on - use their inbuilt Backup Function like Google Drive Backup (its different, some Apps are storing everything on their server like Telegram) You must install and register Chat-Apps new on your new Rom. If you dont do that, Push-Notifications cannot work.
2) Make a backup of important folders and files from your internal storage (DCIM, WhatsApp folder, Downloads....)
3) Download Firmware update.zip - depending on the device model - and unzipp it on your PC - you receive META-INF and UPDATE.APP
GRA-L09C432B398: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v88316/f1/full/update.zip
GRA-L09 with other Cust: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA-L09&firmware_page=0
Other GRA models: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA&firmware_page=0
4) Copy UPDATE.APP and META-INF into a folder on the root directory of your external SD which must have the name: dload
5) If you are on Stock Firmware, not rooted you can directly update your Firmware. But go to step 6
A) If you are on Stock Firmware, but rooted, with TWRP installed and Xposed Framework installed, uninstall first Xposed Framework, reboot to system, after unroot your device, restore original boot.img and flash the original Huawei Stock Recovery.
B) Arrow Editions: If you have Xposed Framework installed, uninstall Xposed Framework, reboot to system (15 min) - after go to step 6
If you are on Arrow v1 Classic Edition without Xposed Framework, flash Huawei Stock Recovery from K-Settings /more settings / flash recovery - flash official recovery. You can reboot directly from here to Stock Recovery.
If you are on Arrow v1 Magisk Edition without Xposed Framework, flash with TWRP Magisk Uninstaller: http://tiny.cc/latestuninstaller and after flash Huawei Stock Recovery b391 (by choosing img): https://www.androidfilehost.com/?fid=529152257862705190
- go to step 6
6) Press Vol+ and Power Button until phone reboot and hold this position until phone boot up to Stock-Recovery. Here you do first "Wipe Cache Partition" and second "Factoryreset" - go to step 7
7) If you start EMUI Update from here, just go to Restart and press Vol+ and Vol- (in the middle down and hold this position), wait until phone reboots and EMUI Software Installing begin (of course, update.app and meta-inf must be already in dload folder)
If you was back in system between you can start update with pressing down Vol+ and Vol- in the middle and at the same time pressing Power Button. Wait until phone reboot and you see Huawei Logo. Now you can release Power button, but you must keep holding all the time the pressing down postion with Vol+ and Vol- until EMUI Software Installing begin. After some time your firmware is updated and restart to system. Dont make an account yet, just make short setup.
8) Open settings /about phone and klick 7 times on build number for enabling developer options. Open developer options and in there enable USB Debugging. After go to settings / (advanced) settings and enable "unknown sources"
9) Connect your device with USB to your PC and let windows install the drivers or install HiSuite (which installs drivers if windows cannot recognice) You need the USB Connection. With Minimal ADB and Fastboot in administrative mode you can flash now the newest TWRP, which I have linked above.
10) Disconnect your device from USB Cable, soon TWRP is succesful flashed
11) With Vol+ and Power Button reboot your device to TWRP - this step is important if you want to keep TWRP
12) Allow system modification and go to ADVANCED WIPE - choose in the first step ONLY internal Storage (nothing else). Do not wipe internal Storage together with the other partitions in step 14! Soon internal storage is wiped, go back to main menu and restart the recovery. You should get the Root Permission request from TWRP "Allow system modification" once again, allow it and open settings to configure (24h clock, language, time zone, etc) If you dont get the Root Permission request from TWRP yet, you will get it after next boot to TWRP.
13) Now copy MagicArrow.zip to your external SD - Attention: If you want the boot sound to be played on the phone - before flashing the Rom, sound must be switched on!
14) Boot to TWRP and go to ADVANCED WIPE - Wipe following partitions:
Dalvik/Art Cache
Cache
Cust
data
system
15) Go back to main menu and flash MagicArrow. After flashing is done, reboot system without wipe of dalvik/cache. As you know, the first boot process can take up to 15 minutes (just like installing the Xposed Framwork)] After boot to system and first setup - you have to make some IMPORTANT STEPS (see next Point) before you restore /installing your apps and adjust your phone.
4) Important information for the Magisk -Edition:
During first setup you may receive a root-rights request, if so, confirm this. After first setup - please do not open the Magisk Manager . Before you do anything else,open settings / about phone and klick 7 times on build number to enable the developer options. Open developer options and in there enable USB debugging! Then go back to Settings - in the b398 there are the extended settings with the short name: Settings. In it, please enable " allow unknown sources "
At this point restart immediately your P8.
Now open the Magisk Manager, the app is looking for updates - to speed this up, drag from first white field (like refresh of a website in Chrome) with the finger pressed down - the manager is up to date. Makes a query of the Safteynet = green.
Then you go in the Magisk-Manager left to the Controll-Pannel to settings. Do not change anything, with one exception: enable systemless hosts! This step is very important. Then immediately the second reboot .
Next open AdAway and activate the hosts file (download files and activate the advertising block) - then the third reboot .
After open AdAway again and see if the hosts file is active, if it is, all well, if not, download the hosts files once again and restart P8. (Sometimes another reboot is necessary at the point) Only when AdAway is green (activated) - then the safetynet is passed by. You can now again check in the Magisk manager safetynet = green - if you do not these steps, you can break the safetynet. In addition, root and apps can be blocked!
As you know, Magisk uses his own superuser, integrated into Magisk Manager
For some reason if you have problems with safetynet with some apps, just download the following module in the Magisk Manager in the Control-Pannel under Download:
Universal Safetynet Fix
Otherwise, please do not download any modules, you do not know if they run and what they do.
Two modules are preinstalled - please leave this, otherwise this Rom does not function properly with K-Settings!
5) Important information for the Classic -Editon:
The Classic edition gets systemless Root during the installation by SuperSU 2.82 SR1 (SR1 has an integrated update for Huawei devices). After Rom is flashed and you restart phone, the first boot process will terminate, the device will restart once again - this is normal because of systemless rooting . Why systemless this time? Because of compatibility with SuperSU. The new versions of SuperSU are rooting always systemless. If there is the next Final version of SuperSU, you need only flash the zip in TWRP and there are no problems with the update.
To enable AdAway , just download the AdAway ad block (hosts file) and reboot the P8 - but after rebooting, please open AdAway again and see if it worked the first time - otherwise just download again and restart the device once more. The second time it fits. AdAway is controlled by the systemless root using an init.d script that mount the hosts file systemlessly and this script is usually only active after the second restart. If you ignore this step, you can block root privileges.
6) Features:
• VoLTE and IP-Calling enabled - disable it, if your mobile provider dont support it!
• Push notifications working - Enable WhatsApp, Telegram... as protected apps and enable Wlan and mobile data during "sleeping mode" as always on
• Most Gapps contained in system debloaded - please dont flash any GApps, just install it with Playstore (Core GApps and settings are present in the Rom)
• System is deodexed
• pre-rooted: Classic Edition by Chainfires SuperSU 2.82 SR1 - Magisk Edition by topjohnwuMagiskSU 13.3
• BusyBox 1.27.1 - Please dont change this BusyBox to any other (not Stericson, not JRummy...)
• Call Recorder - You can enable recording manually, if a call comes through with the memory icon in dialer - or constantly in dialer settings
• Some nice themes, BlackPyramid ...
• K-Settings - as usual with extended restart menu
• MiXplorer (very powerful Root-Explorer) and TitaniumBackup (can store backups without any problem through storage SD instead of document provider)
• Dolby / Atmos for Teamwork with Viper4Android - best experience with BlackPlayer (or similar) but not Huawei Music App
• Security patch level 1 July 2017 - all known Stagefright Security holes are closed
• Multiwindow mode - you can start this mode with long tap on square in navigation bar. Close the Mod in the middle with the turquoise symbol.
• Viper4Android (enable it via K-Settings) can be linked to its settings permanently in notification bar for quick access. - as usual.
• Xposed Framework of Wanam included in K-Settings, Installation start from there, reboots automatically. The Restart needs about 15 minutes.
• VIA Browser instead of Chrome
• AdAway - newest release
• And much more...
7) Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
8) Disable Chinese Letters:​
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To hide these, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
9) Save Battery:
NFC (with Android Pay) ist enabled by default - disable it and enable it only for the time you need it
VoLTE is enabled by default - disable it, if your mobile provider dont support it
Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
With "auto app-launch" (if you have installed) you can disable Apps which you use just sometimes.
Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
9) Download MagicArrow:
MagicArrow Classic Edition: https://www.androidfilehost.com/?fid=889764386195920974
MD5: 5ee32443300f10dcbced4808101aff42
MagicArrow Magisk Edition: https://www.androidfilehost.com/?fid=673368273298976764
MD5: 7afa8619778a81a11a60665f27b2289f​
Magisk-Update to 15.3 - use only this zip from this post please: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Please check the MD5 after the download! Because if the download / the zip is faulty - then you have problems after the flash!
And please keep to my instructions - then everything is as it should be
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - fell free to donate KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, I am happy about some beer: https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@dkionline - Custom Roms for P9
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10
​
Last Thread Update: 03.01.2018

Right settings for Push Notifications and install manual for Stock Firmware Update
Right Settings to make Push-Notification work for Chat-Apps like WhatsApp:
Settings with Phone Manager:
1) Once you have installed with PMPlus the Autostart-Manager called: App auto-launch as a part of Phone Manager- WhatsApp, Viber and all those apps must be activated!
2) Activate these applications also in Protected apps
3) In Notification center activate for these applications - Priority display, Status bar, Banners and Lock screen
4) If these apps are available in Dropzone management - activate them
5) In Phone Manager /open Akku-Manager (Remainning) and in this mask open the settings-symbol above - deactivate Power-intensive prompt and deactivate "Close excessively power-intensive apps" and some lines below:
Activate: Keep Wi-Fi on when sleeping ALWAYS - Keep mobile data on when sleeping
Settings with Permissions and Notifications:
1) Open settings /Apps and search for WhatsApp. In this mask you find Permissions- and Notifications-Settings , go inside of both and set the needed permissions for the app and also "Alllow Notifications" and Priority display
Settings in Developer options:
1) one point after "use legacy DHCP client" - set: Mobile data always active
Additional Settings:
1) Settings /More - Open Mobile network and set: Mobile data - and Enable always-on mobile data
2) Open Settings /Wi-Fi and go to menu in the right corner below "Advanced setting" - set: Keep Wi-Fi on during sleep ALWAYS
3) Open Settings /Notification panel & statusbar - activate: Notification panel "Allow notification panel to be opened from the lockscreen if not password protected
4) Open Settings /Screen lock & passwords - activate "Show detailed notification info" and activate optional "Notification turn on screen"
For most users of ARROW Push-Notification for Chat-Apps are working now as they should (whitout converting them to system-apps like in Gratitude before) -
And for most users battery life is much more better than in Gratitude or in Stock Firmware.
But for some users not!
- Notifications coming not constant or not at all - andBattery life is worse than before - How can that be?
Answer: The complete different initial situation and sometimes also the settings.
Initial Situations (examples):
User A updated Lollipop with Stock Firmware to Marshmallow a long time ago (example: from b200 to b317) - after he was going to Custom Rom "Gratitude" - and from this time he was never back to any Stock Firmware and flashed new versions of Custom Rom always dirty.....
User B was also last on b317, after on "Gratitude" and flashed every new version clean, with Fullwipe.....
User C was last on b321a, after on "Gratitude" and flashed every new version clean, with Fullwipe but Arrow dirty....
User D was on Gratitude 5 and then he go back to Stock Firmware b370 - from there with OTA to b382 and after he flashed TWRP and did a Fullwipe before installing ARROW - this user has the best starting position! And for this user ARROW should work as provided
Why?
Custom Rom can only modifiy on Huawei Devices following partitions: system - cust - vendor (and nothing else!) Modem Updates, Updates for Push-Notifications and other sync services or battery software updates are coming with official Firmware!
The best performance for ARROW is given, if your Marshmallow Firmware and Bootloader and Modem.... is also up-to-date.
There is no need to do following steps, if you have flashed ARROW and everything is fine for you.
I would recommend to go back to Stock Firmware as an step between - before flashing ARROW - for Users which come from Gratitude and for Users which have already ARROW installed and issues with Push-Notifications or too much battery drain!
(STOCK-RECOVERY AND UNROOT IS REQUIRED - AND YOU NEED ALWAYS FULL FIRMWARE FROM CUSTOM TO STOCK) - see install manual below!
The Full-Firmware you download (no OTA Files please) should be minimal b370 (which is available for all models). After this EMUI-Installing with reboot to system you can use in settings the Update-App to receive the next OTA Update and install this also. If the Update-App says after installing "no more Updates available" it is okay!
Normally you can use one Full-Firmware above b370, for GRA-L09 it is b382 - alternatively you can use b391 - but a higher version like b391 seems not work (cause Rom is based on b391)
Complete List of Huawei P8 Firmwares (for all models and cust v.): http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra
GRA-L09:
GRA-L09 Full Firmware b370: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v54178/f1/full/update.zip
GRA-L09 Full Firmware b382: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v69133/f1/full/update.zip
Attention: Bootloader may closed after update with Firmwares above 390 (even if showing in fastboot mode as open - but cannot flashing TWRP "command not allowed" - needs unlock Bootloader again)
GRA-L09 Full Firmware b391: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v71319/f1/full/update.zip
Complete list for GRA-UL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul00
Complete list for GRA-TL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-tl00
Complete list for GRA-CL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-cl00
Firmware for GRA-CL10: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v73798/f1/full/update.zip
Complete list for GRA-UL10: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul10
Install manual:
To go back to Stock Firmware you have to do following steps:
1) Backup what you need to backup! Use Huawei Backup and also Titanium Backup. NOTE: But dont restore in the new ARROW then system-apps or data from system-apps from previous system! Restore only USER-APPS. For Chat-Apps like WhatsApp, Viber, Skype use the built-in Backup function - but keep or backup the folder from those apps on internal memory (because you need them on the same place if you reinstall those apps)
Battery must have minimal 80% doing those steps....
2-A) Users of Classic-Edition: Open K-Settings /more settings /flash recovery - Flash official Recovery (grant Root-Permission) - this flashes Stock Recovery in half a second.
2-B) Users of Magisk-Editon: Please go to TWRP and flash Magisk-Uninstaller.zip to unroot your Phone. Users of Gratitude Magisk Edition should also flash unsu.zip (both linked in OP) After reboot make a connection with USB to your PC. With Minimal ADB and Fastboot program (on PC) flash Stock-Recovery. If you dont know how to do, ask me in this Thread. Download: https://www.androidfilehost.com/?fid=529152257862705190
If you have Xposed Framework installed - uninstall it (Magisk Users in Magisk Manager/Modules - Classic Users in K-Settings /Xposed Settings /Install Xposed confirm - Reboot needs about 15min)
3) Download the Full Firmware for your model, unzipp it on your PC (mostly you get update.app and meta.inf)
4) Create a folder on internal memory or external SD and name it: dload
5) Copy only update.app and meta.inf (if meta.inf is present) in this folder. After DISCONNECT USB from Phone!
6) Reboot to Stock Recovery - with Restart menu (also possible with pressing Vol+ and Power-Button at the same time as long until Recovery is displayed)
7) Wipe Cache with Stock Recovery (it uses another engine than TWRP) and do after a Factory Reset. There is no need to restart the phone to system now. Go to:
8) Press Vol- and Vol+ (in the middle) and Power-Button at the same time, until phone reboots and EMUI-Software-Installing is displayed
9) Let the EMUI-Installing finishing - it reboots automatically to system and starts the EMUI-Optimizing - wait until Language-Selection is displayed. Make a short set up (You can skip the most) - but it is important to arrive the homescreen.
10) Go to Settings / About the phone and tap 7x (times) on Build-Number. It activates developer options.
11) Go to Developer options and activate USB DEBUGGING - after open Advanced settings /security and activate "Unknown Sources"
12) Connect Phone with USB to your PC (Accept the Fingerprint query with "always" on your Phone) Look, if Windows installed the right drivers so you have access to phone - if not install HiSuite http://consumer.huawei.com/minisite/HiSuite_en/index.html and make a connection with HiSuite. Allow installing HiSuite on Phone. If you have access now, close HiSuite (also in Background).
13) Copy ARROW-Rom to your Phone.
14) With Minimal ADB and Fastboot flash TWRP: https://www.androidfilehost.com/?fid=529152257862681510 - if you are unsure with the right commands, ask me in the Thread.
15) DISCONNECT USB Cable now from your Phone
16) Press Vol+ and Power-Button at the same Time until phone reboot (at the moment, Huawei Logo comes you can leave Power Button, but keep holding Vol+) Reboot to TWRP takes a while
17) Set up TWRP (allow modification, set language, screen timeout, time zone...)
18) There is no need to wipe internal SD (but if you like to do this, do it at first and restart after TWRP - then you must setup TWRP again)
18) Go to Wipe, Advanced Wipe and wipe: Dalvik&Cache, Cache, data and system
19) Install ARROW Rom
20) Restore User-Apps, but dont restore any System-Apps (or data from it) Chat-Apps install from Playstore, and use the built-in restore function.
ARROW should work now as ist should!

Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:

Hucast_DL said:
Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:
Click to expand...
Click to collapse
Thank you

Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?

00471 said:
Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?
Click to expand...
Click to collapse
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...

Tecalote said:
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...
Click to expand...
Click to collapse
i will try dirty reflash it with mounted data and let you know :good:
EDIT. reflashing fixed it and app appeared, thanks for halp @Tecalote

To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs

lespaul79 said:
To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs
Click to expand...
Click to collapse
Thanks a lot

Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?

enzoade1994 said:
Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?
Click to expand...
Click to collapse
Hi
Written in OP
"In ARROW are not included Chinese letters, with the exception of "Lunar" - which comes with K-Settings. Gratitude users know how to get rid of them. For all others:
1) Go to K-Settings, in there to:
2) Notification Settings / Show "statusbar lunar" - deselect.
3) Go to Lockscreen and desktop settings "Lunar calender + desktop wheather lunar" - deselect."

Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.

Ammar_ said:
Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.
Click to expand...
Click to collapse
Hi Thank you for your feedback!
You have installed the ROM on the Middle Eastern variant UL00C185...
I am glad to hear that it not only works on GRA-L09
This is what I promised, but I wasn't 100% sure - cause I have only L09...
I am interested which build number is displayed in "About the phone"?
Thanks!

Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.

rodlane said:
Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.
Click to expand...
Click to collapse
Hi there Automatic Call Recording can be enabled that way:
Open the Dialer App - below left is a star, below right is the symbol for the settings menu. Open it and there you can enable automatic call recording.
For the other issue: Can you give me a link to an African Marshmallow Huawei Stock Firmware? So I can look at it and perhaps include the Region.
Which Region did you set up right now?

Thanks very much man!
Flashed it last night, after it took me half an eternity to backup all my files (had something messed up so I had to look a bit deeper). Flashing and all was fine, including xposed via magisk.
Been using it the day now, but at 2 Things im not sure if it is caused by the Rom or by the latest whatapp update:
-in widgets i can select WhatsApp - but there is no more this huge 4*2 widget with message-preview, does anybody else have this? (only WhatsApp Chat and WhatsApp camera available there)
-even though i have given WhatsApp all permissions, my Screen won't wake up when i receive a message. It was quite usefull while the phone lay at my table i could see in one glance whether or not it was important and decide to pick it up
....okay i have tried a bit and found out my Screen also won't wake up after receiving sms or email.. where could i look after that? every app has "Show on lockscreen" enabled
There was another thing, which i could't read fast enough, but it was something with kvip Settings and some overlay permissions and a path where to find them or so?
it popped up a couple of times at the beginning (those little messages in the lower middle of the Screen, just like "wifi connected") next time i will try to make a screenshot of that.
edit:
@Tecalote congrats for 500 Posts and 300 likes! :good:

@Tecalote your ROM IS ****ing awesome, congratulations!!!
Enviado desde mi HUAWEI GRA-L09 mediante Tapatalk

@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Edit:
For enabling the Wakeup on Homescreen - you must go to Settings /Screenlock and Password - and there set up : Notification turn on screen!

Tecalote said:
@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Click to expand...
Click to collapse
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Edit2: I think in those Messages i was talking about it wasn't Overlay - it was Dropzone. But still no clue what i should do there, everthing is allowed that wants to be

ChavezD said:
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Click to expand...
Click to collapse
Hi again You can stop Google from downloading the previous installed Apps at the first start. After Google Login you will be asked if you want to restore - just deny.
Don't know yet what you exactly mean with 4 rows in the same time.
Do you mean perhaps Toast Messages? There's for example an Xposed Modul called "Perfect Color Bar" - in this you can enable "Toast" with mixed compatibility. After you get instead of the the small black info messages colored ones with the symbol of the App message. There are also other "bars" on the Repo for customization that messages.
Do you remember which official firmware did you have before using Custom Roms like Gratitude? b317, b321a, or b370? I know, there were some modem updates coming with the official firmwares (which cannot be done with Roms on Huawei Phones)
Maybe you should update to officially Firmware as an step between before reflashing the Rom. For this you would need the Stock Recovery, which can flashed from K-Settings, more Settings. On xda you can find the b391 here:
https://forum.xda-developers.com/huawei-p8/how-to/firmware-huawei-p8-b391-gra-l09c432-gra-t3534020
It would refresh the Rest of your Phone (which cannot be reached by ROM) - and after the ROM can work as it should...
Just an idea

[RECOVERY][OFFICIAL] TWRP for Galaxy S9 and S9+ (Exynos)

Team Win Recovery Project
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
#include <std_disclaimer.h>
{
"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"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy S9:
https://twrp.me/samsung/samsunggalaxys9.html
Galaxy S9+:
https://twrp.me/samsung/samsunggalaxys9plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - Discussion, Testing, Feedback and Support
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
To contribute:
TWRP Code Review
Github pull requests will be ignored.
XDA:DevDB Information
TWRP for Galaxy S9 and S9+, Tool/Utility for the Samsung Galaxy S9+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2018-03-15
Last Updated 2018-08-15

Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
USB connection fixes
Mar 14, 2018:
Initial version

Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Since Android O, Samsung introduced a new security feature, Remote Mobile Manager (RMM) aka Remote Lock Control (RLC). This feature allows stronger theft protection but unfortunately it also imposes a burden on users like you.
Samsung added a 7-day buffer period for enterprises or device owners to spot a missing/rogue device so they can use this feature to lock the device remotely.
In this 7-day (Prenormal) period, you can NOT flash any custom binaries including but not limited to this TWRP. OEM Unlock option won't appear, either.
(You will meet "custom binary blocked due to remaining installment balance" or "custom binary not allowed" error when you try)
The 7-day timer will start/reset once you completed the setup wizard. After 7 days (168 hours), RLC service will send an inquiry to Samsung's server. If your device is "clean", the RMM state will become "Normal".
Then you can enable "OEM Unlock" option and flash TWRP. Be careful, DO NOT reboot to a stock ROM before you flash patch in part 2 of this guide or you will have to go through another
Whether you have RMM problem or not depends on your model, region and/or carrier.
If you don't have any wait period to enable OEM Unlock option, congratulations but please do NOT mislead other people.
NOT EVERYONE IS AS LUCKY AS YOU.
If you don't have RMM problem when you get the device, it is unlikely that you will get any RMM problems later.
But note that this problem applies to MAJORITY of people.
Note that the special patch will freeze RMM, FRP and OEM lock state.
This is an anti-stupid measure to prevent careless users from enabling security measures which are not compatible with custom binaries.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings, remove all Samsung and Google accounts and if your device is registered to an enterprise, de-register it.
3. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
NOTE: You will be asked to do a factory reset, that's normal.
BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.
You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.
4. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
5. Download and extract Odin (Samsung's Flash Tool) to your computer.
6. Download a .tar image of TWRP.
7. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
8. Open Odin and place that TWRP tar file in the [AP] slot.
9. Connect your phone.
10. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
11. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP:
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO".
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
Now you may want to flash a root solution (Magisk, SuperSU, etc) or custom ROM but keep in mind that:
1. This thread does NOT provide technical support to any root solution or ROM unless the problem is DIRECTLY related to TWRP and there is no other solution without modifying TWRP itself.
Please contact developer of respective ROM or root solution for technical support.
2. Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection". https://www.samsungknox.com/en/blog/real-time-kernel-protection-rkp
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.

Awesome work Jesse. Thank you!

Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk

@jesec hey mate, happy to see you again (S7 ROM)
Sorry i don't have this device but my friend will try soon

spackeddie01 said:
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.

BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset.
Click to expand...
Click to collapse
Please boot to recovery instead of system.
Be aware that Android Verified Boot requires data to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data,*all*state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot) It is normal to get such prompt.

Got twrp installed formatted data, rebooted twrp, do we need Dm-Verity? If so how to get it on as MTP is not working, or OTG, and system bootloop so can't get back in to do it that way.

BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
Click to expand...
Click to collapse
You have to flash dm-verity/magisk.

****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.

iamnotkurtcobain said:
Awesome work Jesse. Thank you!
Click to expand...
Click to collapse
Dis you try treble AOSP ?

giorgior.r said:
Dis you try treble AOSP ?
Click to expand...
Click to collapse
I can't. This TWRP is for 9+. I have a normal S9.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
BokkieAndijk said:
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
Click to expand...
Click to collapse
You formated system it seems.
Steps are:
-flashing TWRP
-boot into TWRP
-format Data
-reboot recovery
-install magisk
-reboot

iamnotkurtcobain said:
You have to flash dm-verity/magisk.
Click to expand...
Click to collapse
pls can you give me a link to the packages you have used?
Thanks.:good:

Nice to see you doing work on the S9 @jesc

deleted

@jesc good to see you in the s9 forums. Great work as usual

Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.

BokkieAndijk said:
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
Click to expand...
Click to collapse
check in this site
https://www.sammobile.com/firmwares/database/SM-G965F/

Flashed twrp then flashed no dm verity - seemed to flash ok - but saw one error message that says "failed to mount '/cpefs' - I haven't seen that error before but thought it might be important. THis message happens after the flash has finished -(after it says updating partician details)
Tried to flash magisk after I flashed twrp and phone bootloops had to flash stock in odin

How to ROOT Samsung Galaxy Tab Active 2 T395 - SOLVED !

First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!

How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.

Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!

I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.

[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)

Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you

oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.

RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew

Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,

Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.

Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.

Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt

Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?

Hello, did you manage to remove the "format as internal" lock?

Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?

alguma fortma?

(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only

How to ROOT Samsung Note 9 N960F/FD/N
Before trying make sure that flashing said file,
- Warranty will be void
- You won't be able to use Secure Folder/Samsung Pay forever (or may be more)
- May lose OEM unlock option
- Backup important stuff as you need to full wipe device (including internal storage)
DO IT ON YOUR OWN RISK
What is OEM fix?
Since Note8 samsung have introduced OEM unlock control remotely and flashing any custom binary removes OEM unlock option and rebooting in this state it ends with custom binary error and have to flash stock firmware. OEM patch will retain OEM unlock option in spite of having custom recovery. If you are not sure your device have OEM issue then there is nothing wrong to use 'OEM patch' option.
If you don't have OEM unlock option out of box then it may appear after 7 days, before this nothing can be done. Also this suggest, you have OEM affected device.
Click to expand...
Click to collapse
METHOD 1 : Root with TWRP Also works on Android Q (RECOMMENDED)
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for N9
5.Switch Off device
6.Press Vol down + Bixby and connect to PC to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14A (If you are on Pie)
.Now select Install and navigate path to Ext SD card - N960_root_OEM_issue_devices_V*.zip, you have copied earlier, select desired root method and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
OR
14B (If you are on Android Q)
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
Credits and Thanks goes to BlackMesa123 for OEM fix
Click to expand...
Click to collapse
METHOD 2: Root with Stock Recovery (NOT SAFE ON OEM ISSUE DEVICES)
1.Download Magisk.apk attached below
2.Download Prerooted_N960_Exynos.zip (For Oreo Only)
3. Keep stock ROM file ready in case this doesn't work
4.Download De-Knox tool attached below (optional)
Installation :
- Enable OEM unlock
- Reboot to Download mode
(Here method changed - Switch off device - connect top PC - Press Vol down + Bixby)
- Extract (Unzip) Patched kernel - you will get N960F_kernel_PreRoot_RH5_DrKetan.tar.md5
Flash it using latest Odin with AP tab
- Once file successfully flashed, device will reboot and ask to reset device.
- Reset device, keep patience, device may take 5-7 minutes to boot.
- Once device reboot - Install Magisk manager apk manually
- install De-Knox tool apk and click icon, this will remove all knox app (no more useful on rooted device). This will also remove security messages
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
Click to expand...
Click to collapse
14.01.2019 - Added support for Pie
Credit and Thanks to breakersvd for ril patch (defex fix) and @topjohnwu for magisk
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users attached below.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM

So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.

chrispyutec said:
So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.
Click to expand...
Click to collapse
No, on previous device you get oem unlock option back again after 7 days
Though this is csc related and not all users will lose this option. Usually if your device have unlock option out of box then mostly you won't lose it. Though if we get root working we may need move forward to fix this

When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril

Here you see the half working root with ril. Normal magisk will break ril like i said

geiti94 said:
Here you see the half working root with ril. Normal magisk will break ril like i said
Click to expand...
Click to collapse
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.

dr.ketan said:
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.
Click to expand...
Click to collapse
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one

geiti94 said:
When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril
Click to expand...
Click to collapse
Wow! Wtf Samsung!!!??

How did you manage that half working root ?

siriom said:
How did you manage that half working root ?
Click to expand...
Click to collapse
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same

geiti94 said:
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same
Click to expand...
Click to collapse
If you to open a prompt and su ? would that work ?
I would like to mount or chgroot ....
This obviously blows up the whole knox deal right ?

geiti94 said:
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one
Click to expand...
Click to collapse
It's up now

FINALLY ROOTED NOTE9
May be Worlds first fully rooted Note9
Big thanks goes to @breakersvd for his special hex fix for recent samsung devices.

I will re-write first post with new files soo

Amazing @dr.ketan ??

Amazing @dr.ketan ??

Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?

Plzz let us know how to fully root note 9 dr.ketan
Plzz update file and root process .. i am very excited to root my note 9 .. dr. Ketan u r the best.. love ur work????

Nasty_z said:
Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?
Click to expand...
Click to collapse
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done

pankajgavri said:
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done
Click to expand...
Click to collapse
Yes, I know. I asked about ota after unrooting. I can still get ota if I unroot?

[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk

I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed for the Tab 10.1 (2019)).
It's been quite some time since I published a tutorial on XDA. So, I decided to put up this comprehensive tutorial, hope it helps everyone who's looking for it. We will take the direct approach of rooting the tab by patching the AP firmware and flashing the patched AP through Odin.
/* I will be using the same images I prepared for the tutorial to be posted on my blog. Sorry that they have been watermarked, that is to prevent scrapers from stealing. It took me enough time to capture them and do some post-processing. */
Before we start, here's the obligatory disclaimer and warning:
Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
If you do land your tablet in trouble, feel free to ask, I shall try my best to help.
Click to expand...
Click to collapse
Update log
Updated on March 2, 2021
Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
Click to expand...
Click to collapse
Requirements
Your Galaxy Tab A7 with SM-T500 or SM-T505 model number
A compatible USB-C cable
A Windows computer. (Odin only works on Windows. If you're using Linux or Mac, you could try Heimdall)
Instructions
Step 1: Enable OEM Unlocking
In order to unlock the bootloader, you must first enable the 'OEM Unlocking' toggle. This toggle resides inside the 'Developer options' screen, which is hidden by default on most Android devices.
First, enable 'Developer options' by going to 'Settings' > 'About tablet' > 'Software Information' and repeatedly tap on the 'Build number' section five times. If you have a lock screen security set, you will need to input your PIN/Password/Pattern when prompted.
{
"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"
}
Once you do this, you should see a toast notification on the bottom of the screen saying that "Developer mode has been enabled".
Once that is out of the way, go to 'Settings' > 'Developer options' and turn ON the toggle next to "OEM unlocking". You will instantly be prompted to enter your PIN/Password/Pattern, so do it. Then select "Enable" to allow OEM unlocking.
Note: If the OEM unlocking toggle is grayed out, make sure that you have connected the tablet to the internet first (via WiFi or mobile network, your choice).
Step 2: Unlock the Bootloader
Start by powering off your tablet completely. Then while holding the Volume Up and Volume Down keys together, connect it to your computer using the USB cable. This should take you to the bootloader screen (I call it that because logically that's what directs you to either Download Mode or Device Unlock Mode). Long-press the Volume Up key to enter the 'Device unlock mode'.
Your tab should now prompt you with a confirmation screen, so press the Volume Up key to confirm and unlock the bootloader.
Your Tab A7's bootloader is now unlocked and it should reboot automatically. You should also see a warning message right before the Samsung splash screen, just as shown in the picture below. Don't worry, it's completely normal. And no, there's no way to get rid of it (unless of course, you relock the bootloader).
The first boot after unlocking the bootloader could take some time (took around 3-4 minutes for me). So be patient.
Now that the bootloader is unlocked, let's verify it. Samsung introduced a new feature known as "VaultKeeper", which will automatically relock the bootloader if you do not perform this step.
After your tab boots, connect it to the internet. Then enable the Developer options as shown in step #1 and go to 'Settings' > 'Developer options'. The OEM unlocking toggle should be greyed out and say that the bootloader is already unlocked. Again, refer to the picture below.
Step 3: Download the firmware package
With the bootloader properly unlocked, you can begin with the rooting part. As I mentioned, we will be patching the AP firmware file via Magisk App, as instructed by John Wu in his installation guide on Github.
So, you will need to download the firmware package for the software version that's currently installed on your tab. This is very important, do not use an older firmware, as it will result in issues. You could of course use a newer firmware, which will update your tab at the same time as rooting it.
To verify your software version, you can go to 'Settings' > 'About tablet' > 'Software information' and check the "Build number". The latter half of the mentioned build number is your tab's software version, which in my case as shown in the picture below is: T500XXU1ATJ2. So, I will need to download the firmware package for "T500XXU1ATJ2" and in your case you should download the one corresponding to the info you see under 'Build number'.
Where to download? You could use online FW databases like SamMobile, Samfrew, etc. However, I would recommend using Frija or Samloader as they allow you to download the firmware directly from Samsung's Firmware Update Servers and without any speed caps. If you're operating on Windows, use Frija. On macOS/Linux, use Samloader.
Step 4: Extract the AP firmware and transfer it to your Tab A7
Once you have the ZIP package downloaded, you will need to extract it to get The extracted folder should contain the individual firmware files like BL, AP, CP (only for SM-T505 LTE variant), and CSC/HOME_CSC (in .tar.md5 file format).
The file you'll require is the AP firmware, which in my case is "AP_T500XXU1ATJ2_CL19362637_QB34980135_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS10.tar.md5". Again, in your case, the filename would be a bit different, but it should follow the same structure.
After extracting the AP firmware, connect your tab to the computer, enable File Transfer (MTP) mode on it, and copy over the AP firmware to your tab's internal storage. Copy it to the root directory, that is, outside all the folders as shown below. The location of the file doesn't matter, you can copy it anywhere, but I prefer this for easier access.
Step 5: Patch the AP firmware using Magisk App
Now's the time to patch the AP firmware. To do this, download the latest version of the Magisk app from the official Github releases page to your Tab A7. This will be an APK file. Once downloaded, install the APK file using your choice of file manager.
Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.
Click to expand...
Click to collapse
You do not need to change Magisk's update channel to Beta anymore. Starting January 12, Magisk v21.x was pushed to the stable channel (default).
After installing, go to the app drawer and launch the Magisk Manager app. Before you start patching, you would want to change Magisk Manager's update channel to Public Beta. This is because Magisk's latest version (i.e. v21.0) is only available on the beta channel and hasn't been pushed to the stable channel yet (at least at the time of publishing this tutorial).
To do this, press the settings icon on the top-right, tap on "Update channel" and select "Beta". Then go back to the app's main screen. It should refresh and show you the latest version as v21.0.
Press the "Install" button and then "Select and Patch a File" from the list of available methods. This should open the file selector, so navigate to the internal storage and select the AP firmware you transferred during the previous step.
Once the file is selected, hit "LET'S GO" to start the patching process. This should take a minute or so because the AP firmware is quite a heavy file. Once it is done, the patched AP firmware with the filename "magisk_patched_xxxxx.tar" (where "xxxxx" is an arbitrary code) should be stored inside the "Download" folder of your tab's internal storage.
Step 6: Flash the Patched AP Firmware using Odin
The last step is to flash the patched AP firmware to your Galaxy Tab A7 and root it. For this, connect your tab to the computer over USB and copy the "magisk_patched.tar" file from the Download folder. Paste this patched AP firmware inside the firmware folder that was extracted during step #5, along with the rest of the firmware files (BL, CSC, etc). Disconnect it from the PC after transferring the file.
Now, boot your Tab A7 into Download Mode. Power it off, and connect it to the computer over USB while holding the Volume Up and Volume Down keys together. This should bring up the bootloader screen. Simply tap the Volume Up key once to enter Download Mode. Here's what the Download Mode on the Tab A7 looks like.
Next, download Odin v3.14.1 from this XDA thread (NOT the patched version, but the regular one) and extract the contents of the downloaded ZIP package. Then launch Odin on your computer by double-clicking the "Odin3 v3.14.1.exe" executable and click "Ok" when prompted. You should see the Odin interface on your computer screen now.
Odin should automatically recognize your tab in Download Mode and display the COM ID on the top-left.
Click the 'Options' tab and uncheck the 'Auto Reboot' option. This will prevent the tablet from being automatically restarted after the flash is complete.
Now, load the firmware files in the respective slots of Odin.
The BL firmware file (BL_T500/5XXXXXXX_xxxxxxxxxxx.tar.md5) goes to the "BL" slot
The CP firmware file (CP_T505XXXXXX_xxxxxxxxxxx.tar.md5) goes to the "CP" slot. Note that the CP firmware only applies to the Tab A7 LTE variant with the SM-T505 model number.
The HOME_CSC firmware file (HOME_CSC_OMC_ODM_T500/5XXXXXXX_xxxxxxxxx.tar.md5) goes to the "CSC" slot. We will not be using the regular CSC, as it will erase all the data. If you want to do that, feel free to use it.
And finally, the patched AP firmware file (magisk_patched.tar) goes to the "AP" slot.
Once the files are loaded in their respective slots, hit the "Start" button to flash them to your tab.
Note: While you could get away with just flashing the patched AP firmware alone, John recommends NOT doing it. Always flash the patched AP along with the rest of the firmware files like BL, CSC, etc.
Wait for the flash to finish. Once it is, you should see the 'PASS!' message in Odin. Like so:
You can now close the Odin window and disconnect your tab from the computer.
Step 7: Perform a Factory Reset
Once the flash is complete, you will need to manually boot your tablet into the stock recovery mode and do a factory reset. This is only mandatory during the initial rooting process, which is exactly what we are doing here.
To do this, hold the Volume Down and Power keys together for about 7 seconds. As soon as the screen turns off, release the Volume Down key and quickly hold the Volume Up key, while still holding the Power key. Keep holding the keys until you see the stock recovery screen.
You should now see the stock recovery screen with some device information in yellow color at the top. Like so:
Use the Volume keys to move the selector to 'Wipe data/factory reset' and hit the Power key to confirm the selection.
You will now see a confirmation prompt on the screen. Select 'Factory Data Reset' to confirm and finally perform a factory reset.
Once done, select the 'Reboot system now' option from the recovery's main menu. Your Tab A7 should now reboot may be more than once, so be patient.
We're not done yet. After booting, you will need to open the Magisk app from the app drawer and follow the on-screen instructions to replace the Magisk stub with the actual full application, and further complete the required setup when prompted by Magisk app.
Once this is done, your Tab A7 should reboot one last time and should be rooted thereafter.
Your Tab is Rooted!
You may now go ahead and start using root applications, install some modules, etc. Since v20.4, Magisk Hide has been disabled by default on new installations in light of the new hardware-backed SafetyNet attestation. So, to use banking/security, or any other sort of apps that may detect root, you will need to turn ON Magisk Hide from within the Magisk App settings.
Before you leave, there are a few key things you should note:
Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.
Click to expand...
Click to collapse
That's all from my side. If you run into any issues, feel free to post. Don't forget to share details like the software version your tab is on, the firmware package you downloaded and used, and of course your tab's complete model number.

Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?

jserio said:
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
Click to expand...
Click to collapse
I was really inclined to the Tab S6 Lite. But being honest, I wouldn't have used the SPen that much. So, I dropped it.
I saw Tab A 10.1 (2019), the one you're referring to, and it was a steal for the specs. The reviews were good too. But then the A7 was released, an upgraded model along the same lines. I like it very much. For a budget tab, it really delivers decent performance and a premium-ish design. And, great speakers I must say.
Unlocking and rooting were really fun and easy as well. Overally, it's a pretty darn good tab for the price.

Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.

Gitah. said:
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Click to expand...
Click to collapse
You're welcome!
For me, 3GB of RAM is enough, of course given my usage. I usually use it for browsing and streaming only. Not much of a mobile gamer, use real consoles and PC for that, lol.
I like Samsung's One UI experience, compared to any other OEM skin (apart from OxygenOS). It's quite smooth IMO. Already removed the bloatware via ADB, might as well come with a guide for that.
It could however be different under heavy multi-tasking usage, like playing mobile FPS titles, etc. Couldn't tell on that.

storage problem
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system

You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.

Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I cant seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?

Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse

Cloudxddd said:
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
Click to expand...
Click to collapse
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.

Dj89 said:
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Click to expand...
Click to collapse
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).

paziusss said:
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Click to expand...
Click to collapse
It's more likely to be unit-based. For example, my OnePlus 8 still hasn't been forced to hardware-backed attestation for SN. But my friend's unit (same model and region) has been.
Have you tried enabling Magisk Hide? It is disabled by default. Another thing to try is the Magisk Props module.

jserio said:
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I can't seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Click to expand...
Click to collapse
Could you share a picture of the screen you're referring to?

DJBhardwaj said:
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
Click to expand...
Click to collapse
Thanks for the info! I'll post an update later this week once I get it going! Take care and thanks again for posting this guide!

DJBhardwaj said:
Could you share a picture of the screen you're referring to?
Click to expand...
Click to collapse
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.

jserio said:
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
Click to expand...
Click to collapse
That's great!
As for updates, I think there was a way by blocking the update services using Titanium. Might have to look it up again. I did that years ago. Yes, TWRP would be great for flashing ROMs and NANDroid backups.
I was going for the 10.1 earlier, didn't knew it had one-sided speakers.

I have a question... Unlocking the bootloader and rooting a device are mostly the first steps to a custom rom like lineageos . I find tons of threads for the SM-T510, but not the SM-T505.
Will there ever be a custom rom for the T505?

DJBhardwaj said:
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Click to expand...
Click to collapse
So it's impossible to move apps to sd even with root?

Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?

Allow apps to be moved/installed on SD card
ormefocus said:
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Click to expand...
Click to collapse
Same here i tried on 2 different sd cards(SD- HD) format them from the tablet and no one app won't move to the sd card.
I turn on the develpoers options and i fount this option: Force allow apps on external(Makes any app eligible to be written to external storage regardless of manifest values) and i tried to donwload Asphal 9 and Gangster Vegas and 2 apps downloaded to the internal storage...
I chekt if the options to move apps is visable on this apps and its not.
If any one fine how to transfer apps to the sd card i will very thankful