Related
This guide shows how to install TWRP and Magisk even starting from firmwares after B19 A2017U firmware (starting B25, ZTE removed Fastboot). As always read the ENTIRE directions before beginning. If you'd like to try a faster method, see instead King1990's Alternate Method posted below steps A, B and C.
Step A involves downgrading your OS to B19. If you are on B25 or higher currently, you must not skip this step. If you are on B19, skip this step.
Step B is upgrading to B32 on an unlocked system, retaining Fastboot and the Recovery by using DrakenFX's method.
Step C is installing Magisk.
STEP A: FLASH TO B19 WITH TWRP USING EDL MODE
NOTE: This assumes you are unlocked. If you need to unlock starting from a firmware later than B19, please follow the EDL Unlock instructions at the EDL Thread, or use the Axon7Toolkit unlock, which is essentially the same but may be easier for some.
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, select the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolls back your device to B19 stock)
9. Repeat Steps A.3-A.8 for "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
10. After EDL flashing B19-NOUGAT_TWRP (Nougat 7.1.1), hold Power+VolUp when boot into TWRP. At the first warning screen, slide to allow modifications, but DO NOT BOOT INTO THE ROM until you complete the next step re: no-verity.
11. Tap Mount, and then Mount the phone via MTP in TWRP. Transfer over the latest (5.1 at time of writing) no-verity-opt-encrypt-5.1.zip file from this link (original thread) to your phone via MTP. Flash this file using the "Install" command in the TWRP main menu.
Troubleshooting Notes:
If bootup freezes at the very first screen after the ZTE logo ("Start - Continue to Boot..."), you probably have either (1) not properly flashed the B19 FULL before the TWRP folder, or (2) enabled changes in TWRP without flashing the zip in Step 11. If so, start over from the beginning, reinstall B19 FULL and TWRP via EDL. If you cannot boot into the system, this is likely your only option.
If you are stuck on a bootup screen that says "To start android, enter your password": You have probably mistakenly started a normal boot after flashing the B19 FULL but before flashing TWRP. Do not attempt to enter a password, simply get back into EDL mode to flash the TWRP folder for Step A.9. Do this by either holding VOL+/VOL-/POWER, or by using the ADB command if available, "adb reboot edl" . If you are in-between steps and having trouble finding a part of the boot sequence that ADB receives commands, try opening an ADB console on Windows and entering "adb devices -l" to see if your device is visible to ADB at either the bootloader itself (VOL+/POWER), or the main root TWRP screen. (Worst case, if TWRP is not installed, but if you can access Fastboot, put the TWRP .img file in the same directory on your PC as your ADB/Fastboot .exes, rename to "recover.img" and use the command "fastboot boot recovery.img" to temporarily boot into TWRP.)
If MiFlash cannot flash to your device even when it can see your device: If you can access ADB, try the command "adb reboot edl" . Some Axon 7 phones apparently do not correctly enter EDL mode when holding VOL+/VOL-/POWER, and although visible to MiFlash cannot be flashed unless a software command puts the phone into EDL. Alternatively, Axon 7 Toolkit can do this - select Option 10 when ADB is active.
If you follow this guide and receive a ctsProfile mismatch error when running a SafetyNet check in Magisk, you likely had some remnant of a prior SU installation that is triggering the error. Please follow the steps in this troubleshooting guide: https://android.gadgethacks.com/how-to/magisk-101-fix-safetynet-cts-profile-mismatch-errors-0178047/
STEP B: UPDATE TO B32
Important: You cannot use the update process in Mifavor to update, or you will lose fastboot. Instead, any updates must be flashed via TWRP.
1. Go to DrakenFX's thread and follow the instructions. Relevant portion added below for simplicity.
2. Download and move to your phone (Internal or SD):
- A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
3. Boot into TWRP, and Wipe Cache, Dalvik, and Data
4. Flash ("Install" in TWRP) A2017UV1.1.0B32_bootstack_by_DrakenFX.zip, then install A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip.
5. Flash the no-verity-opt-encrypt-5.1.zip file again from this link (you should already have this on your phone from Step 1 above)
STEP C: INSTALL MAGISK ZIP VIA TWRP
NOTE: If you have performed this with the 13.6 Beta per my earlier guide, simply download Magisk 14.0 within the Manager app and then flash 14.0 in TWRP to update. For new installations, flashing directly the 14.0 ZIP file should be fine. Any Magisk before 13.6 Beta will likely no longer work.
1. This guide assumes you have a clean image with NO SU. (If you have used SuperSU or another SU, you will need to either reset/reflash a clean image, or uninstall it sufficiently. If you have a prior Magisk, there is a Magisk Uninstall tool (here You can proceed without flashing a clean image using that tool, included in Step 3b below.)
2. Download the latest Beta Magisk ZIP file ("Magisk-v14.0.zip") in the main Magisk thread. I have also attached it to this thread for convenience. NOTE that this ZIP file also automatically installs Magisk Manager, so you do not need to download or install it separately in Android.
3. Go to TWRP, and install the Magisk-v14.0.zip. Clear Dalvik/Cache after install.
4. Reboot into stock, and open Magisk Manager which should be installed now automatically. Magisk Hide should be auto enabled, MagiskSU 14.0 should be installed, and all checks should pass including SafetyNet. Catch all the Poke-mans and Pay all the Androids.
Please make a TWRP backup before attempting, and be ready to roll back if needed.
Alternate Method (Thanks to King1990)
This method may be quicker, so you may prefer to try this method first, or as an alternate if the above method is too complex or doesn't work for you:
*these steps only if you are already unlocked your bootloader first UNLOCK *
*Note: it does not matter if your on stock B25 or B32 or any custom roms just follow the steps below*
*Backup first*
1- Download & install Axon7toolkit 1.2.1,install drivers & ADB from the tool (option 1).
2- using the tool, choose option 11 & follow the instructions to flash "A2017U_B19-NOUGAT_FULL_EDL" using Miflash (Axon7toolkit will start Miflash)
3- if the flashing was successful reboot your phone
4- now update using OTA to B25 then again update to B32 through OTA .
5- now you have completely stock B32 , you will also lose fastboot command
6- Reboot to EDL
7- Start Miflash directly it should be here "C:\Program Files\Xiaomi\MiPhone" & Click on refresh , a COM port should appear
8- in the target white bar, paste this destination "C:\Axon7Development\Axon7Toolkit\miflash\unlock\FASTBOOT_UNLOCK_EDL_N" & click flash, if succeed reboot & you should now have fastboot commands
9- again use Axon7toolkit & choose option 9 to flash TWRP , follow the instruction and you should have TWRP.
10- start the system then reboot to recovery and flash magisk 14.0 check for safety net if fails just reboot your phone & it will pass.
11- done.
Previous threads and guides
(Previous Thread)
-----------
(Previous Magisk and OTA process - DO NOT USE)
STEP 2: INSTALLING MAGISK 13.2 WITH ROOT AND SAFETYNET PASS
1. This guide assumes you have a clean image with NO SU. (If you have SuperSU or another SU, you will need to either reset/reflash a clean image, or uninstall it sufficiently. If you have a prior Magisk, there is a Magisk Uninstall tool. You can proceed without flashing a clean image using that tool, included in Step 3b below.)
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 5.0.6 and Magisk 13.2 (here, and attached for convenience), and copy them to your device. (Note that you can also just install Magisk Manager 5.0.6 and download the latest Magisk flashable ZIP from there.)
(3b. If you already have a prior Magisk & Manager installed, also download Magisk Uninstall (here, attached for convenience) and copy it to your device. Boot into TWRP, and "Install" (flash) Magisk Uninstall. Boot into system, and uninstall Magisk Manager. Clear Dalvik/Cache after each step.)
4. Install Magisk Manager v5.0.6 via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 13.2.
6. Reboot into stock, and open Magisk Manager. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Reboot into TWRP, and flash the Magisk 13.2 SafetyNet Fix, attached. Reboot.
9. Now if you check SafetyNet, it should pass.
STEP 3: GET OTAS (EXPERIMENTAL)
There are still issues with B19 to B25 upgrades with Magisk using OTA packages, (such as those by DrakenFX).
Prior to the SafetyNet update (Magisk 13.0 beta), users reported partial success - if they installed Magisk successfully on B19, and gave root permission as needed, they could upgrade to B25 and retain old root permissions but NOT add new permissions for apps. I have not seen it tested whether this is still true after the SafetyNet update (Magisk 13.2).
----------
(Previous Original Guide - DO NOT USE)
If you are only here for Magisk: Despite all the horror trying to get it to work with 12.0 and earlier versions, it should flash fairly easily using versions later than the 20170520 beta and 13.0 beta Magisk Manager.. But since the 20170520 files are the only version I've tested, I can only vouch for those files and they are specifically mentioned in the guide.
NOTE: This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP). ALTERNATIVELY, you can use the Toolkit to install TWRP, or via ADB, or any other method.
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
Also, if any of these steps fail, install the Toolkit and use the same operations in the Toolkit. I used v. 1.2.0 for both the EDL flashing and to install TWRP as well, since on a later A2017U, the button restart method appeared to put me in a halfway-EDL mode which was visible from MiFlash, but did not allow flashing. In that case, a software EDL reset ("adb reboot edl" or "reboot edl" in the TWRP console) was the only way to get MiFlash to allow it to flash. The Toolkit does this nicely.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. Again, my guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET UPDATES / GO TO B25: I have not tested yet to ensure Magisk doesn't break, but I believe you should be able to download OTA packages, such as those by DrakenFX and flash them. However, users are reporting some bugs upgrading beyond B19, so OTAs are a work in progress. Please make a TWRP backup before attempting this and be ready to roll back if needed.
6bolt2g reports he had success moving from B19 (rooted) to B25, with the following steps: (a) flash "the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP"; and (b) follow STEP 2 above. However, 6bolt2g and StickMonster report that after upgrading to B25, you may experience problems with adding apps not previously whitelisted. Again, this is not verified by me but reporting it in the first thread for convenience.
For now, applying OTAs beyond B19 should be considered experimental - please be aware of the risk and have a backup before trying, and share your results here.
Changelog
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Edit 5/23/2017: Added 6bolt2g report re: moving from B19 to B25.
Edit 5/24/2017: Added additional updates re: OTAs.
Edit 7/17/2017: Revised based on new ~7/12 Google SafetyNet changes, new Magisk from 5/15, and SafetyNet fix
Edit 9/3/2017: Added additional alternate solutions and troubleshooting advice.
Edit 9/4/2017: Revised process for B32, Magisk 13.6 Beta.
Edit 9/10/2017: Revised process for Magisk 14.0.
Edit 9/17/2017: Added King1990's alternate method.
Just wanted to thank you for the guide. Now I'll be able to get root on B25.
EDIT: I just wanted to know if flashing the B19_full will wipe userdata? I have a feeling it does, but I just want to double check.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
Just wanted to thank you for the guide. Now I'll be able to get root on B25.
EDIT: I just wanted to know if flashing the B19_full will wipe userdata? I have a feeling it does, but I just want to double check.
Click to expand...
Click to collapse
When I did it, it did NOT wipe userdata. Surprising to me that all my apps and things were still on the screen, but the version did indeed roll back. YMMV.
I've played with Magisk 13 too. I could get root, but not safety net. That's on b25. I can't remember if I tried it on b19.
To get safety net and Magisk 10 working on b25 I have to get it working on b29 and then upgrade to b25. So what you suggest for 13 sounds promising.
I'll have to play some more if you got it working on b19.
Curious, what makes you think OTAs will work? B25 removes fastboot for me and installed stock recovery. I had magisk working on B25 when not updating the bootsect and keeping that at B19.
Second question, with only B19 installed, after rolling back from B25 do you, or anyone for that matter have a problem where the signal constantly cycles on/off?
StickMonster said:
I've played with Magisk 13 too. I could get root, but not safety net. That's on b25. I can't remember if I tried it on b19.
To get safety net and Magisk 10 working on b25 I have to get it working on b29 and then upgrade to b25. So what you suggest for 13 sounds promising.
I'll have to play some more if you got it working on b19.
Click to expand...
Click to collapse
Magisk 10.3-beta2 worked after simply flashing the zip and the superuser and manager apks for me on b19
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
6bolt2g said:
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
Click to expand...
Click to collapse
Nice. Looking forward to hearing those results.
crashnova said:
Nice. Looking forward to hearing those results.
Click to expand...
Click to collapse
So far the masking function ie. Android Pay worked today when I went to use it. I went to use a few root apps, ES File Explorer and just an emoji switcher this afternoon and it was force closing the Magisk app. I tried to restart the phone to see if that was some of the issue, no difference. I also tried to uninstall and install the app from the Play Store, but it was an older version (v12). So I removed it and put the v13 back on and the force closes have stopped for now. I will have to continue using it to see how it goes. Anyone have any suggestions for root apps they would like me to try? With all the goodies baked into these stock roms there is less and less need for root access, at least for me.
6bolt2g said:
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
Click to expand...
Click to collapse
Thanks! I will update the original post with your results.
Edit: Can you confirm exactly which ZIP files you flashed, and where you specified "no-verity"?
Dodgexander said:
Curious, what makes you think OTAs will work? B25 removes fastboot for me and installed stock recovery. I had magisk working on B25 when not updating the bootsect and keeping that at B19.
Click to expand...
Click to collapse
I figure that as long as you can keep TWRP, the fact that Magisk was updated and confirmed to work with one version of Nougat suggested it should work with minor updates. (Nougat seems to be what broke Magisk initially.) I understand DrakenFX allows flashing in a way that preserves TWRP, so infer that it will likely work. I'm trying not to overstate what I know, but it appears to work for at least 6bolt2g. However, upgrading to B25 should be considered experimental at this point.
Dodgexander said:
Second question, with only B19 installed, after rolling back from B25 do you, or anyone for that matter have a problem where the signal constantly cycles on/off?
Click to expand...
Click to collapse
I haven't had that issue rolling back from B25. Maybe clear caches? Try reflashing with MiFlash?
ScaryBugThing said:
Thanks! I will update the original post with your results.
Edit: Can you confirm exactly which ZIP files you flashed, and where you specified "no-verity"?
Click to expand...
Click to collapse
I already was unlocked and had TWRP installed and I was on Stock B19 with root via Super SU, but the root part shouldn't matter.
I flashed the stock Bootstack and B25 Rom from this post: B25 TWRP Flashable
His directions mentioned using the vm-verity zip file if you want to keep TWRP and not flash super SU. He did not link the verity zip that I saw, so I searched XDA for them.
The link to the TWRP post with the download link: TWRP dm-verity Half way down the first post.
And the direct link to the download file list : no-verity download link I just picked the newest version.
Hope that helps.
*Edit*
To add to my issue earlier about the Magisk Manager crashing when approving root access. After re-installing it seems to work fine. I believe its after a reboot, it starts to have the crashing problem. It does seem to maintain previously approved root accesses though. For example, ES File manager is still able to explore system folders during the crash, because I approved it earlier when it was still working. I'm no programmer so I do not have a clue what is going on. I imagine, something is not persisting through the reboot. And to clarify, it is crashing when new programs are asking for root access and the pop-up shows.
Same for me using the 170523 build. Everything works at first, including root for apps already whitelisted from before the b25 upgrade, but once you try to add a new app to your root list you get FCs from then on any time su tries to run, including trying to start superuser from within Magisk manager. If you delete Magisk data, from twrp or Android app settings, the FCs stop but then you have no apps with root granted.
It looks like there is a version from nfound we should try.
Yep tried miflash running back to b19 and it's the same. I can't run b19 stock anymore, but it's off topic here so I'll shut up
Dodgexander said:
Yep tried miflash running back to b19 and it's the same. I can't run b19 stock anymore, but it's off topic here so I'll shut up
Click to expand...
Click to collapse
If you flash back to b19 try erasing Magisk data. I'm pretty sure that worked for me.
StickMonster said:
If you flash back to b19 try erasing Magisk data. I'm pretty sure that worked for me.
Click to expand...
Click to collapse
Magic is no problem on B19, signal is not. Flashing on and off like the phone is detecting a modem one sec and the next not.
Thanks for the updates about moving to B25. Updated first post - if you test anymore, please share.
ScaryBugThing said:
Hi all - this thread originated in the Q&A forum (old thread), but since I mapped out steps in a guide, I am posting it here since it is the more proper place for it.
This is a guide showing how to get TWRP installed, Magisk running, and I plan to update once I confirm OTAs can be flashed.
If you are only here for Magisk: Despite all the horror trying to get it to work with 12.0 and earlier versions, I believe you should be able to flash it fairly easily using versions later than the 20170520 beta and 13.0 beta Magisk Manager, see links below. But since the 20170520 files are the only version I've tested, I can only vouch for those files and they are specifically mentioned in the guide.
NOTE: This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. Again, my guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET OTAS: I have not tested yet to ensure Magisk doesn't break, but I believe you should be able to download OTA packages, such as those by DrakenFX and flash them. However, users are reporting some bugs upgrading beyond B19, so OTAs are a work in progress. Please make a TWRP backup before attempting this and be ready to roll back if needed.
6bolt2g reports he had success moving from B19 (rooted) to B25, with the following steps: (a) flash "the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP"; and (b) follow STEP 2 above. However, 6bolt2g and StickMonster report that after upgrading to B25, you may experience problems with adding apps not previously whitelisted. Again, this is not verified by me but reporting it in the first thread for convenience.
For now, applying OTAs beyond B19 should be considered experimental - please be aware of the risk and have a backup before trying, and share your results here.
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Edit 5/23/2017: Added 6bolt2g report re: moving from B19 to B25.
Edit 5/24/2017: Added additional updates re: OTAs.
Click to expand...
Click to collapse
I kept having error Object ref not set to an instance of an object. I already have TWRP, i wonder if i need stock recovery for this to work?
Question: On B25, once you have your root apps whitelisted and root access granted, does the Magisk Manager work alright? Other than FC on new apps, does it still do its thing and the phone work normal? My Axon 7 should be arriving today and I want to be on B25 for the wifi-calling fixes. I can probably live with white listing the apps on B19 and then updating to B25 once everything is ironed out.
genbu said:
I kept having error Object ref not set to an instance of an object. I already have TWRP, i wonder if i need stock recovery for this to work?
Click to expand...
Click to collapse
Can you give more details... whats your starting point? and what step are you getting this error?
---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------
HallOfPromise said:
Question: On B25, once you have your root apps whitelisted and root access granted, does the Magisk Manager work alright? Other than FC on new apps, does it still do its thing and the phone work normal? My Axon 7 should be arriving today and I want to be on B25 for the wifi-calling fixes. I can probably live with white listing the apps on B19 and then updating to B25 once everything is ironed out.
Click to expand...
Click to collapse
I cant answer for stock AXON 7 OS... but im running LineageOs and everyththing is working very well... no Force closes with apps or anything like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOUR WARRANTY WILL BE VOID
I AM NOT responsible for anything that may happen to your phone while attempting to follow this guide.
You are doing so at your own risk, and you take full responsibility for your decisions and actions.
You are not to blame me or XDA, or any of it's respected developers.
Anyways, now that that is out of the way. Those of us who have been in the Axon 7 forums know that information is quite scattered about. So it can be difficult for any newcomers to find everything they need before making any leaps or dives with their device. This guide’s purpose is to centralize the quickest and easiest steps to follow in order to get Treblized and to get on a stable Pie GSI build that can be used as a home base before experimenting further with other ROMs and/or GSIs.
Even if you are not satisfied with the Havoc Pie GSI, your device will still be in an optimal state to try the latest Oreo 8.1 ROMs, such as LOS 15.1 or DotOS 2.5, or to try any of the other Pie GSIs in the Treble forums.
Things you will sacrifice:
No VOLTE
No Encryption
No Dolby
No Daydream
No AK4490 DAC (will default to AK4491)
Camera Flash out of sync (Use OpenCamera for flash shots)
Not able to set password for Hotspot (Open connection only)
Again, if you don't find using a Pie GSI worth these sacrifices after trying it out, you can easily move to an Oreo ROM like LOS 15.1 or DotOS 2.5, which have more functioning features.
----------------------------------------
DOWNLOAD
----------------------------------------
(NOTE: The below setup will be fluid as discussion in this thread finds more stability with newer vendor builds and newer HavocOS 2.0 GSI builds)
After completion of this guide, your device will be setup with the following (might as well download everything):
Oki's TWRP 3.2.3.0 Lab's Mod v1.3
B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Oreo Modem (U, G, or Chinese)
DotOS 2.5 boot.img (This also contains the DotOS vendor, if you wish to use it)
LOS 15.1 vendor (20181110) build
HavocOS 2.0 Pie GSI (20181027) build - NOTE: Most GSIs are provided compressed. You must extract the .img file from the downloaded file.
Your preferred GApps ( https://opengapps.org/ ) (ARM64, 9.0, Micro or below only)
Also download OrdenKrieger's TWRP 3.2.3.0, going to need it handy to flash the vendor img.
And the NFC_Hotspot Fix by Kountry83 (You will need this for almost every GSI you try)
----------------------------------------
FAQ
----------------------------------------
WHATS UP WITH THE BOOTSTACKS?
The bootstacks that are currently available for the Axon are somewhat of a mess, if not careful, you can easily brick your device.
For Pie GSI setups, I recommend the B20 bootstack by DrakenFX that has been modified by Verequies, Splash version.
Verequies has asked that I also link the NoSplash version in case some users have issues with the Splash version, but many testers have had no problems with the Splash version on this setup.
Unlike the DrakenFX B20 bootstack, these modified versions do not flash the modem, so there is no need to flash modem again when switching between them. Sometimes will need to Unlock Password in TWRP when switching though, it will say not recognized.
Splash
Ability to have Read/Write access in system.
Nice three logo splash screen, replacing bootloader warning screen.
No bootloader warning screen means not able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Which also means you will have to use power button + volume up combo to enter Recovery, or reboot to recovery from the ROM.
No EDL three button combo.
Can't charge without booting system or TWRP.
NoSplash
Read Only access in system. (Which will break Magisk)
Ugly bootloader warning screen.
Able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Able to use EDL three button combo.
Allows offline charging without booting into system.
WHY EDL?
Starting out with Oki’s LOS 15.1 EDL package just makes it easier for everyone. It’s easier for you because there will be less steps needed to get treblized, which will also mean less room for error. It’s easier for me because it makes for a much shorter guide, and it’s easier to find answers to issues if we all started on the same page. However, if there are enough requests, I’ll make a longer guide without the use of EDL.
If you are already treblized you won’t necessarily need to EDL (in most cases), but if you run into issues please don’t comment until you’ve tried starting with first step.
----------------------------------------
GUIDE
----------------------------------------
STEP 1:
Please follow Oki’s Easy Guide to EDL LOS15.1
IT IS IMPORTANT TO FOLLOW EVERY STEP
Try not to boot into system while going through the steps if possible, but it’s ok if you do.
You can use @djkuz Axon 7 EDL Tool, instead of MiFlash, if you are more familiar with that.
Also, in step 12, it states to format to F2FS, but I recommend to format to EXT4 for the best compatibility with GSIs. As a precaution, to make sure your partitions will read correctly, format the partitions to F2FS per the instructions, then format them back to EXT4.
You can always test if F2FS works for you later.
Thank you @Oki for this wonderful starting point for new Treble users.
CONGRATULATIONS - You are now TREBLIZED and should never have to do Step 1 again.
STEP 2:
Once done with Oki’s guide, stay in TWRP
Wipe Dalvik, Cache, Vendor, System and Data.
Flash the bootstack you chose.
Flash the appropriate modem for your variant.
CONGRATULATIONS - You should never have to flash those again, unless changing bootstack for whatever reason.
STEP 3:
In TWRP make sure System and Vendor partitions are mounted.
Flash the DotOS Vendor flashable.
(It doesn’t have DotOS in the file name, so it should be named something like “Vendor_Flashable_GSI…”)
In TWRP go to Install and in the bottom right select Install Image
Now we flash the Havoc GSI image you extracted, selecting the System partition.
DO NOT BOOT TO SYSTEM - We need to use OrdenKrieger’s TWRP 3.2.3.0 to flash the LOS 15.1 vendor.img
(If you wish to use the DotOS vendor, you can skip to Step 5. You will still need to reboot to Recovery, so don't skip that.)
STEP 4:
Flash TWRP 3.2.3.0 to Recovery partition and then reboot to Recovery
You should now be in TWRP 3.2.3.0
Flash the LOS 15.1 vendor.img to the Vendor partition
DO NOT BOOT TO SYSTEM - We need to restore Oki’s TWRP and flash GApps.
STEP 5:
Flash Oki’s TWRP 3.2.3.0 Lab’s Mod to Recovery partition and then reboot to Recovery
You should now be in Oki’s TWRP 3.2.3.0 Lab’s Mod
Flash GApps
Make sure System and Vendor are mounted
Flash the NFC_Hotspot Fix
NOW BOOT SYSTEM
I will wait here while you setup your device.
DONE? GOOD. Lets set up Magisk and pass SafetyNet
STEP 5:
At this time I recommend Magisk 17.2
Find it, download it, and flash it in TWRP
Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.
Then search for BusyBox module by Osmosis and install it.
Reboot
Using a terminal app (not in TWRP) like Termux, type “su”
Grant root privileges
Then type “props”
You should be greeted with a menu
Select 1 to Edit fingerprint
Select F to Pick a Certified fingerprint
Then follow the menu to select ZTE and Axon 7
Then yes and yes to reboot.
Everything should be good to go now. ENJOY!!
To add just a few more options to your setup without overdoing it with a heavy launcher, I highly recommend:
Lean Launcher Optimized
I will surely be adding to this guide and modifying it as the situation evolves. So feel free to give me any input on how to improve it.
----------------------------------------
THANKS
----------------------------------------
Thanks to @raystef66 and all of the testers in the [SUMMARY][PIE] BEST PIE ROMS to TRY thread, as well everyone in the "Axon7 (s)GSI trebleSHOOT" Telegram group, for testing, "trebleSHOOTing" and reporting your findings.
Thanks to @Oki again for his easy guide and LOS 15.1 EDL package.
Thanks to @Unjustified Dev for uploading separate vendors for us GSI users, and for all of the work he's done on LOS and his help in the LOS threads.
Thanks to @Verequies for creating the two modified versions of @DrakenFX 's B20 bootstacks, and of course @DrakenFX for his B20 and B12 bootstacks.
Thanks to @SaintZ93 for his work on DotOS and for providing a flashable for boot and vendor only.
Thanks to @SaintZ93 and @Skrem339 for their great work on the Schwifty kernel.
And thanks to @hundeva for his work on Lean Launcher.
----------------------------------------
GUIDE EDIT LOG
----------------------------------------
11/22 - Updated that it is optional to stay with DotOS vendor and skip a step.
11/30 - Changed Step 1 to recommend EXT4 for best compatibility. Also to format from EXT4 to F2FS, then back to EXT4, to avoid internal storage error some are getting.
12/10 - Props Config module now requires BusyBox module, updated Step 5.
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
Please make sure you redownload Ordens TWRP. There are two of them with the same name out there. The one I linked should allow you to see Vendor partition. I should list this step as optional, as the DotOS vendor works, Ive just found the LOS vendor to show improvement personally. I also wanted to teach how to flash vendor.img, as there is only one way atm, using Ordens TWRP.
The vendor setup in this guide is all based off LOS sources, so any issues LOS is having that are vendor related will carry over to this setup. Sorry.
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Mousman said:
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
Click to expand...
Click to collapse
I found minor things to work better with the LOS vendor, such as GPS locking and Bluetooth not freezing display data in my car. Of course this can vary from user to user. And my preference changes as well when I find improvements with other vendors.
The DotOS vendor flashable is provided as it's the easiest way to get an up to date vendor. Otherwise you would have to download and flash an entire ROM, or extract the boot.img from that ROM, or modify the install script. Unjustified didn't provide the LOS vendor in combo with the boot.img, so the DotOS flashable is the best option as of now.
If you're already on the Havoc GSI, then you can just flash the bootstack, wipe vendor, flash DotOS vendor flashable, flash LOS vendor.img if you want (using Ordens TWRP), flash Magisk. Then boot.
It will feel like a dirty flash, but it's not, thanks to Treble.
Please do a full backup before doing so, as I think if your vendor partition was created differently, pulled from data, it might not work.
Kleva94 said:
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Click to expand...
Click to collapse
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
EBeatFLA said:
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
Click to expand...
Click to collapse
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
piet8stevens said:
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
Click to expand...
Click to collapse
This particular setup will sacrifice encryption. Getting encryption on a GSI would be another path. The TWRP and bootstack options we have for our device play a part in why I find encryption to be a mess right now, and chose to move forward without it.
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
g0dzstar said:
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
Click to expand...
Click to collapse
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
OMG guys, so sorry, was linking to the wrong TWRP. Link updated. It's not on AFH, so if you don't trust it's a legit link and want to check, it's the same link in the LOS16 op.
Thanks for testing.
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Reakleases said:
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Click to expand...
Click to collapse
Make sure to follow all of the steps in Oki's guide. Also, if you used the NoSplash bootstack, that might be it. But I'm pretty sure it's a missed step in his guide.
did everything again without success, but something of that helped, tried chmod 755 on root directory and fix contexts.
Really nice guide, thanks!
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Make sure system and vendor are mounted before flashing.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Predatorhaze said:
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Click to expand...
Click to collapse
Thanks for the reply.
I flashed the bootstack in the EDL package uploaded in the guide using MiFlash went through fine. Also did a clean wipe of everything and formatted my Internal Storage before I flashed the package.
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global Rom but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx, due to support wifi 2.4 ghz only. (Because bluetooth interfering with wifi 2.4 Ghz and our device doesn't support 5ghz wifi)
Compare to MIUI, Havoc OS has somethings i like:
+ Faster download/upload speed: no delay with wifi bluetooth interference
+ Doesn't have bloatware, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk and root.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI and extract to get system
From Official Havoc OS here: https://sourceforge.net/projects/havoc-os/files/a64-ab/ (Newer Version)
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature. If it doesn't work, then try an alternative way:
Open /vendor/bin/init.qcom.post_boot.sh and add the string:
Code:
sendevent /dev/input/event2 0 1 5
then reboot
13) Enjoy Havoc OS. Install apps, configure settings...
How to Update
- Flash system image over, no wipe require. Just reboot.
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from https://vancedapp.com/; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
- To fix Recording, from Misc features -> Force Timestamp Source, choose Clock boottime
And that's all. Now enjoy!
I gifted my sister this phone so i don't have device to test anymore. Still, sometime i'll test if i can. The guide still works so enjoy flashing!!!
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
ways2 said:
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
Click to expand...
Click to collapse
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw module working, despite i don't active the xiaomi option in setting.
Ga_hap_la_chanh said:
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw working, despite i don't active the xiaomi option in setting.
Click to expand...
Click to collapse
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
ways2 said:
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
Click to expand...
Click to collapse
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Thank you sir
thanks a lot for this
can you tell me how to upgrade our 32bit os to 64bit
Ga_hap_la_chanh said:
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Click to expand...
Click to collapse
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
eddy law paul king said:
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
Click to expand...
Click to collapse
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
ways2 said:
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
Click to expand...
Click to collapse
i am very afraid that i brick my devise
so make a video
it is accurate and much helpful and easy to understand
i am waiting
Can I use the attached files for installing gsi in redmi 9 ?
vinith 32 said:
Can I use the attached files for installing gsi in redmi 9 ?
Click to expand...
Click to collapse
no
this is for 8 and 8a only
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
ways2 said:
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
Click to expand...
Click to collapse
I used TWRP then moved to Orange Fox. Everything working fine, may be your screen is different. In d2tw module, there's a file called readme.md: Manual usage : - enable $ set-dt2w 1 - disable $ set-dt2w 0
Just try it -))))))))
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
ItsmeTushar said:
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
Click to expand...
Click to collapse
Boot.img and vbmeta are done before flashing the gsi. I'd recommend reading this thread first for better understanding
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Zzzleepy said:
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
Click to expand...
Click to collapse
That was weird. In stock ROM, I can back up the /data/media just fine even when encrypted. But after having Havoc OS, I cannot do that anymore. Tried on both TWRP and OrangeFox. I can, with an unencrypted phone, but I do not feel comfortable without a lockscreen. Tried all things I have researched on that error. Not one worked. Might as well just stick to Titanium Backup for backups.
Overall, great GSI. Loading is faster than on stock (with the internet too)! Though, I have another issue with regards to the locking of apps, so that the app would not be cleared. Speaking of clearing apps, it is tiring to scroll left just to see the "Clear All" option in Recents. Autostart too.
I know you are not the developer, but just letting you know my concerns.
How to resize system partition for install gapps?
Soerex24 said:
How to resize system partition for install gapps?
Click to expand...
Click to collapse
Reboot to custom recovery > Menu > Manage Partitions > System > Resize or Repair
Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.
Hi all,
please find attached the Havoc OS 3.8 custom ROM, Olivelite version, and Magisk 20.4 which you will need for installation also.
I am neither the creator of this ROM or anyhow involved with the team, nor do I take any responsibility for everything which might go wrong during installation.
How I got it to work:
1. Unlock your boot loader (you will find appropriate instructions here in the forum and elsewhere on the web, also on YouTube).
2. Ensure that you have the XiaoMi Flash tool and the latest stock rom available, to be able to recover you phone when you encounter issues.
Both can be found on the Xiaomi website.
3. Get the "minimal ADB and Fastboot" tools. You will find in the web.
4. Get TWRP (you will find out what this is and why you need it here in the forum). Take care that it is a version for your phone model, else worst case it will not work.
5. Put the attached files to an external SD card in your phone.
6. install TWRP. Boot into "Fastboot" mode and install TWRP with command "fastboot flash recovery twrp.img".
7. Boot into recovery mode - if yoiu did everything right, should be TWRP now
7a. Wipe - Format data - confirm with "Yes", then go back to main menu
7b. Wipe - advanced wipe - select all except the last 2 (expecially NOT "external SD" if you put your files on there),
go back to main menu
7c. Install - select location where you've put the "havoc 3.8 update.zip" and select the file, afterwards wipe Cache / Dalvik (TWRP will give you this option after install), DO NOT REBOOT
7d. Install - select location where you've put the "magisk v20.4.zip" and select the file, afterwards wipe Cache / Dalvik and then reboot to system.
Now, hopefully, congratulations and enjoy
If something happens and it will not work at all, search the web first for solutions and, if still does not work and you do not get along with it, do not worry. You can always go back to the Xiaomi original ROM with the XiaoMi Flash Tool. Phone must be in "Fastboot" mode for this. In the flash tool, select your ROM location (ideally in the root of your drive as this tool cannot interpret spaces in paths), then confirm and ensure that you have ticked "Clean all" in the bottom, NOT "clean all and lock" - else you will have to do the unlock procedure again.
Sometimes, you need the "permissiver v5.zip" which you will find on the web. In case the above does not work, you can try to install the Permissiver. I never needed it, and I'm using 2 Redmi Olivelite.
I just tried this and had a success message from TWRP about the Havoc 3.8 flash but the Majisk file had an error from within TWRP first time & then it installed after reboot. But I still go straight into TWRP after rebooting.
Right now I have TWRP on the device & a micro SD card to get files onto the device but no OS on it & no backup as one way or another I want a ROOTed OS & it was the Chinese version when I got the phone so useless to me anyway.
What's the best approach from here to get this thing running again?
Thanks!!! Thanks!!! Thanks!!! after trying to get a GSI rom run on my daugthers olivelite i finally got a new rom working. I don't know why last guides didn'twork for me actually a recently requested a boot.img patch but i managed to patch it myself after dealing with python. Now will try to update it to 3.12 i suppouse it iwll have many improvements. But this worked right out of the box for me. Just followed each step and good to go.
For anyone interested. its de 2Gb/32Gb Global Version. with 12.0.3 latest MIUI updated applied trough fastboot. I used OFOX to test it and it worked fine by now.
If you have guide to update HAVOC please point me in the right direction.
Thanks again
I got off .Havoc precisely because it did not have voLTE support & BT HS 's didn't work. Has anyone had any luck on these 2
I absolutely thank you for this rom, I can now miraculously play Asphalt 9 on high settings at 30ish fps while on miui it struggled on lowest settings, the UI is flawless but I only have one problem I can't send nor receive SMS and the phone sometimes reboots randomly but that cannot make me go back to miui since it's too heavy for my phone.
IS THERE any fix for not being able to receive or send SMS
I have a black screen [FIxed by installing OrangeFox recovery]