Ah, So You've rooted your 6.1 Plus/X6 but don't know how to Install stock or having troubles with it? I'm here to help!
*All of the instructions and procedures below requires an unlocked bootloader. If you do not have an unlocked bootloader, Please refrain from asking about it here.
*Not having an unlocked bootloader and following this will definitely brick your phone. You have been warned.
Installing Stock ROM - Method 1A(Nost) --
1. Get NOST from here - NOST
2. NOST ONLY SUPPORT OREO FIRMWARE, USE OST LA FOR PIE(Not sharing cause its a patched app, Search on Google and get it from TechMesto)
3. Download unpacked oreo firmware, You can get it from - Here
4. Extract the zip on your PC
5. Put your phone in bootloader mode, Power off - Press Volume Down+Power Button.
6. Now connect it to your PC
7. Open NOST, Select the .mlf file from the folder where you extracted the Firmware
8. Now select, Normal download and Erase User data option.
9. Now click on next and wait for NOST to flash the phone. (It takes 258 seconds or 2.3 - 2.5 minutes on my laptop)
Installing Stock ROM - Method 1B(OST LA) --
Same as NOST, It has the same UI.
Except You might have to change some values in the .mlf file.
An appropriate guide for the same - Here
Installing Stock ROM - Method 2(Hikary's Generic Flashing Script) --
I recommend this method more than NOST and OST LA.
1. Get Hikary's script from - Here
2. Get unpacked Firmware from - Here
3. Extract the Firmware
4. Put the .exe file you got from Github into the folder where you Extracted the firmware
5. Run the script
6. Follow instructions on screen
7. Profit!
Thanks alot to member - Hikary for this easy to use scipt!
You've installed Stock, Now let's add some magisk to it !
*Please disable Automatic System Updates through developer options to make taking OTA .zips easier.
Installing Magisk - Method 1A(Fastboot method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Extract ADB to a Folder
2. Get Magisk patched boot images from - Here Don't worry, Boot images for Nokia 7 Plus will work on DRG(6.1 Plus/X6) and PL2(6.1)
3. Open adb(Type cmd in the address bar of the folder where you extracted adb)
4. Put your device on Download mode
5. type the command
Code:
fastboot boot 'nameofbootimage'.img
6. Now your phone will boot
7. Install Latest Magisk Manger from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
8. Open Magisk Manger, You will see Magisk is installed, But there will also be an Install Button next to it. Tap on Install.
9. Let Magisk Install and re-boot the phone
10. Viola Magisk is now permenantly available
Installing Magisk - Method 1B(TWRP method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Get the latest TWRP for 6.1 Plus
2. Get the Latest Magisk Installer from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
3. Put the .zip file to your Internal Storage/SD Card
4. Open adb and pass the command
Code:
fastboot boot "nameofrecoveryfile.img"
5. Now TWRP will open on your phone
6. Install Magisk through TWRP
7. Wipe Dalvik
8. Reboot
9. Profit
Now you've got magisk. Follow the next post to see how to take an OTA update with Magisk Installed.
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
CarbonGTR said:
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
Click to expand...
Click to collapse
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Hymix said:
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Click to expand...
Click to collapse
Open Magisk Manager, Tap on Uninstall. You will see 2 options, Complete Uninstall and restore stock images.
*Nevar tap on the complete uninstall option, It will throw your phone into bootloop
To install to inactive slot, Tap on install, You will get 2 options, Release Notes and Install. Tap on Install again and select install to inactive slot, Reboot from within Magisk Manager.
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Hymix said:
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Click to expand...
Click to collapse
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
CarbonGTR said:
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
Click to expand...
Click to collapse
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Click to expand...
Click to collapse
It's easy. Get an OTA .zip file, Re-Boot to recovery and flash it. Or Use the ADB Sideload method.
Most likely installing the OTA would fail if the device is rooted because, Magisk will patch the boot.img.
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Click to expand...
Click to collapse
I just took an OTA with Magisk installed it went fine. (September patch)
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Hymix said:
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Click to expand...
Click to collapse
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
CarbonGTR said:
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
Click to expand...
Click to collapse
Really? I did the restore via Magisk and that seemed fine, but then the update part didn't work. It downloaded then gave the error so I quit and started again with a fresh installation, minus Magisk.
Sent from my Nokia 6.1 Plus using Tapatalk
Have you guys modified the system/vendor partition in any way? If you did, Then it will obviously fail.
@Bluebriz and @Hymix I agree. It's the september security patch causing the installation issue.
It fails for me no matter what, Unless I completely un-root. But this method works perfectly fine on the August update.
Lets see for the October patch.
Okay, I can specifically narrow this down to way the September patch. The september patch requires the August security patch as a precondition to install. And that's where something funky is happening.
Guys a quick update. October update has been released but it also fails to install. This time I've managed to find the cause, Apparently some service that needs to be used for the update is being blocked/used by Magisk. (I could be wrong here)
The error code according to the recovery is 20(kDownloadStateInitializationError)
Is there any update to this issue?
Tried removing Magisk, didn't help.
Yesterday I got November security update ..iam using magisk...so it is showing installation problem...I tried in recovery and ADB method both didn't work.. finally I ended in bootloop ...so I again installed stock ROM...any solution is there without resetting each time how to install security updates..coz each time my data balance was wasted??
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.
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
ScarletWizard said:
Thank you for this I will post this on the telegram channel
Click to expand...
Click to collapse
What is the link to the telegram chan?
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
My CPH2459 crappped out on me, and I have had little luck since moving from GN2200 to this model and could use a backup if you could lend a hand
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
OnePlus Nord N20 | Official
You can view and join @oneplusnordn20 right away.
t.me
ScarletWizard said:
Incorrect link
Click to expand...
Click to collapse
Can you share the right channel.
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
Click to expand...
Click to collapse
Damn son, your attention to detail is admirable! Very thorough and well-documented. Thanks.
Can I use this on the new ota update
mvincent2k said:
a.img = boot_a.img magisk patched
Click to expand...
Click to collapse
killerex said:
Can I use this on the new ota update
Click to expand...
Click to collapse
No you would need an updated img if you are on the latest upgrade. I no longer have an N20 to test with otherwise would create one for the group. Someone else may possibly.
How? I'm not updated yet can guide me how to do it.thank
killerex said:
How
Click to expand...
Click to collapse
Search the other XDA threads here for this device. A few explain how to extract payload and patch.
If you are on the previous update, see the update to my instructions just posted on how to take the OTA and stay rooted with Magisk
I'm getting installation error.. I'm in previous update
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
Click to expand...
Click to collapse
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
PsYk0n4uT said:
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
Click to expand...
Click to collapse
Not a problem. Always glad to help the community out!
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
Just make sure your using a12 boot image if your trying to use a posted one.balso be sure to use the same security patch boot image as the system you already have installed.
Safest bet is to use the DSU sideloader method to pull your own boot image and then patch it if your unsure of which patched boot image to use. It's a little more complicated but pulling your own boot image will ensure that you have an exact match for your device.
If you have or can locate and obtain an unpatched boot image that matches your system. You should have one on hand just in case the patched boot image doesn't work so that you can simply reflash your stock image in that case.
A mismatching boot image can lead to an unbootable state so you need to be prepared.
You shouldn't have to worry much about anything crazy or unrepairable so long as your flashing boot images made for the device your flashing them to. Just don't flash boot images from a completely different device as that can cause you to end up with any sort 9f crazy weird issues that may not even be fixable.
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
By any chance you got the latest boot.img
Will this work on a GN2200?
NO
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
alipps1 said:
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
Click to expand...
Click to collapse
I recently ran into this on another device and had to fix so you are in luck. I believe something broke with magisk running on 13 during the last OTA with security, so here are the steps...
1) Unhide and Uninstall magisk app completely and Update to the latest canary version of magisk apk here and restart: https://github.com/topjohnwu/Magisk
2) Verify it sees magisk installed and has latest build.
3) Try restoring images again and it may work.
If that does not work...
1) You will need to do a full unroot...which technically should not work if the images were not present, but it does, so images are present (proving it is a bug)
2) You will need to complete the full procedure of patching the boot image again yourself.
3) Extract payload and patch the boot.img per instructions in this forum, then flash per my instructions above.
FYI. I did this on the current version of the OS and then did the restore images and upgrade to take the OTA and prove the bug and that OTA updates will work as in the instructions above in the future again, which it did.
Alternatively, you could also update the to the latest OTA after unrooting and just do it once, but I wanted to play it safe just in case Google updated something in the latest 13 builds blocking magisk... So your choice, but please post back here how you make out.
Good luck