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

[Resurrection Remix] [Unofficial] [2018-08-19] Treble [Discontinued moved to PIE]

LAST PERSONALLY Verified as working and "stable"*: GAPPS, 8/19 GAPPS
First and foremost, I'm simply compiling this for the OnePlus 6 and am making some small tweaks to include Opengapps and not only Go Apps in the builds.
The parent for this by phhusson can be found at [Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
Next the most important information where to get the most current build of the ROM: Google Drive
For now I suggest the version ending in -go such as: 'rr_6_1_180616_system-arm64-ab-go.img.xz' as the '-gapp' is in development, I expect a number of builds over the next few days as I finally the build scripts and then the rate to tapper off to every two weeks or as there are changes that seem to warrant it, I'm not building nightly for no reason, as RR 6.1 is reasonable stable at this time.
Note: Attached (build.sh) is the build script currently being used, it is a work in progress. and will be updated in case you more regular builds. You will need 12GB of Ram Ubuntu 16.04+ (I'm using 18.04 now, but I started with 16.04) and at least 360GB (SSD recommended) to build, and upto 6 hours for the initial run and then 2 for ever additional run.
Many thanks to phhusson for allowing me to post this based off of his work.
Changes, when I have something to report. Not all build will:
The 7/7 build includes a number of patches recommended by DocRambone.
Overlay support to force Apps fullscreen, Under Display->Advanced
Some cleanups to the UI for the round corners
Better LED support
The 7/8 build is the same as 7/7, but includes July security patches, I built it in order to match the official release.
The 7/24 build is again to match the official release
The 8/19 build is again to match the official release, note regression in status bar height I'm looking into.
Second post: will have details on what is working and not
Third Post: will have full instructions on installation, backup restore based on my experiences
* Stable is relative, for me if I consider it usable from day to day it is stable.

As of 8/11/2018
In the GAPPS version
Working:
Fingerprint
Camera (Front and Back) + Flash (Also got the OnePlus Camera working*)
Speaker
Wifi (Some cut outs seen, this is not unique to this ROM and is dependent on the access port some are worse than others, no clue why)
Bluetooth
GPS
Brightness
Slider for Notifications as of 6/18 build
Mobile Data/Voice (tested dual SIMM is working)
Google Apps
Root (using magisk 16.3), told but have not personally tested that 16.4 without changes works as well
Ambient (works serious effect on battery see next post)
Full Screen Aspect Ratio Display->Advanced 7/07/2018 build+
More fully functional LED Improved for at least mounting USB sticks in 7/7 build
USB Host - Fixed for at least mounting USB sticks in 7/24 build
Bluetooth Phone audio is on the local headset. - Fixed in 7/24 build
Seems working NFC working 5.1.11 Vendor and Boot, not working with previous to 5.1.9 Vendor and Boot I have nothing to connect to to fully test
Not Working:
The Notch hides content (need to wait for P)
Unknown:
Camera Quality: I do little with the camera and am no photographer, so I can say nothing about quality, only it installed and took pictures
VaSU# said:
volte kinda works you can receive messages and calls and can send messages but cant call "out"
Click to expand...
Click to collapse
Please let me know if anything is missing, or needs to be added

Instructions to flash, backup ...
WARNING: With 5.1.8 I had no WIFI, so I suggest sticking to 5.1.6 to 5.1.7 FOR THE MOMENT
Instructions to flash, backup ...
Total time required about 90 minutes
Pre-Reqs:
First and foremost:
Start with at least 5.1.6 (or greater, as of writing 5.1.7 was the lastest), there are Treble fixes in 5.1.6 we need.
Second
verify you have a good USB cable (the Red one shipped with the phone is best)
Three
download the oneplus drivers and abd
- USB Drivers: OnePlus 6 USB Drivers for Windows
- ADB/Fastboot: ADB/Fastboot latest mini
Install both to your local system
Four
Download the latest TWRP (get both the img and zip files)
TWRP for OnePlus 6
Five
Download the files(Treble OP6 Files 5.1.6) from:
GUIDE] How to flash Treble roms on OnePlus 6
Extract and keep: vbmeta.img (if you are on 5.1.X where is the boot version you can keep the boot.img as well, if not discard).
Six
Download the lastest Oxygen OS ZIP and bootloader from:
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As of writing this is:
5.1.6 full image: OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
5.1.6 boot: OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
Seven
Download Device ID:
Device+ID APK
Eight
Download Magisk for Treble:
Magisk modified for treble
Since as of 6/2018 the default magisk does not support Treble we need a special version I suggest: Magisk-v16.3-factory-faizauthar12-20180406.zip as teh latest I could find with support.
Nine
Recommended download fastboot installable 5.1.6 (or latest build):
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Ten
Include Overlay/Ambient Display.
Download APK at: [Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Eleven
OnePlus Camera:
OnePlus Camera APK's
Finally
Download RR 6.0 for Treble compiled after 7/08/2018:
Either download the gapps or go version (gapps is still a work in progress when I wrote this)
ROMs Google Drive
Getting Ready:
WARNING: you will loss all data on your phone, backup anything you want or need, first.
Make sure you can get to fastboot (enable "Advanced Reboot" in developers options and make sure that you can enter on a reboot by pressing volume-down and power at the same time)
Make sure you are on 5.1.6+ (5.1.6 was the latest firmware upon writing this)
Remove Any security you have set (just to be safe)
Reboot to fastboot (bootloader)
run:
Code:
fastboot oem unlock
"You will be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection, allow your device to reboot"
Backup EFS
If you have not already I'd recommend backing up EFS (to do so you need to be rooted, or else use TWRP):
Preferred, if rooted simply open a terminal and run:
Code:
su
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Copy these files someplace safe!
If not rooted reboot to fastboot (bootloader):
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
select only EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Backup the Phone
Recommended if you care: Backup your entire phone using TWRP as well:
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
Select Everything except EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Installing RR:
Finally we are ready to install RR (or any other Treble ROM), on the OnePlus 6. You will need a build from 6/7/2018 or later to have the required Vender-Hal to be present.
You will need to locate and install the AB version for the OnePlus 6.
Note: I'm using RR from 6/13 as the base for the guide: system-arm64-ab-gapps.img
SEE FIRST POST FOR CURRENT DOWNLOAD LOCATION I compiled this using phhusson's (Orginial Build Scripts)
instructions and a bit of setup on Linux. However most Treble base ROM's should work so long as they are from after 6/7/2018 in a similar manor.
* Remember this will wipe your device and you will loss all data *
First
boot in to fastboot (bootloader):
We need to go back to TRWRP and wipe internal storage and data to be safe, as the -w option to do so when flashing is not working for me.
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Swipe to Wipe
Click back until you are at the main menu
Click on Reboot
Click on Bootloader -> "Do not Install" for TWRP if asked.
Second
Flash the new ROM:
Flash vbmeta.img to remove validation
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
To be safe flash a default boot image (5.1.6 in this case)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Next reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->Thiscan not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot to fastboot
Now flash a the new ROM:
- fastboot flash system_a system-arm64-ab-gapps.img
- fastboot flash system_b system-arm64-ab-gapps.img
Three
reboot:
Code:
fastboot reboot
You will see the "andorid" boot screen (this is different that the Oxygen one) and being the first boot it could take a while. If you see no boot screen or it does not boot (give 10 minutes), then you likely need to repeat these steps again. If you boot into RR then continue.
You may get a Vender image mistake error ignore it it only appewars on boot.
Skip the Setup by clicking all four corners top left->top right->bottom right->bottom left (it my take more than one try), at this point you have no networking, that is what we want.
Suggestion make backup here as you have a working OS! -- Instructions to follow
Four
Move over required files: You now have RR installed and working:
Enable developer mode and then enable Advanced Reboot
Then copy over gapps-nano, Device+ ID.apk, magisk-manager apk and magisk installer zip to the phone
To get the magisk manager you need to extract it from the zip as I cloud not get the normal one to install. Extract the zip: Magisk-v16.3-factory-faizauthar12-20180406.zip copy common\magisk.apk to the phone
Five
Deal with: "Play Services not Certified by Google":
Install Device+ID (APK downloaed above) and Open
Once done open the second line shows the GSF ID for this device
Android Register GSF
Login using a gmail account (I suggest the one you use for the playstore)
Enter the GSF in the field, now we wait about 5 to 10 minutes for it to propigate
Reboot the phone as we want paly services to start fresh
First add a wIFI network.
Critical do not let any apps update until you have registered playstore, so if you see a notification saying downloading, select and click pause. Doing so with the updated 6/17 paystore resulted in a black screen where you would enter your password, no know work around other than reset if this happens.
click on playstore it should now start
Now login to your account and you should be go (it may take more than one attempt no idea why).
Now enable the update if previously paused
Update all Apps from the playstore before continuing, this may take a while give it 10 minutes
Optional: If you want remove Device+ID now (but I leave it as it is an easy way to get information).
You now have a working Playstore, if you have hung downloads then you may need to clear the cache for play services and the playstore I assume the unregistered might be the cause of them getting messed up.
Five
Install magisk:
Ensure you copied magisk zip and also the magisk manager apk to your phone, do not open, but click Done
Install the magisk manager, by locating the file in filemanager and selecting it.Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Install
Select the magisk zip from the filesystem and flash
clear cache
Reboot->System (If asked about installing TWRP swipe to install)
Allow the phone to fully boot
Suggested: Reboot the phone
Suggested: disable checks for updates as 5.7 does not work with this build.
Root is now setup.
Six
Installer th onPlus camera:
Many people want the one plus camera, copy the apk downloaed above to the phone.
Open and install via a file manager
Seven
resize Data (as it will be only 11GB), the partitioon will be larger, depending on your devide se we will use TWRP and resize2fs to grow it.
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Advanced->Terminal
Code:
resize2fs /dev/block/sda17
Reboot System
Eight
Recommended, make a backup of your hard work:
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select backup
Select Everything except EFS and Modem (as I'm unsure exactly which you need)
enter a meaningful name
swipe to backup
click "Reboot System" -> Swipe to reboot
Once back in RR copy the backup off the phone
Eight
Start using your OnePlus 6 with RR 6.0, rooted and with GAPPS
Nine
Upgrading:
Upgrading is simply replacing the system partitions and only these paritions (tested going from 6/13->6/16->6/17 builds)
Boot into fastboot (advanced reboot options)
Now flash the new system files:
- fastboot flash system_a new_system-arm64-ab-gapps.img
- fastboot flash system_b new_system-arm64-ab-gapps.img
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot System
Ten
Restoring a Backup from TWRP
*This is a work in progress I can not work out how to do so safely*
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Restore
Select the backup
Select Everything (other than EFS and Modem!)
Got to the main menu
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot Fastboot
Eleven
Night Light, Ambient Display, requires Root:
My suggestion is not to do this if you care abut battery as I've seen major drain (even with Ambient display disabled, testing this).
Copy the apk downloaded framework-res__auto_generated_rro.apk to /vendor/overlays
Code:
mount -o rw,remount -t ext4 /vendor
cp <location of file> /vendor/overlay
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
Comments:
TWRP does not boot if flashed onto RR (the TWRP logo appears but it will not boot), this is currently only go to protect you from using the OnePlus Recovery and messing up RR. Flashing TWRP does not affect booting into RR.
TWRP DOES handle encryption without an issue, even a wrong first pin is not an issue
TWRP making a backup of Treble ROM, backup everything for now: Data, Boot, System, System Image, Vendor, Vendor Image.
If you have problems with hung downloads from the Playstore: Pending hung PlayStore
Wifi can be flaky (appearently this is a more general issue as even stock had some issues, I fixed them by only using either 2.4 or 5Mhz wireless, if I had both active I had constant disconnects.
Worst case, to recovery, back to Oxygen 5.1.6 if you end up in a boot loop stuck booting to rtecovery, etc:
- flash-all.bat
Reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->This can not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Copy the Oxygen full ROM back to the phone
Code:
adb push OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip /sdcard
In TWRP
Install
Select OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
Go back to the root and select Advanced Wipe
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Click on Reboot->Recovery (select Do not Install)
English
Wipe Cach and Data
Wipe Everything
Reboot
The phone will reboot same as the day it was made
If it does not then please refer to:
Mega Unbrick Guide for A Hard Bricked OnePlus 6
Note: Always boot fully at least once (I suggest twice and the first one is configuring android) before trying any steps above again.
Best of Luck, see a typo let me know
ERIC

thank you for this

[emoji102][emoji102][emoji102][emoji102][emoji102]
Sent from my ONEPLUS A6003 using Tapatalk

Thank you for putting so much hard work on this. Really much appreciated, will give it a try.

Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?

saintxseiya said:
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
Click to expand...
Click to collapse
No.

Great rom, I especially like the fact that I can choose to install without gapps (prefer fdroid). One thing that is missing is ambient display, hopefully it will be fixed sooner or later.

Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Abaddon said:
No.
Click to expand...
Click to collapse
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
same quality here

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
Never said anything about results, only that it could be installed and works, (takes pictures), personally I do little with the camera and am not photographer, but it can be installed (link above) and installed.
Updated the working to remove any confusion.

Maibol said:
same quality here
Click to expand...
Click to collapse
Could you post some comparison pics? Including portrait shots.
Would be awesome.

saintxseiya said:
Could you post some comparison pics? Including portrait shots.
Would be awesome.
Click to expand...
Click to collapse
sorry bro celebrating today with the family too much beer .....

So seeing this not even a month after the release of the op6 makes me happy and hopeful that we get a fully working RR-OS for the OP6 in the near future !

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
because Oneplus doesnt release blobs for camera

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
It will never be the same as OOS stock. Because aside from there is no device tree provided by OnePlus, they will never release the camera blobs due to licensing issues. Once we get a stable and proper gcam port. It'll be better than the stock OOS cam or close

is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore

unix2208 said:
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
Click to expand...
Click to collapse
TWRP not for now as treble is build as an image, but you should be able to flash using twrp just switch to img (though I have not tested that).
The GApps version is posted the 6/18 is working great, see second post.
As for Banking I'm unsure if any Treble based ROM passed the checks, as with or without root, as they appear as unsigned.
As for smartbar, I'll give it a try when I get a chance, as I do not use it personally.
ERIC

So safetynet won't pass?

[ROM][OFFICIAL][fajita][11.0]crDroid Android[v7.30]

NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (with no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery (white & purple on black color scheme, LineageOS logo in the middle).
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option), and color scheme should change from purple to orange.
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6T, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery (and lo, it was most purple), ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0

Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13).
- No changes to device-specific files.
Known issues:
Fajita-specific:
- If you use App Lock and/or Face Unlock, you'll likely run into issues with the FOD circle view starting to flicker randomly into view when it shouldn't be there (like it's not dismissing properly because one part of the security handling is fighting with or doesn't notify the other part that it's done and doesn't need to try to accept a fingerprint any longer). As a knock-on effect, this will also cause "Disable Night Light when FOD is visible" to freak out. I have one person who doesn't use either report that they were getting the random FOD circle anyway, so... if you're having this problem, please make sure you've given MatLog permission to manage files so that it can actually save logs to internal storage and capture a logcat & send it to me. Logs or it didn't happen, etc etc.
Common:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)

MaWalla99 said:
Download: coming soon!
Click to expand...
Click to collapse
will this work with verizon?

Tomkumato said:
will this work with verizon?
Click to expand...
Click to collapse
I don't know since I'm not in the US.

MaWalla99 said:
I don't know since I'm not in the US.
Click to expand...
Click to collapse
Thanks

hi dev thanks for this rom i have successfully installed now, so there is a small info i like to share, that is installing any version of nikgapps apart from core nikgapps will result in bootloop or after even format the data, rom will boot but set up screen says it crashed, so i have installed with core version of nikgapps, rom booted successfully. that's all i have info to share now.

Hi dev ROM is working fantastically after installed all the application I used before, so thanks for it, it has enough customization thanks for it too.

Does NOT work on Verizon.

Hi devs i don't know the reason why this happening, the problem is when i change default launcher to nova launcher system ui automatically crashes, i can't specifically pinpoint the reason, but after launching the Paytm app for first time then paytm also crashed so i don't know what to do now. I have attached logcat from matlog so I think I have captured required info.

Thanks for the ROM. Where is the best place to get A11 gapps?

wangdak said:
Thanks for the ROM. Where is the best place to get A11 gapps?
Click to expand...
Click to collapse
nik gapps

hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks

autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
1 - remove any passwords used to unlock screens - 2 - Backup all your important data, - 3 - Make sure you're on latest TWRP for Fajita and that you have latest OOS firmware, Gapps, TWRP installer and the ROM you want to install (zip files) copied to your "Downloads " directory, then reboot into recovery mode, - 4 - make sure you're on slot A (tap "reboot", tap slot "A" and reboot to recovery again), 5 - tap "Wipe", "advanced wipe" and select " Dalvick Art/Cache", " data" and "system", - 6 - swipe to wipe, 7 - tap "install" and select OOS, then swipe to install, 8 - install TWRP zip file, 9 - reboot to recovery, - 10 - install OOS on the second slot, 11- install TWRP, 12 - reboot to recovery, 13 - install the new ROM, 14 - tap "Wipe", advanced Wipe", "Dalvick Art/Cache" and "Data", 15 - swipe to wipe, 16 - install TWRP and reboot to recovery, 17 - install GAPPS, - wipe " Dalvick Art/Cache and reboot to system. That's it!

autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
Boot in latest TWRP
Flash latest OOS 10
Flash CR Droid Zip
Flash Finalize.zip
Flash latest TWRP
Format data -type Yes to confirm
Reboot to recovery
Flash Gapps & Magisk (Optional)
Coming from a different version of Android, format data is recommended. Backup your data before you do this

Hi LiveDisplay color profile doesn't work ,setting a profile ,once you exit it resets back to normal again

Excellent ROM.
Thanks!

Hi dev i attached a video, in which i try to explain a problem, i can't pinpoint say amazon app only having this kind of problem, but i can say irresponsible of which app suddenly ui will have some kind of problem, it will appear from nowhere after that phone will hang and i need to restart the phone or else battery drains very fast. Kindly look into it. I reinstalled the rom two time freshly, even though it having same kind of problem presist, but i really loved one good feature that is finger print working fantastic even after reboot. OS is not crashing and reboot by itself, app also not crashing but suddenly some part is acting wired. Anyway i will upload the video for proof. I have attached gif file as per xda rules.

I have one last idea in my head instead of using app called migrate to take back up of application installed in my phone and restore to newly installed rom. Better use play store to install all app one by one and see there is any difference, i really love this rom thats why i reinstalling freshly again and again to see any difference possible

I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.

flash713 said:
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
Click to expand...
Click to collapse
Yeah I feel you I'm right where you are I think it's time to ditch Google and get a similar setup. Wonder if there's a thread in the 6t section yet? Google still my friend she'll teach me how to set it up, lol

TrebleGSI crDroid Android 11 ROM for x606f - Updated 5/26/21

None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.

Oddities:
Tablet is unencrypted. You can reencrypt, but TWRP will not be able access data partion.
Must re-register GSF everytime you wipe data.
SafteyCheck fails ctsProfile. - Thread updated with info to fix
More to come as I explore the ROM

Tired it myself and works great. It can be also used with other project treble roms but some features might be broken for example face unlock. I would also add that sometimes the message "This device isn't...." might still appear in Google play, because of that you have to clear cache for this app.

Thanks for writing this up @snickle ! I followed your instructions, DRM Info shows Widevine L1, and disney+ and discovery+ install, but they won't play. "something went wrong", etc.

I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.

Do you have widevine L1? Are you able to play Disney+ or discovery+? I'm having lots of issues that seem to be codec related

I don't use those apps, so I can't comment on how phh-aosp would handle them. I do know that phh-aosp is the most fully developed gsi available, so it might be worth trying.

snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!

ZorgonPeterson said:
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!
Click to expand...
Click to collapse
Did you pass security checks?
i am having trouble passing them with LineageOS 18.1

snickle said:
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
I used the above fingerprint, I even tried the fingerprint from a stock install (which is the same by the way) and it still fails CTS safety check. I rebooted after adding the fingerprint. Everything worked great up to this part.
I used the crdrom that has gapps embedded (I think it was the bgZ version). Could that be an issue?
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.

dpn982 said:
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.
Click to expand...
Click to collapse
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.

First of all thanks for these steps...
Just a quick report that I was able to use them to do a clean install of LineageOS 19 (Android 12) using Andy Yan's GSI Build:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
lineage-19.0-20211106-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz
And using NikGapps for android 12 GAPPS:
NikGapps - Browse /Releases/NikGapps-S/18-Oct-2021 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
NikGapps-core-arm64-12-20211018-signed.zip
For bleeding edge stuff I can say it is running VERY smoothly. I figured I would try the latest thing and then downgrade to Android 11 or even 10, but so far 12 is running so well, I think I will leave it. Pretty big design evolution for Android.

Just a question from someone who's had a break from xda.
This rom is a universalrom for the chip, not a specific tablet? or a jump of point?
sixshooterz said:
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.
Click to expand...
Click to collapse
can you share your steps and sources?
I'd love a lineage for the tp-x606f and if i have to build myself the initially i could not find other thatclickbait for this tab & lineage

This is a generic for the chip. Not my work, I just figured out the steps to get it to work on our tablets. I don't know where source is. I just download updates from sourceforge

scottyrick2 said:
I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.
Click to expand...
Click to collapse
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.

aftnoon2 said:
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.
Click to expand...
Click to collapse
With new version of twrp, it has gotten easier. Magisk has changed also. I am out of town but will update op when I return next week

I'd like to try to flash Phh 11 Rom. Which one is good for my TB-X606F? Those with vdlnklite or without? Floss or no Floss?
This is a new world of flashing to me, sorry for this questions.

snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
is this the complete procedure of establishing a custom ROM ?

I followed the guide by installing the latest version of the CrDroid, everything went fine except the verification of the CTS, I've already tried with Magisk but it doesn't seem to work, any ideas? Thanks in advance
{
"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"
}

[SM-T505,T500,T507] Samsung Galaxy Tab A7 LTE GSI flashing guide [UPDATED] [Android 13 GSIs]

Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A galaxy tab A7 running the latest one ui 4.x build
Pre-requisites (software on PC), you'll need:
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Download the latest firmware from here
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3 Download the twrp.img from below
https://forum.xda-developers.com/t/...axy-tab-a7-10-4-sm-t500.4358595/post-87038713
(Yes, correct, download the .img as we won't be using Odin to flash custom recovery)
Copy this to your SD card as well
4. Download Canary apk of magisk delta from link below
https://huskydg.github.io/magisk-files/
Copy the apk to your microSD which has the previously extracted AP file
5. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
6. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
(also, if it exceeds 3.3 GB, don't worry,follow the steps in important notes on how to expand your system partition to accommodate larger GSIs...)
7. If your gsi doesn't have gapps or you want to flash a system mod then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
https://samsungodin.com/
9. Download SmartPack kernel manager apk and copy it to the sdcard too
https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
(We will be using this to flash twrp in a later step)
10. Download the brightness and watchdog fix module from below
Copy it to SD card
(Optional) 11. If you don't want your install storage encrypted, download the following two zips and move them to SD card,
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
3) After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the reboot completes, install the smart pack kernel manager apk we put in the SD card earlier, then open it, then, navigate to
Tools>Backup>(swipe to the right where it says "boot partition")> it changes to recovery partition> click on the plus symbol> two options show up, select the flash recovery option> select the twrp image from SD card (file manager opens automatically)> click on "select" and then flash it...
10. Then open magisk delta app, and reboot to recovery
11. After rebooting to recovery, flash dynapatch
12. Then reboot to recovery (very important)
(Optional)12.1 Flash multidisabler we downloaded earlier, along with disable dm Verity to disable FBE on integral storage. Also, if you intend to disable encryption, do flash both the zips not one.
13. Then select install>Micro SD Card>install image> select GSI image you downloaded> select System Image > swipe to flash, then factory reset and wipe data from within twrp (thank you @shorty9210 for the factory reset part!)
14. Here, hectic nature of you must be used...
15. Boot to your GSI, and set it up as fast as possible as a watchdog crash is triggered every 30-50 seconds which causes a reboot
16. Install magisk apk and reboot for additional setup
17. After reboot, open magisk and install the brightness and watchdog fix module
18. Reboot the device after installing module
19. At this point you won't get random reboots
20. Now you can enjoy your GSI...
Now, onto what works and what doesn't...
Working:
Boot
Touchscreen
Sound
WiFi
Bluetooth
Mobile data
Camera
Microphone
Doze
OTG
Power buttons
Volume buttons
Charging
Rotation
Gyroscope
Calling(works with VoIP)
Not working:
VoLTE
In call audio (in case of Sims)
Auto brightness
Offline charging
Untested:
Cast
USB tethering
MTP
Tested roms:
1. Trebledroid GSIs (don't use, as magisk doesn't work and gapps can't be properly installed for some reason)
2. Pixel experience ( magisk works and it's stable after running the watchdog command)
3. Google GSI (vanilla and Gapps, not recommended, due to it being extremely barebones and not having fixes for DT2W, and headsets)
4. Project Elixir (needs watchdog module, but mostly stable)
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
@shorty9210 for a correction
@huskydg for magisk delta development
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:
1. If your GSI has phh settings, do the following...
1.1 Enable double tap to wake
Settings>Phh Treble settings>Samsung features >Tick "Enable difficult tap to wake"
1.2 For making headphones work,
Settings>Phh Treble settings>Misc features>Tick "Use alternate way to detect headsets"
Also, Enable developer options>Enable "Disable Bluetooth A2DP hardware offload" and restart when prompted
2. If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
Download latest platform tools from AOSP site, link below
https://developer.android.com/studio/releases/platform-tools
https://forum.xda-developers.com/t/...xy-tab-a7-10-4-sm-t500.4371123/#post-86050459
a) download the product.img from above link
b)Reboot to recovery from magisk app, then, in twrp, click on 'Reboot' button
c) click 'fastboot'
d) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
e) connect your device to a pc with the latest version of platform tools and drivers installed
f) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
g) after doing so, again reboot to recovery, flash dynapatch zip first
h) again reboot to recovery and flash your gsi image
i) this time images up to 3.9GB will be flashable
j) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
3. follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)'
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
4. Previously, we had to use either some magisk modules or SmartPack kernel manager to enable swap so that the device won't crash under load, but, now, 2GB of swap is allocated by default, which is plenty sufficient for daily usage, so, i recommend you not to use any modules or services that enable swap....
5. If zygisk is enabled after module is installed, some users reported that it breaks brightness fix, to remedy that, try flashing permissiver_v5 from below in twrp
Permissiver_v5.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
6. Also, please do not rely on extra dim if brightness fix module won't work, try above step , i did this previously and the edges of my screen got ruined(ghost imaging) due to the heat...
7. Please refrain from using any modules that spoof the device identity as it causes the phh Treble app to not display "Samsung features" at which point you can't use DT2W, so beware...
8. Recommended settings in magisk delta
a)magisk delta>settings>hide magisk app, you will be prompted to allow magisk delta to install apps, allow it and start the hiding> now, the magisk app will be under an alias you chose
b)magisk delta>settings>Zygisk(enable)
c)magisk delta>settings>Bootloop Protection (enable)
d)magisk delta>settings>Magisk Hide
9. Passing safetynet on Gapps GSIs
a)magisk delta>settings>Configure MagiskHide> now, tap on three dots, elect show system apps>then tick the boxes next to the following apps
Google Play Store, Google Play Services, Google Services Framework
b) Install the magisk module "shamiko" version 0.5.2, as later version causes Google services to crash... Download link below(warning, shamiko 0.6 causes all Google services to crash, also, is no longer working with magisk delta, so, use magiskhide present in the delta version)
https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
(Optional) You can also install this module below after installing shamiko for a higher chance to not fair safetynet randomly...
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
c) After installing the module, reboot
d) clear data and cache for Google Play Store, Google Play Services, Google Services Framework
e) at this point you should pass safetynet successfully
10. Just a heads up, be sure to only download GSIs from the list in @phhusson GitHub, i.e, link below,
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And, do not spend money on people that claim to give the "best GSIs" or whatever gibberish they use, only spend money as a donation to a developer, if you really enjoy their work, and would like to support them to keep up thier interest!
I had to mention this to put you on the cautious side of things!
11. Taskbar height is incorrect on some roms, and the magisk module from below link fixes it, credits to @wEER1234 for mentioning this, and to @Coxxs for delaying developing it!
Releases · Coxxs/hide-tablet-taskbar
A Magisk module to hide tablet gesture bar and more [Android 12.1+] - Coxxs/hide-tablet-taskbar
github.com
12. This is for improving the longevity of your device
12.1 To prolong the lifespan of your battery, install the "acc" magisk module, reboof, open a root terminal and run the following commands
acc -s mcc=200
acc -s mcc=3900
The first command limits the charging current to 200 mA and charges the battery at a power of 1.8W which greatly reduces the strain and heat evolved by the battery, and the second command only allows your battery to charge up to 3.9v (52%), as according to battery University, maximum cycles can be achieved by maintaining the voltage battery 3.9 and 3.7
12.2 This is to reduce the Power and heat evolved by the processor
Install smart pack kernel manager, grant root access, go to cpu section, and do the following
Big cpu cores:
Maximum frequency:1056Hz
Minimum frequency:902Hz
Little cpu cores:
Maximum frequency: 1017Hz
Minimum frequency:864Hz
At these frequencies the device stays stable and relatively less hot than at higher clocks...

* This guide is present for legacy reasons, use the guide in the first post *
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[Guide][SM-T500] Galaxy Tab A7 10.4 - Flash LineageOS or any other GSI rom.
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there. Some instructions here, like flashing an empty product.img and resizing system partition, are not...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
GSI type should be "arm64_ab" if you want to you can also use vndklite variant!
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
[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...
forum.xda-developers.com
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[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...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker (follow point 7 in additional notes for 4-speaker audio!)
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Tested roms:
1. Pixel experience
2.ProtonAOSP
3.crDroid
4. Lineage OS
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:-
1) if you are stuck in twrp after selecting reboot to system, then go to Advanced>Terminal and type exit_twrp and then reboot to system
2)The brightness patch has not worked for me on any gsi vndklite or normal, so, if it works for you then you are lucky, if not then I have informed you (brightness fix is in the initial post!)
3) I didn't try OTA updates as we used dynapatch and I'm skeptical about OTAs, so, i recommend you to dirty flash any new releases normally from twrp
4) Disable 'A2DP hardware offload' in Phh Settings>Misc settings and check the box next to disable A2DP offload and then do the same in developer settings too
5) Themed icons causes lags and causes some apps to lock the device up, so, proceed with caution
6) If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
a) Download twrp from the link below (as it has fastboot)
[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]
/* * Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
b) Also download the product.img file from the above link
c) Flash this recovery from existing twrp
d) boot to this new twrp
e) here, click on 'Reboot' button
f) click 'fastboot'
g) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
h) connect your device to a pc with the latest version of platform tools and drivers installed
i) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
j) after doing so, again reboot to recovery, flash dynapatch zip first
k) again reboot to recovery and flash your gsi image
l) this time images up to 3.9GB will be flashable
m) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
Credit goes to @paziusss for this!
7) follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)' https://forum.xda-developers.com/t/...eos-19-1-and-twrp-3-6-1.4421365/post-86917225
8. To flash gapps you need to have a Vndklite variant of GSI installed, then, grab your favourite set of gapps (Android 12L/12) depending on your rom and flash them from twrp!
9. For more fluid performance, download "Smart Pack Kernel Manager" from fdroid, open it grant root access, then go to the hamburger menu, select Vritual memory, and move the slider to 2048 mb, then, enable apply on boot, and reboot your device!

Well, I'm back everyone, and I'll be updating the post #1 with new instructions with regards to running Android 13 GSIs, and post #2 contains the old guide in case someone needs it!

Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️

drsanusi said:
Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️
Click to expand...
Click to collapse
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks!

Hausemaster said:
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks
Click to expand...
Click to collapse
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you

drsanusi said:
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you
Click to expand...
Click to collapse
We initially patched AP file initially, so, magisk will be available even after you flash a gsi but yeah you're correct about the gapps part, I forgot about them as I'm using a Pixel experience gsi, I'll add in the part about vndklite, thanks!
Edit: added it!

Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions

drsanusi said:
Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions
Click to expand...
Click to collapse
Did you boot to system and verify that bootloader was in fact unlocked, as, vaultkeeper will lock bootloader if you don't boot to system after unlocking...
Edit: if you directly flashed without booting, bootloader will relock and you have to wait for 7 days for OEM unlocking to be available again...

Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance

drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
If you want to try another ROM, I suggest you to start from setup 15

drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
Also, the battery drop may be because of GSI roms not setting cpu frequency according to usage, it just locks it at full frequency causing heat and heavy battery drain, try lowering clockspeeds using a kernel manager
edit: I use smart pack kernel manager

drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
I found the actual brightness fix from the thread which we downloaded kernel from, I added the commands in the OP here...

If you're flashing big GSIs and flash fails due to insufficient system space, I've added a way to do so in the important notes...

Hausemaster said:
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
https://github.com/topjohnwu/Magisk
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[Guide][SM-T500] Galaxy Tab A7 10.4 - Flash LineageOS or any other GSI rom.
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there. Some instructions here, like flashing an empty product.img and resizing system partition, are not...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[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...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Haptic Feedback (vibration)
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
Click to expand...
Click to collapse
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.

wEER1234 said:
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.
Click to expand...
Click to collapse
I didn't know that this didn't have one, thanks for the information, will do the necessary changes now!

This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com

duyfken said:
This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Click to expand...
Click to collapse
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...

Hausemaster said:
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...
Click to expand...
Click to collapse
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
{
"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"
}

duyfken said:
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
Click to expand...
Click to collapse
Oh my! Thanks for the sharp observation, I corrected it now in the OP
Edit: I also added the type of GSI that should be used for this device!
Edit 2: I also mentioned you in the credits, as you're the one who caught the errors! And once again, thank you very much for the corrections you saved the day!