[GUIDE] Factory Reset Your Elite ROM w/ microG & retaining clean functionality - ZTE Axon Pro

Hello, the purpose of this guide is to show how to retain functionality after doing a factory reset on every ROM.
The problem is that the preinstalled gapps may not be working (login not possible), even after enabling and setting autostart in MiAssistant. Therefore some guides (e.g. this newest one) recommend flashing a working ROM, setting up GApps and afterwards flashing a new ROM without any wipe.
But those who simply want to factory reset can be helped with this guide. This also may make the intermediate step of GApps installaion unnecessary.
microG replaces Google Play Services, Framework and LocationProvider, ALL other GApps are working as expected afterwards.
In TWRP backup your current installation (important if any bootloop occurs)
Factory Reset, Reboot, do basic setup (device name, etc) and select language in MoreLocale if needed
Download, Flash and Wipe Cache + Dalvik Afterwards:
Magisk ONLY if you have a unpatched boot.img meaning no previous supersu installation (to obtain root while passing safety net)
-if the installation of Magisk failed please perform another Factory Reset before continuing (otherwise NanoDroid won't install correctly)-
OTHERWISE SuperSU and Xposed Framework (link for Android 6, SDK23)
NanoDroid fdroid (fdroid plus modified play store)
NanoDroid microG (migroG plus removes unneccessary Google stuff)
NanoDroid patcher to allow signature spoofing not working on odexed roms, we solve that with (Magisk-)Xposed-FakeGapps
Reboot, launch fdroid, let it update its repository and install FakeGapps, XposedInstaller (+ if installed, in Magisk XposedFramework)
In Xposed download XposedGmsCoreUnifiedNlp and enable all installed Modules
In Mi Assistant enable all apps to auto start
Restart, then login into Google to see if that works, otherwise check if Xposed modules are enabled and working, restart and try again, if still not working try disabling and reenabling the concerned app (e.g. Play Store)
Furthermore a selftest can be done in microG settings and you can check if Nlp is working in a Maps App of your choice
Unnecessary Apps CAN be frozen (recommended with AirFrozen) or uninstalled (only if 100% sure and backuped)
Q&A:
Contacts Sync is not working / crashing: Try reinstalling the Google Sync Adapters with the flashable zip from here, set the additional permissions in App Settings

Related

What is the proper order of flashing ROM, Kernel, Root, GApps, and Anti-Throttle?

So I'm working on wiping my phone and starting from scratch. I'm going to be using:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
I'm just not sure which order to install everything. I assume the OS gets installed first, followed by Gapps. Then do I install the Kernel, MOD, and SU? Any reboots inbetween, or install them all at the same time while in recovery?
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
dahawthorne said:
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
Click to expand...
Click to collapse
Pretty much nailed it right there! That's what I do as well!
blueblade123 said:
So I'm working on wiping my phone and starting from scratch. I'm going to be using:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
I'm just not sure which order to install everything. I assume the OS gets installed first, followed by Gapps. Then do I install the Kernel, MOD, and SU? Any reboots inbetween, or install them all at the same time while in recovery?
Click to expand...
Click to collapse
For Clean Flash:
1.) Go to "Wipe" and then Swipe to Factory Reset
2.) After thats done go to "Advanced Wipe"
3.) Tick Dalvik/Art Cache, System, Data and Cache ONLY!! and then "Swipe to Wipe"
4.) Flash Rom and Gapps
5.) Kernel
6.) Then anything else you might install such as Magisk / Super SU, MOD )
All at the same time in Recovery!
Sent from my shamu using XDA Labs
dahawthorne said:
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
Click to expand...
Click to collapse
Do you usually wipe Dalvik/cache before and after flash or just after
minilandl said:
Do you usually wipe Dalvik/cache before and after flash or just after
Click to expand...
Click to collapse
A more technically-experienced member may be able to give you a definitive answer on which is best, if it makes any difference at all, but I normally do it only after flashing the ROM and before installing Magisk. For a total advanced wipe, of course, obviously I do all four partitions beforehand.
blueblade123 said:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
Click to expand...
Click to collapse
For some starting advice/my recommendations:
Instead of Bean GApps, use OpenGApps; they provide newer GApps that aren't months outdated and work fine
Use Magisk for SU/root unless you have a specific reason for AddonSU
Make sure you grab the latest FrancoKernel (I think r73?)
As for flash order:
Wpe everything
Reboot to Recovery
ROM
GApps
Reboot to Recovery
Kernel
Magisk
Reboot to System
As to what I usually do for a really clean install (likely overkill):
Reboot to Bootloader
Wipe everything (fastboot erase all)
Do flash-base.sh from latest factory image (this reflashes modem partitions; this is required after erase all)
Boot to Recovery
Wipe everything from TWRP
Reboot to Recovery
Wipe everything again from TWRP (old habit from when the first wipe didn't actually get rid of everything on older devices)
fstrim Data, Cache, System, and Firmware partitions
Reboot to Recovery
ROM
GApps (I don't use GApps, but if I did, this is when they are to be flashed)
Reboot to Recovery
Wipe everything except System from TWRP
Format Data and Cache to F2FS
fstrim Data and Cache partitions
Reboot to Recovery
Kernel
Magisk
Reboot to System
Do set-up and copy files over to device
Reboot to Recovery
Wipe Dalvik Cache (I guess the button in TWRP would work; I do rm -Rf /data/dalvik-cache)
Use filesystem tools to check and repair partitions (e2fsck for ext4 being System and Firmware partitions, and fsck.f2fs for F2FS being Data and Cache partitions)
fstrim Data, Cache, System, and Firmware partitions
Reboot to System
No, Beans GApps is a better choice.
It only gives the apps that are truly essential.
It doesn't check to see if you're clean flashing a ROM before placing Google Camera in /system.
It's smaller. With OpenGApps you have to download the Stock package at nearly 800MB and exclude a bunch of apps to approximate the full Beans GApps package.
The apps are updated through the Play Store, thus the fact Beans doesn't update his package daily like OpenGApps isn't relevant.
Strephon Alkhalikoi said:
No, Beans GApps is a better choice.
It only gives the apps that are truly essential.
It doesn't check to see if you're clean flashing a ROM before placing Google Camera in /system.
It's smaller. With OpenGApps you have to download the Stock package at nearly 800MB and exclude a bunch of apps to approximate the full Beans GApps package.
The apps are updated through the Play Store, thus the fact Beans doesn't update his package daily like OpenGApps isn't relevant.
Click to expand...
Click to collapse
1. OpenGApps offers multiple packages. If you want the bare-minimum, I don't believe you can limit the apps any further than Pico. If you want Google Search, then Nano is the next step up. Then you have Micro, Mini, and Full, along with Stock and Super. Paired with a gapps-config.txt file, you can have whatever apps you want installed if none of those packages suit your needs, or just grab the smallest package and grab additional stuff from Play Store.
2. I'm not too familiar with a situation where that would be good, but you can use a gapps-config.txt file to force Google Camera and ignore a non-clean install
3. Pico is a little over 100MB, and there's several other options for pre-included packages up until the stock package. If downloading the larger Open GApps package isn't feasible, then a smaller package with the apps from Play Store would work right? Both Bean Gapps and Open GApps are GApps; you're downloading the same amount of data for apps either way regardless, the difference being whether they're included in the package, or you get them from Play Store.
4. I suppose that's a good point, but if I'm doing a clean install of a ROM and GApps, I wouldn't want to have to update all the GApps packages right after a clean flash.
My experience with Open GApps has been great over the years I've used them. I've tried Bean GApps a few times in the past and it also worked fine up until the June full package that was released broken (which gives the impression Bean Gapps are blind-released; although I guess OpenGApps does this as well).
@espionage724: Beans' full GApps package includes the Google Camera. The smallest OpenGApps package that includes the Google Camera is the stock package. In order to emulate what Beans' provides, you have to use the stock package and you have to create a .gapps-config file. When installed, the OpenGApps script looks at the .gapps-config file and by default excludes any items that are listed in that file, such as the items below.
ExchangeGoogle
GoogleNow
TagGoogle
CloudPrint
Docs
Drive
Fitness
Keep
NewsWidget
Books
Movies
NewsStand
Sheets
Slides
Duo
The preceding list is the apps that must be excluded from the install in order to approximate the Beans' full GApps package. Now how do I know this? When Beans was having issues with his GApps package in June I used OpenGApps stock to update the Google apps, and the list above was the list of items that I ended up removing. Once the issues with his GApps package were resolved, I went back to using his.
The above is a rebuttal to point 1 you made.
2. The OpenGApps installer script will not install the Google Camera even if you specifically include it in the .gapps-config. This is done to avoid force closes and other strangeness. According to the OpenGApps wiki...
Experience has shown us that users who install this application FOR THE FIRST TIME during a 'Clean install' GApps installation almost never have issues or problems with these apps. However, there have been several reports of users experiencing FCs or other strange behavior when they have tried to install these apps later (with GApps), after their device has been set up.
To ensure the best possible user experience, Open GApps will only allow this application to be installed FOR THE FIRST TIME as part of a 'Clean' install (data wiped) installation. Updates to an existing System (Open GApps) installation will also install fine, plus you can still freely update these apps from the Play Store and have the Open GApps installer update them later with the next Open GApps update.
Click to expand...
Click to collapse
-- https://github.com/opengapps/opengapps/wiki/FAQ
3. This has nothing to do with the fact that the minimum size OpenGApps package needed to install all the Google apps found in Beans' full GApps package is the stock package. That said, if we ever do run low on space in /system, the smaller packages (e.g. Micro, the smallest package I recommend using) are certainly an option since most Google apps can be downloaded from the Play Store. The Google Camera however may not be available in the Play Store, depending on the ROM, meaning it would have to be sideloaded.
4. While I'm in agreement about not having to update the packages immediately, at the same time it simply does not matter. The Google apps update frequently enough that trying to keep up with it by repeatedly installing GApps packages is a waste of energy. So I only update when the ROM itself is updated. If that means I have older versions of Google apps in /system, then that's fine by me. The apps will get updated.
Prior to the Nexus 6 I exclusively used OpenGApps and never had an issue. With the Nexus 6 I used the recommended GApps for Pure Nexus, and except for June have had no issues. Obviously, which one you want to use is up to you, but I'll let you know right now that it took about two weeks for OpenGApps to get their Android 8 packages to finish installing without requiring a hard reboot. The impression I get is that what happened with both OpenGApps and Beans full GApps was a one-off aberration.

Huawei P8 GRA [ROM][6.0][EMUI 4.0.3][b399]MagicArrow-v3

{
"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*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-gra-b399-rom-6-0-emui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
- K-Settings by KangV for b399
- Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
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!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- Magisk v16 Update available - do it with this steps: https://forum.xda-developers.com/showpost.php?p=75656403&postcount=22
Do not update yet to Magisk v16.1 - it would cause big problems - I will provide a patch zip for the update
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
FIX for the Network-Information-Query (for both Editions): https://forum.xda-developers.com/showpost.php?p=76416139&postcount=167
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
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 disable Lunar, 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"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need 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.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM​​​
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here: https://www.paypal.me/Tecalote
Many thanks and credits:
@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
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
​
reserved for updates
reserved for additional Guides
Tecalote said:
Huawei P8 Custom ROM
*MagicArrow*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread:https://www.android-hilfe.de/forum/...ui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
-K-Settings by KangV for b399
-Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
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!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
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 disable Lunar, 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"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need 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.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV:https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here:https://www.paypal.me/Tecalote
Many thanks and credits:
@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
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
Click to expand...
Click to collapse
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again
hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem withthe media-Provider-app
buuuut i cant fix it..
any ideas???
regards
Nice job work fine thanks
Rasenverbraucheramt said:
hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem with the media-Provider-app
buuuut i cant fix it..
any ideas???
regards
Click to expand...
Click to collapse
I like to know which Gallery and which music App did you flash and which files ? And which path did you use (which App into which directory?) Did you delete the original Huawei Musicplayer/Mediacenter and the original Huawei Gallery?
lespaul79 said:
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again
Click to expand...
Click to collapse
Your welcome my friend
Tecalote said:
Your welcome my friend
Click to expand...
Click to collapse
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!
hello
my device p8 last update
GRA-UL10_C185B391 ?
aswertya said:
hello
my device p8 last update
GRA-UL10_C185B391 ?
Click to expand...
Click to collapse
The last Firmware is from December 2016 - b382 for c185. There's no newer Update available for c185
You must not update your Firmware, just do steps from OP
chros69 said:
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!
Click to expand...
Click to collapse
If you really want to do it complete clean, you should flash for L09c432 Full Firmware b399 with Factoryreset after.
I will write in #2 how to do with links and so on...
All perfect my friend
I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?
Cientista2018 said:
I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?
Click to expand...
Click to collapse
Yes just do Install Guide from Post #1 of this Thread (OP)
I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?
Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.
Morun said:
I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?
Click to expand...
Click to collapse
No additional steps, just as you said
beardedwonder said:
Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.
Click to expand...
Click to collapse
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.
Tecalote said:
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.
Click to expand...
Click to collapse
Which firmware are you on? I'm willing to do a full backup and install of that firmware then your ROM as I've had some dropped calls.

My google play account has been block from ever purchasng in apps and games by google

Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
I
blitzball said:
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
Click to expand...
Click to collapse
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
zgfg said:
I
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
Click to expand...
Click to collapse
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
blitzball said:
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
Click to expand...
Click to collapse
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
zgfg said:
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
Click to expand...
Click to collapse
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
blitzball said:
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
Click to expand...
Click to collapse
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
zgfg said:
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
Click to expand...
Click to collapse
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
blitzball said:
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
Click to expand...
Click to collapse
TWRP backup that can be restored through TWRP (Restore option in TWRP)
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Thanks man. I'll go ahead and install magisk
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Dude so I installed it with no problems but I still can't pass safety net
blitzball said:
Dude so I installed it with no problems but I still can't pass safety net
Click to expand...
Click to collapse
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
zgfg said:
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
Click to expand...
Click to collapse
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
blitzball said:
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
Click to expand...
Click to collapse
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
zgfg said:
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
Click to expand...
Click to collapse
I have Netflix now. It's weird though cause only after maybe ten or twenty minutes did it show up in my store. Still can't buy anything though google still detects my phone for some reason. Thanks anyways.

The root permission request is no longer displayed

I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
@rovo89
@topjohnwu
https://www.didgeridoohan.com/magisk/MagiskHelp
I have added much more information.
Reinstall firmware???
LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe

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"
}

Categories

Resources