WORK IN PROGRESS: This all started in a quest to stay locked, but have root and Magisk running on my phone, and eventually unlocking to install a custom kernel which wouldn't trip SafetyNet.
I've had to compromise on staying locked as unlocking the boot loader was ultimately necessary. As of this update to the guide, I have root, Magisk, and system-less Xposed working with each other. SafetyNet, however, is partially broken.
This is my experience on my new ZTE Axon 7 unlocked U.S. variant (A2017U), running build B29.
I'm certain that most of my problems had to do with the write-protected /system partition, as well as the encryption of fstab (verity check encryption/SE Linux status). I finally got some things working by using the method that follows, and I've opened this thread for anyone wishing to learn from what I've done, and possibly sharing with us, better methods of achieving this:
-> Device needs to have its bootloader unlocked, or else you will get a boot-loop into EDL mode. Use your prefered method for this.
-> TWRP 3.0.2.0
-> Last working SuperSU v2.65, which should install in systemless mode (tenfar's patched boot.img doesn't work for me).
-> A way to disable fstab encryption. I got it done using both: a custom kernel called Kali Kernel (also check this post for a stripped down version of the kernel) and through DrakenFX's script available here.
-> Magisk Manager, and Magisk flashable zip versions available here (look under downloads, v2.5 and v9 respectively as of this writing): [url]http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
-> ADB shell (you can either use Terminal Emulator from the Play Store or ADB Shell on your computer.
After you have unlocked the bootloader, with any of the unlocking guides here on XDA (I used DrakenFX's zip, ultimately. God bless that dude!): Boot into TWRP, flash SuperSU v2.65 mentioned above.
Proceed to flash DrakenFX's boot loop patch.
Boot into the system.
Update SuperSU to the latest version through the Play Store (v2.79 as of this writing, should be automatic).
Open the SuperSU APK and update the SU binary at the prompt. Reboot the system.
Once booted back into the system: Open an ADB shell (either through terminal emulator, or through ADB shell on a computer) and type the following:
Code:
su
reboot disemmcwp
The phone will reboot.
Boot into TWRP and flash the Magisk v9 zip file.
Here, I would advise flashing the Kali kernel as well (if you're interested in passing SafetyNet validation, or even if you aren't as it worked for me this way). There is a stripped down version of the kernel available here (source post here).
Boot back into the system.
Once you're up, proceed to install the Magisk Manager.
If it is still showing up undetected then reinstall through the app, reboot into TWRP and flash the Magisk v9 .zip file as well, and reboot into the system.
Reboot system at the prompt.
A word of caution regarding Magisk's implementation of suHIDE: it can't be used with this method as it breaks root after a while, and apparently has no impact on a superuser system which is not a Magisk module. I am exploring Chainfire's suHIDE implementation in the coming days.
Hope it works for you all!
Edits: Updated guide to reflect my current research gains, and removed superfluous text. I will upload screenshots of my status as soon as I get back to my computer.
Updated screenshots to the current state.
{
"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"
}
Still no work for me. I can install it but when i reboot Magisk disapear. And i don't know why but magisk worked good before i do a factroy reset.
Alright, still working on streamlining my methods, and I've managed to get root, Magisk, and system-less Xposed playing nice together.
The next step was to try to not trip SafetyNet with this setup, and I've made some progress on that front. It involves installing the patched Kali kernel (as I've done so far) and suHIDE from Chainfire (next test, tomorrow).
I'll update the OP tomorrow, with screenshots!
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Znuf said:
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Click to expand...
Click to collapse
I've just updated the guide. Do you want to give it a shot and see whether it works for you?
It's exactly what I do many time, at least 10.
But it's never activated after boot. :sad:
If I found a way I'll post here
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Znuf said:
I found a way.
On unlocked phone.
Install supersu 1.65
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk framwork
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9
Reboot system.
This worked for me. 😀
Click to expand...
Click to collapse
I have a couple of doubts about your procedure before testing it twice:
1. Are you sure you have to install SU v1.65? Why not SU v2.65?
2. you are referring to the magisk framwork, but I do not find it. Were you referring to Xposed framework maybe?
It would be easier if could provide some links to the download pages, just to match versions.
Thanks
I update my post. Sorry for the poor precision. It was late. ?
Znuf said:
I update my post. Sorry for the poor precision. It was late.
Click to expand...
Click to collapse
Thanks for the clarification, I understand that when you say install Magisk v9, you rever to install within the Magisk manager app, and then later, booting directly to TWRP flashing the Magisk v9 zip file.
I have been experimenting with Safetynet helper and I have found that it doesn't pass when the phone is unlocked. As soon as I unlock the bootloader, the safetynet helper reports a CTS profile doesn't match. Even when using the stock boot and stock system without any root!!!!
Any thought on this???
blue skies
So Android Pay is working with this method?
JKSurf said:
So Android Pay is working with this method?
Click to expand...
Click to collapse
Not for me.
I am still experimenting, there must be a way.
---------- Post added at 17:30 ---------- Previous post was at 17:23 ----------
Znuf said:
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Click to expand...
Click to collapse
I have done exactly that with the B29 ROM with stock boot and system. For some reason Magisk manager keep asking for Magisk v9 even after the whole process has been completed. I have root thanks to SuperSU, but safetynet helper test doesn't pass.
A better question is if you can pass the SafetyNet check apps.
I posted this in the thread that started this one, but with the official TWRP you can flash recent versions of SuperSU, not just 2.65 anymore (that was a limitation of the unofficial).
I know this thread relates to getting Magisk working, but unless there's a specific module you're looking to use, I don't see a benefit to using it for systemless root over SuperSU. I had tried to install it before using unofficial TWRP and had problems, but I think those, like the inability to install SuperSU past 2.65 we're due to faults with the unofficial TWRP. Official TWRP should install Magisk just fine (haven't cared to try it).
That said, if Android Pay is you're concern SuperSU might be the way to go. I am running SuperSU 2.79, Xposed 86.2, suhide 0.55, and Root Switch 1.3.3.2 and am able to pass both of the popular SN test apps (SafetyNet Helper and SafetyNet Playground). I don't use AP to know if that functions, but Pokémon GO, which also relies on SafetyNet runs just fine.
Also, as far as kernel goes, if you want one that doesn't have all the extra stuff the Kali NetHunter kernel does, there's a stock kernel patched for SafetyNet, kcal, and exFAT in this post of the same thread.
If you don't care about Xposed, SuperSU and Root Switch should be all you need to pass.
And as I mentioned in the other thread, this will likely all be rendered useless by the Nougat update hopefully coming next month.
The method I posted as an update in the OP the other day closely follows @Znuf's method, and all the relevant files are linked in the OP. Still a bit busy to experiment more, but this is how far I had gotten with the method I had posted, and, in theory, should work with suHIDE. Even the Kali Kernel I have linked to is the patched one without the extra tools.
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
I'll try this out and update it soon. Screenshots attached is my progress on the last update..
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
H0lmEd said:
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
Click to expand...
Click to collapse
The bootloop fixer script should work on all devices as it just disables forced encryption in your bootloader. Make backups and try it out. If you experience a problem just restore the backed-up boot partition.
I'm on 2017g no bootloop.
Erahgon said:
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
Click to expand...
Click to collapse
suhide will only work with Xposed 86.2 (which is provided in the same post).
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Oki said:
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Click to expand...
Click to collapse
Yep, Xposed modules still work, all you're toggling is root and no reboot required to disable/enable root. It's worth clarifying that while modules will still work, root apps obviously won't while disabled. Also, while root is disabled, Xposed installer will say Xposed isn't installed - as long as Xposed installer is green when root is enabled you're good.
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.
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
{
"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"
}
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
can you make an English video please thx!
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Not happening.
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
the_bulk said:
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
Click to expand...
Click to collapse
Theres no official TWRP for Speadtrum based 2016 J3s. There are newer versions for the J30F/FN i think, but atm i don't care/need it.
Since we don't have an Exynos or Qualcomm SoC, the custom rom scene doesn't look so good. Pretty much you have Lineage (MM & N), RR (N) and more recently DotOS (N), but they all suffer from pretty much the same problems give or take, in top of that most of the other roms are dead since the devs moved on to other phones, the ones I mentioned before don't really receive updates oftem. Right now im using stock with root and Xposed, is working fine, however im thinking about giving a second chance this rom: https://forum.xda-developers.com/galaxy-j3-2016/development/j2-pro-port-markus-rooted-t3657383 is stock MM, a port from the j210F wich i think is newer and somewhat better than this other j2 port: https://forum.xda-developers.com/galaxy-j3-2016/development/marshmallow-rom-j320f-t3623551
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Odin Faild
Hi Guys!
I tried to flash the TWRP recovery on my J3 (2016) , but odin saids its faild could you help me with it please?
milewap said:
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Click to expand...
Click to collapse
I flashed latest Magisk v18,with TWRP and yes TWRP vorks great tnx dev...for all :good:
Here's another one TWRP custom recovery,this one he has a bekap EFS....downloaded from 4pda ru site.All credits goes to them
SM-J320F-TWRP-F2FS.tar.md5
And here SM-J320FN-TWRP-F2FS.tar.md5 for FN but it does,on J320F i flashed today and works without problems.
Here it is PIT J320F if someone needs it...
Need help
mauriciognr said:
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Click to expand...
Click to collapse
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
AminNadery said:
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
Click to expand...
Click to collapse
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Sorry for bothering again.
mauriciognr said:
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Click to expand...
Click to collapse
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
AminNadery said:
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
Click to expand...
Click to collapse
First, perform a factory reset and flash your stock ROM (with odin), afterwards twrp and then magisk. Whatever problem you might have it will go away after a clean install of your rom. Use latest magisk.
Odin
Can I do this without computer???
Does anyone know how i can delete all Xposed related material through the TeamWin recovery at the beginning? I was rooted and tried installing Xposed and the phone wont go past the sprint logo anymore. I that cant be fixed How do i reset my phone completely to atleast have what i had before. thanks if anyone answers.
CRICE89 said:
Does anyone know how i can delete all Xposed related material through the TeamWin recovery at the beginning? I was rooted and tried installing Xposed and the phone wont go past the sprint logo anymore. I that cant be fixed How do i reset my phone completely to atleast have what i had before. thanks if anyone answers.
Click to expand...
Click to collapse
Well you installed the wrong xposed get an xposed Uninstaller put it on your sd card and flash it in xposed and you be good to go you need the wanam 87.1 xposed for the J3 emerge and if you want systemless xposed you got to lower your magisk to 15.3 and then flash wanam systemless xposed 87.3 (if you try to flash that systemless on a higher magisk you will get error 1 cause the template for that xposed sadly isn't getting updated) after its flashed wipe and your phone boots up you going to see that it's in your modules list then you can flash the new magisk (on magisk 19 and higher it will show that xposed is not installed but it is its just an error that the xposed material installer or regular installer isn't updated to perceive how magisk places modules in 19 and up but when you download modules or check your xposed modules it won't say xposed not installed so you be good hope this helps you)
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
thanks one more thing
PoochyX said:
Well you installed the wrong xposed get an xposed Uninstaller put it on your sd card and flash it in xposed and you be good to go you need the wanam 87.1 xposed for the J3 emerge and if you want systemless xposed you got to lower your magisk to 15.3 and then flash wanam systemless xposed 87.3 (if you try to flash that systemless on a higher magisk you will get error 1 cause the template for that xposed sadly isn't getting updated) after its flashed wipe and your phone boots up you going to see that it's in your modules list then you can flash the new magisk (on magisk 19 and higher it will show that xposed is not installed but it is its just an error that the xposed material installer or regular installer isn't updated to perceive how magisk places modules in 19 and up but when you download modules or check your xposed modules it won't say xposed not installed so you be good hope this helps you)
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
I used SuperSu not Magisk.., Can i download the Xposed uninstaller on my phone ? and i tried removing everything that had xposed on it ftom the team win area the boot recovery mode. What do you mean flash it in Xposed ? or do you mean just flash the xposed uninstaller?
CRICE89 said:
I used SuperSu not Magisk.., Can i download the Xposed uninstaller on my phone ? and i tried removing everything that had xposed on it ftom the team win area the boot recovery mode. What do you mean flash it in Xposed ? or do you mean just flash the xposed uninstaller?
Click to expand...
Click to collapse
Yeah I meant flash the xposed Uninstaller in twrp..... Yeah put the xposed Uninstaller on your SD card and put the sd card back in your phone... Why would you use supersu it's deprecated
Sent from my SM-J327P using Tapatalk
tried this didnt work
PoochyX said:
Well you installed the wrong xposed get an xposed Uninstaller put it on your sd card and flash it in xposed and you be good to go you need the wanam 87.1 xposed for the J3 emerge and if you want systemless xposed you got to lower your magisk to 15.3 and then flash wanam systemless xposed 87.3 (if you try to flash that systemless on a higher magisk you will get error 1 cause the template for that xposed sadly isn't getting updated) after its flashed wipe and your phone boots up you going to see that it's in your modules list then you can flash the new magisk (on magisk 19 and higher it will show that xposed is not installed but it is its just an error that the xposed material installer or regular installer isn't updated to perceive how magisk places modules in 19 and up but when you download modules or check your xposed modules it won't say xposed not installed so you be good hope this helps you)
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
I tried what you said thanks for responding but that didnt work for me what else can I do ? thanks again
new update
CRICE89 said:
I tried what you said thanks for responding but that didnt work for me what else can I do ? thanks again
Click to expand...
Click to collapse
now it says no OS installed when i try to reboot did i mess up the phone completely now ?
CRICE89 said:
now it says no OS installed when i try to reboot did i mess up the phone completely now ?
Click to expand...
Click to collapse
I don't understand how you flash the Uninstaller zip for xposed and now twrp is saying you have no os installed as if you wiped the system partition if that is however your case I would suggest Odin your stock firmware and after it boots oem unlock again and flash twrp and then search for the proper xposed also root this time with magisk also are you flashing the decrypt zip to make your data partion accessible via twrp so you can do backups im surprised you didn't even have a twrp backup in place before even attempting to flash xposed
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
1 more question
PoochyX said:
I don't understand how you flash the Uninstaller zip for xposed and now twrp is saying you have no os installed as if you wiped the system partition if that is however your case I would suggest Odin your stock firmware and after it boots oem unlock again and flash twrp and then search for the proper xposed also root this time with magisk also are you flashing the decrypt zip to make your data partion accessible via twrp so you can do backups im surprised you didn't even have a twrp backup in place before even attempting to flash xposed
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Will you tell me the things I need to do this? Do i use the same Odin I used to root ? and yeah I know i didnt know what i was doing I wiped the system thinking it would solve my problem..., Just if you can give me a list of the things i need for this that would be very appreciated... Im new at this rooting stuff I only wanted to root to change the color of my system font to like blue or purple bit it didnt work out for me haha thanks again for all of your responses. : )
CRICE89 said:
Will you tell me the things I need to do this? Do i use the same Odin I used to root ? and yeah I know i didnt know what i was doing I wiped the system thinking it would solve my problem..., Just if you can give me a list of the things i need for this that would be very appreciated... Im new at this rooting stuff I only wanted to root to change the color of my system font to like blue or purple bit it didnt work out for me haha thanks again for all of your responses. : )
Click to expand...
Click to collapse
Well to change the color of the font you going to use ifont app and it has a xposed module with it that gives you the ability to use color fonts.... Now the process is simple your going to reflash the firmware for your phone to get it up and running... After your up and running your going to unlock develop options in the settings by going to about device and tying on your bulid Verison a couple of times and when your in them settings you going to make sure oem unlock is on, once you do that you going to flash twrp again and this time you going to download magisk and flash it the newest stable one to obtain your root after that you going to look for xposed Verison 87.1 special Samsung bulid by wannam and flash that wipe Dalvic and cache and reboot its going to take a little while but after that it's going to boot system optimize all your apps and then finally download or get it before the xposed material installer it's going to say xposed Verison 87.1 is active after that you can download the ifont app activate the module in xposed and proceed to change your color font...
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Magisk ???
CRICE89 said:
Will you tell me the things I need to do this? Do i use the same Odin I used to root ? and yeah I know i didnt know what i was doing I wiped the system thinking it would solve my problem..., Just if you can give me a list of the things i need for this that would be very appreciated... Im new at this rooting stuff I only wanted to root to change the color of my system font to like blue or purple bit it didnt work out for me haha thanks again for all of your responses. : )
Click to expand...
Click to collapse
CRICE89 said:
Does anyone know how i can delete all Xposed related material through the TeamWin recovery at the beginning? I was rooted and tried installing Xposed and the phone wont go past the sprint logo anymore. I that cant be fixed How do i reset my phone completely to atleast have what i had before. thanks if anyone answers.
Click to expand...
Click to collapse
PoochyX said:
Well you installed the wrong xposed get an xposed Uninstaller put it on your sd card and flash it in xposed and you be good to go you need the wanam 87.1 xposed for the J3 emerge and if you want systemless xposed you got to lower your magisk to 15.3 and then flash wanam systemless xposed 87.3 (if you try to flash that systemless on a higher magisk you will get error 1 cause the template for that xposed sadly isn't getting updated) after its flashed wipe and your phone boots up you going to see that it's in your modules list then you can flash the new magisk (on magisk 19 and higher it will show that xposed is not installed but it is its just an error that the xposed material installer or regular installer isn't updated to perceive how magisk places modules in 19 and up but when you download modules or check your xposed modules it won't say xposed not installed so you be good hope this helps you)
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
PoochyX said:
Well to change the color of the font you going to use ifont app and it has a xposed module with it that gives you the ability to use color fonts.... Now the process is simple your going to reflash the firmware for your phone to get it up and running... After your up and running your going to unlock develop options in the settings by going to about device and tying on your bulid Verison a couple of times and when your in them settings you going to make sure oem unlock is on, once you do that you going to flash twrp again and this time you going to download magisk and flash it the newest stable one to obtain your root after that you going to look for xposed Verison 87.1 special Samsung bulid by wannam and flash that wipe Dalvic and cache and reboot its going to take a little while but after that it's going to boot system optimize all your apps and then finally download or get it before the xposed material installer it's going to say xposed Verison 87.1 is active after that you can download the ifont app activate the module in xposed and proceed to change your color font...
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Hey thanks for the help. I have TWRP again now which Magisk do i get the latest version ? and is it installed the same way SuperSu is installed ?
Im rooted installed magisk beta 92.1
CRICE89 said:
Hey thanks for the help. I have TWRP again now which Magisk do i get the latest version ? and is it installed the same way SuperSu is installed ?
Click to expand...
Click to collapse
I rooted and and am now using magisk beta 92.1 which is the correct XPOSED APK for SAMSUNG J3 EMERGE ? ALSO I NEED THE ZIP FILE TOO CORRECT THATS ALL I NEED CAN YOU HELP 1 LAST TIME ? i just need the xposed correct files.
CRICE89 said:
I rooted and and am now using magisk beta 92.1 which is the correct XPOSED APK for SAMSUNG J3 EMERGE ? ALSO I NEED THE ZIP FILE TOO CORRECT THATS ALL I NEED CAN YOU HELP 1 LAST TIME ? i just need the xposed correct files.
Click to expand...
Click to collapse
Latest stable magisk is 19.2......
https://forum.xda-developers.com/ga...nt/wip-custom-rom-j3-emerge-sm-j327p-t3634206
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
There's also a systemless magisk for are device also however the template is old the trick to installing that would be 2 downgrading your magisk to 15.3 flashing the systemless xposed and then upgrading back to 19.2 however with the new magisk in my experience when you on 19 and higher and tru to downgrade magisk you lose root I think it's the new method Magisk is using in 19 + so since you already rooted with 19 + I suggest just flash the system xposed from the link I sent you only thing with that is with the system xposed you can't turn it off on the fly to regain safety net like you could with the systemless one
{
"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"
}
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
PoochyX said:
There's also a systemless magisk for are device also however the template is old the trick to installing that would be 2 downgrading your magisk to 15.3 flashing the systemless xposed and then upgrading back to 19.2 however with the new magisk in my experience when you on 19 and higher and tru to downgrade magisk you lose root I think it's the new method Magisk is using in 19 + so since you already rooted with 19 + I suggest just flash the system xposed from the link I sent you only thing with that is with the system xposed you can't turn it off on the fly to regain safety net like you could with the systemless one View attachment 4763721
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Thats the system xposed download link still active
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
thank you...,
PoochyX said:
Latest stable magisk is 19.2......
https://forum.xda-developers.com/ga...nt/wip-custom-rom-j3-emerge-sm-j327p-t3634206
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
CRICE89 said:
I rooted and and am now using magisk beta 92.1 which is the correct XPOSED APK for SAMSUNG J3 EMERGE ? ALSO I NEED THE ZIP FILE TOO CORRECT THATS ALL I NEED CAN YOU HELP 1 LAST TIME ? i just need the xposed correct files.
Click to expand...
Click to collapse
thank you for all your help I wouldnt have been able to root correctly without it..., THANKS...
HELLO
PoochyX said:
There's also a systemless magisk for are device also however the template is old the trick to installing that would be 2 downgrading your magisk to 15.3 flashing the systemless xposed and then upgrading back to 19.2 however with the new magisk in my experience when you on 19 and higher and tru to downgrade magisk you lose root I think it's the new method Magisk is using in 19 + so since you already rooted with 19 + I suggest just flash the system xposed from the link I sent you only thing with that is with the system xposed you can't turn it off on the fly to regain safety net like you could with the systemless one View attachment 4763721
[emoji3436]I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Hey how do I disable Xposed modules or Xposed to fix phone not starting up cause I dont wanna do the whole process all over again... Im on the TWRP screen i tried downloading a module and it wouldnt start back up.
CRICE89 said:
Hey how do I disable Xposed modules or Xposed to fix phone not starting up cause I dont wanna do the whole process all over again... Im on the TWRP screen i tried downloading a module and it wouldnt start back up.
Click to expand...
Click to collapse
You got to go into system settings thru the file manager in twrp to the xposed folder and delete the module list file and your phone will boot up with no modules enabled
Sent from my SM-J327P using Tapatalk
Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Ballroomblitz said:
Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Click to expand...
Click to collapse
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
ChazzMatt said:
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
Click to expand...
Click to collapse
I had updated to 20.4. that may be part of the problem. I'm going to downgrade to 20.1 and see if that has any effect.
Thanks.
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
ChazzMatt said:
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
Click to expand...
Click to collapse
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Ballroomblitz said:
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Click to expand...
Click to collapse
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Ballroomblitz said:
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Click to expand...
Click to collapse
Any other thoughts on this @ChazzMatt?
Ballroomblitz said:
Any other thoughts on this @ChazzMatt?
Click to expand...
Click to collapse
Will answer tonight to give you range of options.
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
Even easier way is Reboot Recovery app shortcut on desktop. Whereas, the Magisk Manager option is like 3 levels deep in that app.
We used this originally with Oreo, then I found the Advance Power Menu. But Advance Power Menu doesn't work with Pie, so for those KDZ I have to recommend this again:
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to system, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"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"
}
Ballroomblitz said:
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Click to expand...
Click to collapse
Yeah, I can relate. I got my cheap used V30 with the express intention to tinker with it, and for the wired audio.
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Here are three options -- each one successively more powerful but also harder.
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk before rebooting.
If you are slightly OCD, you will also reflash the other two root files -- Encryption Disabler (Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip) and Root Check Disabler (AK3_RCTD_Remover.zip). You shouldn't NEED to do that -- as you are just factory resetting what you already have -- but I would rather do it and not need it, than not do it and then find out "Oh, for some reason you did need to do it". (You can find those two files in the Option 3 link.) Flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot.
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS, so do NOT reboot from TWRP until you fix that. Before you use this option, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + Encryption Disabler + Root Check Disabler stored on microSD card ahead of time OR connect phone to PC while in TWRP mode and drag over all the files like with a flash drive. If you are depending on TWRP drag-and-drop to transfer files after wiping phone's internal memory, please test this functionality ahead of time. You don't want to wipe your internal memory and then find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back-to-back, then flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot. You can "stack" them all to flash back-to-back in TWRP, then hit the install button and they will successively go through the list you create.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Then, follow this post instructions below to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone post. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
ChazzMatt said:
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk. If you are slightly OCD, you will reflash the other two root files also -- encyrption disabler and root check disabler. You shouldn't NEED to do that, but I would rather do it and not need it, than not do it and then find out "oh, for some reason you did need to do it".
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS. So, before you do this, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + encryption disabler + root check disabler on microSD card ahead of time or connect phone to PC while in TWRP mode and drag over like a flash drive. If you are depending on TWRP drag and drop, test this functionality ahead of time. You don't want to wipe your internal memory and find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back to back, then flash Magisk, then the encryption disabler, root check disabler, then Magisk again. Then reboot.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Follow this post to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone thread. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Click to expand...
Click to collapse
Man! Don't know what to say, but thank you for taking the time to provide such an in-depth assist. I'll start picking away tomorrow, and let you know what happens.
WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"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"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
This is very interesting but maybe a more accurate/calm title would be better
I posted in another tread but I was on November's patch but used .15's vbmeta to root (before images were available for November)
Can I just flash vbmeta with the disable flags, and not worry about a wipe?
Confirmed working using Flash Tool method coming from 015 to 036. Used Magisk Alpha 23012 to patch boot image and pass SafetyNet on checker apps. GPay still doesn't work, though. It may be identifying that verity and/or verification is disabled. I don't use it, but it's generally what I confirm the SN fix with.
lackalil said:
Confirmed working using Flash Tool method coming from 015 to 036. Used Magisk Alpha 23012 to patch boot image and pass SafetyNet on checker apps. GPay still doesn't work, though. It may be identifying that verity and/or verification is disabled. I don't use it, but it's generally what I confirm the SN fix with.
Click to expand...
Click to collapse
To pass SafetyNet, you have to use Universal SafetyNet Fix 2.2.0, which is currently in beta on Patreon.
V0latyle said:
To pass SafetyNet, you have to use Universal SafetyNet Fix 2.2.0, which is currently in beta on Patreon.
Click to expand...
Click to collapse
Ahh, I see that in the thread now. Not a big deal for me because I don't use any apps that need it—I've just been doing it as a matter of course for a good while. Nonetheless, I'm still passing attestation with USNF 2.1.1 according to Root Checker and YASNAC.
Confirmed root working on Magisk Alpha v23001 (then reverted back to MM 23.0 to keep the old module repository links). Also updated to Nov '21 bootloader and radio at the same time. GPay stopped working for me since the Sept '21 update and all the various requirements to re-enable. I'm not that interested in GPay functionality.
schalacker said:
Confirmed root working on Magisk Alpha v23001 (then reverted back to MM 23.0 to keep the old module repository links). Also updated to Nov '21 bootloader and radio at the same time. GPay stopped working for me since the Sept '21 update and all the various requirements to re-enable. I'm not that interested in GPay functionality.
Click to expand...
Click to collapse
In case anyone is, GPay is working for me on my Pixel 5 with the November build. Magisk 23001 + MagiskHide + Riru + Universal SafetyNet Fix 2.1.1.
V0latyle said:
In case anyone is, GPay is working for me on my Pixel 5 with the November build. Magisk 23001 + MagiskHide + Riru + Universal SafetyNet Fix 2.1.1.
Click to expand...
Click to collapse
where can i get magiskhide, riru universal safety, thanks
when you receive the pixel
I update it with the latest update and then unlock booloader and root.
is this correct?
miss said:
where can i get magiskhide, riru universal safety, thanks
Click to expand...
Click to collapse
Magisk 23001, MagiskHide is in the options
Riru is in the module repo
Universal SafetyNet Fix 2.1.1
miss said:
when you receive the pixel
I update it with the latest update and then unlock booloader and root.
is this correct?
Click to expand...
Click to collapse
This would probably be the best way to do it, yes.
Great write up! Thanks for putting it together.
You talk about booting the patched boot.img as an option instead of flashing it just to make sure everything is working correctly before they flash the patched file. I just want to really suggest to people that they do this anytime they are rooting after an update.
Sure it's an extra step (because you will have to flash the modified boot.img to make root permanent), but being able to simply reboot the phone if something goes wrong to get back to a working OS is priceless. You might think the odds are very low of something going wrong and causing a bootloop if you flash the boot.img before booting it, but experience has taught me this isn't the case. It's possible that there is a Magisk module that doesn't work with the update, or it's possible that user error will cause an issue (I have copied over the wrong patched boot.img from the phone before as an example). Whatever the case, if something goes wrong you will be glad you are only booting the patched boot.img file instead of flashing it!
sic0048 said:
Great write up! Thanks for putting it together.
You talk about booting the patched boot.img as an option instead of flashing it just to make sure everything is working correctly before they flash the patched file. I just want to really suggest to people that they do this anytime they are rooting after an update.
Sure it's an extra step (because you will have to flash the modified boot.img to make root permanent), but being able to simply reboot the phone if something goes wrong to get back to a working OS is priceless. You might think the odds are very low of something going wrong and causing a bootloop if you flash the boot.img before booting it, but experience has taught me this isn't the case. It's possible that there is a Magisk module that doesn't work with the update, or it's possible that user error will cause an issue (I have copied over the wrong patched boot.img from the phone before as an example). Whatever the case, if something goes wrong you will be glad you are only booting the patched boot.img file instead of flashing it!
Click to expand...
Click to collapse
Exactly, I was guilty of not removing a Magisk module on my P5 when installing an update. And learned the hard way.
You really never know if there is some sort of residue left from your previous setup.
sic0048 said:
Great write up! Thanks for putting it together.
You talk about booting the patched boot.img as an option instead of flashing it just to make sure everything is working correctly before they flash the patched file. I just want to really suggest to people that they do this anytime they are rooting after an update.
Sure it's an extra step (because you will have to flash the modified boot.img to make root permanent), but being able to simply reboot the phone if something goes wrong to get back to a working OS is priceless. You might think the odds are very low of something going wrong and causing a bootloop if you flash the boot.img before booting it, but experience has taught me this isn't the case. It's possible that there is a Magisk module that doesn't work with the update, or it's possible that user error will cause an issue (I have copied over the wrong patched boot.img from the phone before as an example). Whatever the case, if something goes wrong you will be glad you are only booting the patched boot.img file instead of flashing it!
Click to expand...
Click to collapse
You don't actually have to flash it. If you boot the patched image and it works, you should be able to use Direct Install in Magisk to patch the image in /boot. Then, next time you reboot, the device loads that image, which should be exactly the same as what you live booted.
But yes, it's very useful to be able to test.
I was able to take the SD1A.210817.019 to SD1A.210817.036 delta OTA via System Update by restoring my boot (via Magisk) and vbmeta (via dd) partitions back to stock, then patching vbmeta in both slots (again via dd) before rebooting. No data wipe required. To simplify that process, I made a tool to patch and restore the vbmeta partitions:
Release v1.0.0-alpha01 · capntrips/VbmetaPatcher
initial commit
github.com
The process should be considered experimental until a few other people have tested it. Should anyone attempt it, I would suggest backing up any critical data.
I'm also considering making a tool to restore the stock boot backup image, in case anyone fastboot flashed, rather than doing a direct install in the Magisk app. It could also be used to download the newly installed boot image from the inactive slot after an OTA, to avoid having to download the full factory image.
Unfortunately, patching boot in the inactive slot in Magisk was disabled for Pixel devices a while back, since it caused issues with starting back up. When the December OTA comes out, I'll probably take the plunge to see if I can figure out a way to make it work.
On a related note, a fix that will allow Magisk to properly detect the current slot on Pixel 6 devices has been approved. Hopefully it'll get merged before the next mainline canary build, so we can stop using custom builds (or having to fastboot flash boot_b when on slot B).
capntrips said:
I was able to take the SD1A.210817.019 to SD1A.210817.036 delta OTA via System Update by restoring my boot (via Magisk) and vbmeta (via dd) partitions back to stock, then patching vbmeta in both slots (again via dd) before rebooting. No data wipe required. To simplify that process, I made a tool to patch and restore the vbmeta partitions:
Release v1.0.0-alpha01 · capntrips/VbmetaPatcher
initial commit
github.com
The process should be considered experimental until a few other people have tested it.
I'm also considering making a tool to restore the stock boot backup image, in case anyone fastboot flashed, rather than doing a direct install in the Magisk app. It could also be used to download the newly installed boot image from the inactive slot after an OTA, to avoid having to download the full factory image.
Unfortunately, patching boot in the inactive slot in Magisk was disabled for Pixel devices a while back, since it caused issues with starting back up. When the December OTA comes out, I'll probably take the plunge to see if I can figure out a way to make it work.
On a related note, a fix that will allow Magisk to properly detect the current slot on Pixel 6 devices has been approved. Hopefully it'll get merged before the next mainline canary build, so we can stop using custom builds (or having to fastboot flash boot_b when on slot B).
Click to expand...
Click to collapse
So, if I use this tool after rooting OTA updates will work and I'll still have root?
Edit: And can you explain more clearly the process on how to do this?
KedarWolf said:
So, if I use this tool after rooting OTA updates will work and I'll still have root?
Edit: And can you explain more clearly the process on how to do this?
Click to expand...
Click to collapse
No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot into fastboot and flash or boot from a patched boot image.
The steps would be:
Restore boot in the Magisk app
Restore vbmeta in Vbmeta Patcher
Take the OTA in System Updater
Patch vbmeta in Vbmeta Patcher
Patch the new boot image in the Magisk app and copy it to your computer
Reboot into fastboot
Boot from the new patched boot image
Direct Install Magisk in the Magisk App
As I noted the quote post, this process should be considered experimental until it has been more thoroughly tested. You should consider backing up any critical data before attempting it, in case something goes wrong.
I'm working on another tool to make it a bit easier to acquire the new boot image in step 5, but that will likely be a few days. Hopefully we'll be able to install Magisk to the inactive slot on Pixel devices again in the future, which would consolidate steps 5-8.
capntrips said:
I was able to take the SD1A.210817.019 to SD1A.210817.036 delta OTA via System Update by restoring my boot (via Magisk) and vbmeta (via dd) partitions back to stock, then patching vbmeta in both slots (again via dd) before rebooting. No data wipe required. To simplify that process, I made a tool to patch and restore the vbmeta partitions:
Click to expand...
Click to collapse
Patch vbmeta how? What does patching the image accomplish?
capntrips said:
On a related note, a fix that will allow Magisk to properly detect the current slot on Pixel 6 devices has been approved. Hopefully it'll get merged before the next mainline canary build, so we can stop using custom builds (or having to fastboot flash boot_b when on slot B).
Click to expand...
Click to collapse
This is good news. Would the same thing be accomplished by flashing the boot image to both slots using --slot=all?
lackalil said:
Confirmed working using Flash Tool method coming from 015 to 036. Used Magisk Alpha 23012 to patch boot image and pass SafetyNet on checker apps. GPay still doesn't work, though. It may be identifying that verity and/or verification is disabled. I don't use it, but it's generally what I confirm the SN fix with.
Click to expand...
Click to collapse
did the flash tool make you wipe when disabling verity and verification? I noticed it allows you to uncheck the wipe device option.... just curious thx
dadoc04 said:
did the flash tool make you wipe when disabling verity and verification? I noticed it allows you to uncheck the wipe device option.... just curious thx
Click to expand...
Click to collapse
If the build you're currently on has verity and verification disabled, you don't have to wipe when you update using the flash tool.
I haven't tried it without wiping from unrooted/stock vbmeta. It could well be possible despite a wipe being required when flashing using adb.