Related
Thanks all - I've figured out most of these steps, 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. Since this has now become a guide, I will put it into the Guide section and this thread can be deprecated.
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.
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. 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 you should be able to download OTA packages and flash them. Will update when I care to, or others can feel free to try it and report.
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Old Post (NOT CURRENT):
I unlocked my phone some time ago, but did not install TWRP or root so that I could get OTAs. I'm currently on A2017 B25 (fully up to date) and am stock otherwise. I was hoping I could get help with updated information since the guides and threads are usually old and the reply updates can be contradictory. Two questions:
1. Can someone confirm how to take my unlocked stock A2017U B25 Axon and (1) install TWRP and (2) install Magisk?
There have been a number of threads related to installing TWRP and Magisk, but all of them have question marks. The Phh Magisk guide is from 2016 so would be pre-Nougat. Then there's also a tutorial to build your own Magisk ROM, which seems like it's more complex than other people who just flash Magisk - though for them it seems like there are still problems, with it not being clear whether Magisk 10.2 or 12 is needed.
I assume I can flash TWRP using the toolkit, but it sounds like rooting via the toolkit is not going to be Magisk. I'd really like to have a root that can pass SafetyNet if needed so my device is fully functional - if there are other methods than Magisk, that'd be great too.
2. Can someone confirm what process I use to get future stock OTAs after I install TWRP and am Magisk rooted?
Do I just download the OTA file from this thread and flash it via TWRP, or do I need to go back to stock (such as with the toolkit) first?
-------------------------------------------------------------------------------------------------
UPDATE 2017/05/21:
I came very close to solving all problems. My steps are below in case anyone wants to try.
FLASHING FROM B25 TO B19 USING EDL MODE: See my explanations here: https://forum.xda-developers.com/showpost.php?p=72294934&postcount=11
INSTALLING MAGISK 12.0 WITH ROOT AND SAFETYNET PASS
I was able to get Magisk 12.0 to run on Unlocked A2017U B19, and it appears I pass every test and Pokemon Go (test app) runs. Starting from A2017U B19 clean wipe, these are the exact steps I did. They can probably be optimized.
HOWEVER, MAGISKSU ROOT DOES NOT GIVE PERMISSION TO APPS SO THE METHOD BELOW IS NOT A SUCCESS - it says "X is denied superuser rights," without prompting. I tried all options in Magisk and could not solve this problem. If you think you can solve this problem, please feel free to give it a shot below - you will pass all status tests in Magisk but I cannot get root to actually grant access. Any suggestions?
1. Install Magisk Manager app in Google Play.
2. Boot into TWRP, flashed Magisk 10.2. Reboot. (This appears to flash successfully in TWRP, then booting back into Android it does not appear Magisk is installed in Magisk Manager).
3. In Magisk Manager, download Magisk 12.0.
4. Boot into TWRP, install/flash Magisk 12.0.
5. Boot into OS, check Magisk Manager. Magisk is shown as installed, NO root is installed.
6. Download PHH Superuser ZIP from the main post here: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 (NOTE that I cannot tell which version this is. It appears to be r170 based on the changelog, but no version appears in the "superuser.zip" that I download.)
7. Boot into TWRP, install "superuser.zip".
8. Boot into OS, check Magisk Manager. Magisk shown installed, and Superuser is shown installed. SafetyNet FAILS.
9. Enable MagiskHide in Magisk Manager settings.
10. SafetyNet should PASS in Magisk Manager.
Note that I think step 2 is unnecessary, but I kept it in anyway since that's what I did exactly. Images below show the current state of things:
{
"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"
}
Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.
I also am curious about this... having just scratched my head for like 2 hours as to why i cant boot into fastboot mode trying to install TWRP. so at this time as far as i can tell there is no way to flash twrp if you are on b25? the update packages in the EDL sub forum are all for b19
I would actually like to know which toolkit I should use to get root and keep my data on stock for A2017U
Sent from my ZTE A2017U using XDA-Developers Legacy app
B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.
StickMonster said:
B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.
Click to expand...
Click to collapse
Ok but how do i do that? which package do i download do i just put the TWRP zip file into miflash? whenever I use axon tool it tries to do it through the bootloader which of course doesnt exist anymore. also what is the deal with like 25 different miflash tools? I cant seem to find one that works for anything
That's interesting. I accidentally upgraded to B25 OTA a couple of days ago (well, not accidentally, but now I suppose that was a stupid idea). Is there a way to root the phone and unlock the bootloader now?
Cheers,
Mike
StickMonster said:
Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.
Click to expand...
Click to collapse
Thanks! I haven't had time to get around to trying it, but thinking about doing so tomorrow.
Assuming that I don't have an issue getting TWRP via the Axon Toolkit I linked to above, do I just flash Magisk 10.2 via TWRP? It seems like the process goes wrong for 50% of the people who post here, so I'm expecting some crazy process. But maybe I'm worried about nothing.
Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.
ScaryBugThing said:
Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.
Click to expand...
Click to collapse
Have you tried the TWRP app from the Play Store? Pretty straight forward.
amphi66 said:
Have you tried the TWRP app from the Play Store? Pretty straight forward.
Click to expand...
Click to collapse
Thanks for the suggestion. It turns out the Miflash method DID work. I had to extract the EDL folder, and then in the app select the subfolder for the EDL type. In detail:
1. I first installed the MiFlash at the EDL thread
2. Installed the QUALCOMM drivers linked in the same thread
3. Downloaded "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread
4. Extracted the ZIP file
5. Opened MiFlash, selected on the named sub-folder from the ZIP
6. Connected my Axon 7, and held VOL-UP/VOL-DOWN/POWER until the screen went black and the red notification LED blinked very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirmed my device was shown
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then did the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)" 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 (since it was on B25 but had the B19 TWRP partial update, which caused problems).
My problem now is that I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick? I have the option in Magisk Manager to download 12.0, but I hear that that does not work (and I don't want to have to restart this process) so I haven't tried it.
Edit: Also, Magisk Manager shows SafetyNet fails with a "CTS Profile Mismatch" error (though no SU is installed) - though Pokemon Go seems to run so I don't know what that means.
Edit 2: This is resolved, see first post.
I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.
BoboBrazil said:
I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.
Click to expand...
Click to collapse
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).
ScaryBugThing said:
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).
Click to expand...
Click to collapse
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.
ScaryBugThing said:
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.
Click to expand...
Click to collapse
I see, thanks for telling me. I'll give this a go pretty soon
Sent from my ZTE A2017U using XDA-Developers Legacy app
Sorry, in case it got lost in my old post: I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick?
If anyone can answer this, I'd really appreciate it.
With help from here: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
I am running B25 whilst keeping TWRP and a bootloader.
How? Simple really, I just took the latest B25 zip from the above link of the system and installed it without the new B25 bootstack. I guess I was running B19 before so my bootstack will be the same from there.
So that means TWRP+Unlocked bootloader, it also means I can use SuperSU to root.
Downsides:
Magisk doesn't work, tried v12,11.6,11.1,10.2 and none work, no root access.
Now I am on B25 I can't use any prior stock rom , B19 stock or bad boyz rom (based on B15?) causes me to have major problems with my gsm signal turning on and off repeatably, I tried to fix it by installing different modems but failed.
BTW this is all A2017U, no idea if it will also work with other variants.
In case anyone is wondering, I updated the first post to show that I did succeed in getting a full pass on SafetyNet with Magisk and MagiskSU/PHH SU "root" installed, and I gave the full method there.
However, all apps are denied Superuser rights with no prompt, even if the Superuser app is set to prompt or allow all. Turning off MagiskHide also fails to give Superuser, so it appears MagiskSU/PHH Superuser is simply not installing correctly.
Just for kicks I also tried flashing SuperSU 2.79. It does work as root, and gives root to apps, but of course fails SafetyNet, and Pokemon Go (test app) fails.
Hi all - I think this is solved - i.e., Magisk is fully functional. See first post which has been updated with the details.
Hi,
I would like to do the last update for the Mi A1, but without losing the root. I'm rooted with CF-Auto-Root and SuperSu is installed without TWRP. How can I do? Possible with FlashFire?
Thanks.
AFAIK it isn't possible. There is a feature in MagiskManager that lets you root the OTA update in the second slot but its not working for our device yet. The same goes for FlashFire.
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
So, I too rooted my phone using the CF-Auto-Root. I tried to unroot through SuperSU, but it didn't work. I also tried to flash the boot.img, and that didn't work either. I'm new to all of this, and I don't really know what I'm doing.
How can I actually unroot this sucker?
What do you mean by it "didn't work"? What steps have you tried? You're not supposed to flash the CFAR boot.img, instead you should use `fastboot boot boot.img` to boot into it (don't do anything after it's run, it'll automatically boot), use FlashFire to flash the zip version of SuperSU (found here http://supersu.com/download), and then reboot normally on the phone.
justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
After the full unroot, all the apps that had access for root (eg. Viper4Android, BusyBox, SELinux, etc) will working again after the update?!
http://techintouch.it
The apps will work once the system is rerooted, but you'll need to authorize the apps in SuperSU again.
Can I use the SuperSu OTA survival mode? Maybe it works?
Ok, so here's what I did.
I followed kraatus90's guide to using CF-Auto-Root. I ran the .bat executable, and I rooted my phone. Everything works. I downloaded SuperSU from the Play Store to manage the apps.
I then tried to lock the bootloader, and got the "The system was destroyed" error. So, I had to unlock it again for the phone to function.
I went into the SuperSU app and tried to do the full permanent unroot, but all I got was "Uninstallation Failed"
So, then I went to find a stock boot.img, and got one.
Now, I don't know how to reverse what I did.
I tried booting into the stock boot.img from fastboot mode, and it looked like it worked because my rooted apps spotted working, but I wasn't able to download the latest security patch.
Those are the steps I did, and I don't know how to proceed further.
EDIT 1: So, after toying around with it some more, and trying to recover the stock.img in both FlashFire, and SuperSU, and trying to flash an external stock.img through fastboot, I think I know what the problem is.
{
"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"
}
I think that the A/B partitions are what are getting me in trouble. Do I need to change the active partition through fastboot? do I need to flash something to one of the partitions through FlashFire? What can I do?
EDIT 2: So turns out, you need to use fastboot flash boot_b boot.img, and then it'll work.
Can I flash the OTA file with FlashFire without losing root? I don't have TWRP installed and I'm rooted with SuperSu.
justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
kkn14 said:
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
Click to expand...
Click to collapse
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
DeV91 said:
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
Click to expand...
Click to collapse
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
kkn14 said:
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
Click to expand...
Click to collapse
i didnt read the whole thread, but i didnt find a january oreo boot image there.
only flash a patched boot.img that is from the current build you are on.
anyway, you could try to simply boot the patched boot.img with fastboot:
fastboot boot patched_boot.img
while this may boot the system without problems, things like not being able to activate wlan could happen. because this boot image was for a different build.
however, as long as it boots the patched image, you could then simply go to magisk manager and press install direct (recommended method) - this way it will patch your stock boot image, modfying your partition directly. remember: you only "booted" the patched boot image before with the "fastboot boot" method, this will only "load" the boot.img in to memory, and will not modify your actual partition.
another way would be to just boot into twrp revovery and flash the newest magisk on your own. i'd recommend this method as you will not risk in flashing a wrong boot.img from a different build version
fastboot boot recovery.img
as long as you just boot stuff, this will only be loaded into RAM, which is a volatile memory and will be lost on a reboot - hence not modifing partitons and maintaining the possibility of taking OTAs.
My moto e4 is the USC XT1768 one.
I wanted to install magisk so I removed root with SuperSU Unroot, then tried to flash the stock boot.img and it just got stuck on the bad key screen.
so i reflashed my backup boot.img and i'm back where i started.
How can i flash the boot.img without getting stuck in the loop?
shogunreaper said:
My moto e4 is the USC XT1768 one.
I wanted to install magisk so I removed root with SuperSU Unroot, then tried to flash the stock boot.img and it just got stuck on the bad key screen.
so i reflashed my backup boot.img and i'm back where i started.
How can i flash the boot.img without getting stuck in the loop?
Click to expand...
Click to collapse
It's likely dmverity causing issues. After you flash the stock boot.img, before booting system, you could try flashing dm no verity zip.
Or better yet,when you have your system running properly, install magisk manager app. Then inside the app, use it to patch the stock boot.img. then install the magisk patched boot.img. then you will have magisk installed.
madbat99 said:
It's likely dmverity causing issues. After you flash the stock boot.img, before booting system, you could try flashing dm no verity zip.
Or better yet,when you have your system running properly, install magisk manager app. Then inside the app, use it to patch the stock boot.img. then install the magisk patched boot.img. then you will have magisk installed.
Click to expand...
Click to collapse
there are 2 advanced options, should i have both "preserve force encryption" and "preserve AVB 2.0/dm-verity" checked in advanced settings or just the first one? (that's default)
shogunreaper said:
there are 2 advanced options, should i have both "preserve force encryption" and "preserve AVB 2.0/dm-verity" checked in advanced settings or just the first one? (that's default)
Click to expand...
Click to collapse
I don't use either one. I find running encrypted with root causes issues. I usually disable dmverity and encryption, then format data in twrp (format, not wipe. To remove encryption). But you can try to keep encryption if you like. Definitely don't want to preserve dmverity.
madbat99 said:
I don't use either one. I find running encrypted with root causes issues. I usually disable dmverity and encryption, then format data in twrp (format, not wipe. To remove encryption). But you can try to keep encryption if you like. Definitely don't want to preserve dmverity.
Click to expand...
Click to collapse
alright so i patched the boot.img and then flashed it in twrp, it was able to boot successfully.
quick question, are all the things under the downloads tab compatible? Can you brick your phone by installing them?
shogunreaper said:
alright so i patched the boot.img and then flashed it in twrp, it was able to boot successfully.
quick question, are all the things under the downloads tab compatible? Can you brick your phone by installing them?
Click to expand...
Click to collapse
Magisk modules won't install on e4. It's because of the f2fs loopback bug in Moto devices. There is a fix. F2fs loopback bug workaround module. It's in the download section in magisk manager. Download it (not install) then boot to twrp and flash it there. Then you can install magisk modules. Most should be compatible. Non will brick. If one causes your phone not to boot, you can remove it. There is a magisk mount zip in magisk forum. Flashing it mounts magisk in recovery so you can remove the offending module with twrp file manager. Which ones do you want to try?
madbat99 said:
Magisk modules won't install on e4. It's because of the f2fs loopback bug in Moto devices. There is a fix. F2fs loopback bug workaround module. It's in the download section in magisk manager. Download it (not install) then boot to twrp and flash it there. Then you can install magisk modules. Most should be compatible. Non will brick. If one causes your phone not to boot, you can remove it. There is a magisk mount zip in magisk forum. Flashing it mounts magisk in recovery so you can remove the offending module with twrp file manager. Which ones do you want to try?
Click to expand...
Click to collapse
I was going to try out the sony apps enabler to start.
I seem to get "/data/magisk_merge.img mout faled..." when trying to install from inside magisk, but it works from in twrp. Is that just something i have to deal with on my device or is there a workaround?
thanks for helping.
shogunreaper said:
I was going to try out the sony apps enabler to start.
I seem to get "/data/magisk_merge.img mout faled..." when trying to install from inside magisk, but it works from in twrp. Is that just something i have to deal with on my device or is there a workaround?
thanks for helping.
Click to expand...
Click to collapse
That's the f2fs loopback bug I was talking about. Get the f2fs loopback bug workaround module from the download list. Download it (don't install in magisk manager) you have to install it in twrp. Then modules will install normally. I outlined all of that in my previous post.
madbat99 said:
That's the f2fs loopback bug I was talking about. Get the f2fs loopback bug workaround module from the download list. Download it (don't install in magisk manager) you have to install it in twrp. Then modules will install normally. I outlined all of that in my previous post.
Click to expand...
Click to collapse
i did install that, it was the first thing i did.
shogunreaper said:
i did install that, it was the first thing i did.
Click to expand...
Click to collapse
If you installed that in twrp, you should be able to install all modules normally in magisk manager. Some modules need to be updated to work properly in the latest magisk version. Some do say to flash in recovery. But if you installed the work around module, you should not get the "failed to mount" error anymore. It moves magisk to /cache, which is already mounted and ext4.
madbat99 said:
If you installed that in twrp, you should be able to install all modules normally in magisk manager. Some modules need to be updated to work properly in the latest magisk version. Some do say to flash in recovery. But if you installed the work around module, you should not get the "failed to mount" error anymore. It moves magisk to /cache, which is already mounted and ext4.
Click to expand...
Click to collapse
it's there
{
"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"
}
Where did you find the stock boot.img? I have accidentally deleted it and could do with it back...
If anybody has it then can they send it to me please?
Thanks
voxboi said:
Where did you find the stock boot.img? I have accidentally deleted it and could do with it back...
If anybody has it then can they send it to me please?
Thanks
Click to expand...
Click to collapse
You can get it from the stock firmware package
madbat99 said:
You can get it from the stock firmware package
Click to expand...
Click to collapse
Where can I find that?
voxboi said:
Where can I find that?
Click to expand...
Click to collapse
Depends on which version you have. You haven't provided any info.
All Moto firmwares are here
You need to know which version you have.
madbat99 said:
Depends on which version you have. You haven't provided any info.
You need to know which version you have.
Click to expand...
Click to collapse
I have attempted to flash the stock boot.img but when I do, nothing happens. (my boot partition is completely gone - is there any way to remake it?) I tried to flash the full zip as well but it had no META-INF so it was unflashable.
Moto E4 (woods)
SKU: XT1761
voxboi said:
I have attempted to flash the stock boot.img but when I do, nothing happens. (my boot partition is completely gone - is there any way to remake it?) I tried to flash the full zip as well but it had no META-INF so it was unflashable.
Moto E4 (woods)
SKU: XT1761
Click to expand...
Click to collapse
You can't flash a firmware package in TWRP. You have to use fastboot.
What do you mean "nothing happens"? How are you flashing it?
Flash the firmware for your specific model. There are a bunch of different versions. Flash the full firmware, it has the partition table in it.
How do you think you got rid of your boot partition? That's not likely.
Flash the firmware with fastboot. The commands are in the flashfile.xml in the firmware zip. Extract it.
Or you can use RSDlite to flash it.
What is your model (SKU) and software channel?
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms
Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio
Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
No need to wipe any partition (Dirty Flash)
[Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
Install vbmeta.imgwith TWRP by selecting vbmeta partition.
[This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Follow the below procedure to root RUI or to replace stock recovery
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to fastboot(power off device and hold vol- and power)
Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
TWRP - Download: TWRP 3.4.0-0 Thanks @mauronofrio
Code:
fastboot flash recovery twrp-3.4.0-0-RMX1931-mauronofrio.img
OrangeFox - Download: OrangeFox-R10.1 Thanks @Jerry08
Code:
fastboot flash recovery OrangeFox-R10.1_1-Unofficial-RMX1931.img
OrangeFox Recovery for realme X2 Pro - Download: OrangeFox-R11.0_1-Stable-RMX1931 Thanks @Jerry08
Code:
flash OrangeFox-R11.0_1-Stable-RMX1931.zip in custom recovery
Reboot to Custom Recovery
Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
Download: VBMETA
Flash Magisk Canary - Download to your device.
Download: Magisk Canary module[12.1 MB]
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu
[*]
{
"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"
}
Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
Download: Magisk Canary Uninstaller [2.54 MB]
Reboot to System (May take 5-7 minutes to complete booting)
New Magisk Canary app will be installed automatically in few seconds
Update Magisk Canary app
Download: Magisk Canary app [9.45 MB]
Uninstall any previous old versions of magisk
Open Magisk Canary app
Click Gear button on the Right Top Corner
Under section Manager click Hide Magisk Manager
Enter any new name of your preference
Modified Magisk manager will be installed
Under Magisk section, enable MagiskHide Toggle
Go Back to Magisk home and click shield icon present at the bottom
Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
Troubleshoot:
Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
Can follow the following instruction(s) in any order
Hold Vol+ and Power button till it restarts (more than 10 seconds)
Work in Flashboot to Flash or Wipe anything as per your requirement.
Try flashing Custom Recovery
Flash Magisk Uninstaller if issue related to Magisk
Download: Magisk Canary Uninstaller [2.54 MB]
Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.
Cool! Thanks.
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
Rj_Param said:
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
Click to expand...
Click to collapse
Install vbmeta only when you replace stock recovery with custom recovery. If custom recovery is previously installed with vbmeta, they don't need to install vbmeta again.
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
adsubzero said:
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
Click to expand...
Click to collapse
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
hack-os said:
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
Click to expand...
Click to collapse
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
adsubzero said:
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
Click to expand...
Click to collapse
Yes when you have custom recovery then you cant install ozip directly from file manager but when you click the ozip in file manager, it takes you to custom recovery if not de-bloated and its completely safe
minoccio said:
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
Click to expand...
Click to collapse
Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery
Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
nkbhr said:
Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
Click to expand...
Click to collapse
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.
hack-os said:
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.
Click to expand...
Click to collapse
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
Magisk hide keep failing
Please help
nkbhr said:
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
Click to expand...
Click to collapse
Data and system partitions enough imo
Series of the nightfall said:
Magisk hide keep failing
Please help
Click to expand...
Click to collapse
Did you enable magiskhide in settings? Check op for attached images
hack-os said:
Did you enable magiskhide in settings? Check op for attached images
Click to expand...
Click to collapse
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.
hack-os said:
Data and system partitions enough imo
Click to expand...
Click to collapse
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.
nkbhr said:
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.
Click to expand...
Click to collapse
System image should be what you need
Series of the nightfall said:
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.
Click to expand...
Click to collapse
Uninstall magisk and try everything again. If you never missed any steps and magisk hide option to rename should definitely work on devices above Android 9.
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available
A. First time rooting
{
"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"
}
This process is common across all options
A.1 Flashing Magisk patched boot imageThere are two ways to sourcing a copy of the stock boot image (other than using TWRP - See A.2).
Using the MSM Tool readback option to pull a copy of the current boot image from the phone
Using Payload Dumper and a full update zip
A.1.1 Using MSM Tool ReadBackThe MSM Tool has a feature (ReadBack) that allows it to pull copies of partitions from a phone when it is connected in EDL mode to a PC.
This means that you can pull a copy of your currently running stock boot image directly from the (unrooted) phone and you are not dependent on having access to a full rom installation zip.
A big thanks to @scottlam1 for this information (see https://forum.xda-developers.com/t/oxygenos-a12-breaks-rooting.4456251/post-87067419 and following). You can get a copy of the MSM Tool from @Some_Random_Username's https://forum.xda-developers.com/t/...ol-to-restore-your-device-to-oxygenos.4180837. I used the one for OOS 11.0.7.9 for KB05AA when testing this process.
Find your current slot by connecting your phone to your PC and running adb shell getprop ro.boot.slot_suffix Note: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device.
Start MsmDownloadTool V4.0.exe
Select User type: Others and click Next
Press F8
Select the appropriate boot partition (boot_a or boot_b based on the getprop result). Note: do NOT select both boot_a and boot_b because ReadBack will only produce one boot.img file and the _b extract will overwrite the _a extracted file.
Enter the password: oneplus and then press OK. You should now see a ReadBack button underneath the Target dropdown list.
Reboot the phone into EDL mode using adb reboot edl . When you see it connected to the MSM Tool - it will show an entry with COM3 (for example) - click on the ReadBack button.
Warning: Do NOT click on the Start button as this will start the installation process and reset your phone.
MSM will show "ReadBack Complete" (in green) when it has copied the boot image and power off the phone. Close the MSM tool.
Disconnect the phone from the PC, turn on your phone, reconnect it to the PC, and copy the boot image (it's in C:\boot.img) to your phone.
The rest of the process is the same as that in section A.1.2 below, but starting from step 6 in @DroidFreak32's guide as you already have the boot image.
A.1.2 Using Payload DumperNotes:
This can ONLY be used on full update zips, NOT on incremental updates.
Note: if you use @mslezak's Payload Dumper (see https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/ then you may be able to use it on incremental updates. I personally have not done this.
Follow the instructions detailed in @DroidFreak32's https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/ paying attention to:
You can use the latest stable version of Magisk (my recommendation as of June 2022)
Do NOT use the "To flash" option in step 11 because this causes issues when you get the next OTA update. Use the the "To Temporarily boot into a rooted system (RECOMMENDED!!)" option.
Backup both the stock boot and Magisk patched boot images if you are going to use CLI
I also recommend that on OOS you install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/).
A.2 Using TWRP or Orange FoxI will use TWRP throughout the document to mean TWRP or Orange Fox unless indicated otherwise.
I use the TWRP installer zip to create an installer for Orange Fox by replacing the recovery.img file in the TWRP installer zip with the Orange Fox recovery image (the file has to be named recovery.img). The advantage of this is that you can then flash the recovery zip in recovery as well as in Magisk (install it as a module). And the installer zip will flash recovery to both slots.
Notes:
on OOS 11 use TWRP 11 from https://dl.twrp.me/kebab/
on OOS 12 use the WIP TWRP 12 version from https://forum.xda-developers.com/t/...roject-8t-9r-2022-07-27.4473983/post-87271673 or Orange Fox from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/
on OOS 13 use Orange Fox for OOS 13 from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/ or @apophis9283's version of TWRP from https://forum.xda-developers.com/t/recovery-unofficial-twrp-oneplus-8t-oos13-1-19-23.4541965/
Boot bootloader
fastboot boot <twrp.img>
(optional - see next item) Backup current boot
Install Magisk-*.apk and note that Magisk will create a backup of the current stock boot (see section C)
Install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/)
Reboot system
Uninstall Magisk stub
Install Magisk-*.apk and in Magisk>Settings enable both Zygisk and Enforce DenyList
Reboot system
A.2.1 Keep TWRPIf you want to keep TWRP installed then the process is very similar to that described for Magisk. The difference is that this time we backup recovery and install TWRP. You can merge the Magisk process with the TWRP process by: Backing up current boot and recovery; Installing both the Magisk-*.apk and the TWRP installer zip.
Here's the process for just TWRP:
Boot bootloader
fastboot boot <twrp.img>
Backup current recovery
Note: the TWRP backups of physical partitions (like boot and recovery and so on) are actually image dumps. You could rename the files from *.emmc.win to *.img and install them using TWRP or other methods.
Install TWRP installer zip
Reboot system
B. Keeping root during an update
B.1 System Update downloads and installs the updateThis is using the built-in System Update tool, which you'll find in:
OOS 11: Settings>System settings> System Update
OOS 12 and higher: Settings>About device>Software update
The process is complicated because you cannot use Magisk>Magisk Install>"Install to inactive slot" as this will fail on OOS 11 (for incremental updates) and OOS 12 (for all updates, including the initial update from OOS 11 to OOS 12).
But testing on OOS 13 (updating from F.62 to F.63 on KB2003 and KB2005) shows that you can now use "Install to inactive slot" and, therefore, the simpler B.1.2 process can be used with System Updater for both incremental and full OTA updates. However this needs more testing (by adventurous IN users).
B.1.1 SafeThe following process is safe to use on all versions and types of OTA updates. It is courtesy of @osm0sis in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713 and @rage302 in https://forum.xda-developers.com/t/...ing-root-options.4387977/page-4#post-86830285.
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
Download and Install the update (and DO NOT reboot) using:
OOS 11: Settings>System Settings>System Update>Download and Install
OOS 12 and higher: Settings>About device>Software update
Copy the updated boot image as follows:
On PC:Find the inactive slot suffix:
adb shell getprop ro.boot.slot_suffix Note: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device.
If the result is _a then the inactive slot suffix is _b otherwise it is _a
Take a copy of the inactive slot boot image: adb shell su -c dd if=/dev/block/by-name/boot<inactive slot suffix> of=/sdcard/oos-ota-boot.img replacing <inactive slot suffix> with the value you previously determined (_a or _b). Note: Magisk may prompt you (on your phone) to grant root access to Shell - grant it.
On phone: Patch the dumped oos-ota-boot.img using Magisk>Magisk Install>"Select and Patch a File"
Copy /sdcard/Download/magisk_patched*.img to your PC
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Turn on Airplane Mode to prevent Google Play Services detecting that the phone is bootloader unlocked and making your phone uncertified in Google Play.
Reboot the phone from the System Update dialog; verify that you are now running the updated version
On PC: Reboot to bootloader using adb reboot bootloader
Boot (NOT flash) the patched boot image: fastboot boot <magisk-patched image> where <magisk-patched image> is the patched image you transferred to the PC
On phone: Verify that Magisk shows you are rooted
Make rooting permanent using Magisk>Magisk Install>"Direct Install (Recommended)" and reboot again
Turn off Airplane Mode
B.1.2 SimpleThe following process is the simplest update method, but is limited to:
OOS 11 full image OTAs only
OOS 13+ full image OTAs and, starting with C.62, incremental OTAs (confirmed for KB2003 and KB2005)
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
Download and Install the update (and DO NOT reboot) using:
OOS 11: Settings>System Settings>System Update>Download and Install
OOS 13+: Settings>About device>Software update
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it and it is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting, leaving you without root.
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 reboot.
To re-install TWRP, follow the process in A.2.1
B.2 Manual InstallThis involves manually downloading the update zip and then installing it using one of the following options.
It is up to you to download the update (from whichever source you use).
How to get a copy of the update zip
The simplest option is to use Oxygen Updater (https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater).
It is also possible to get a copy of the update zip if the OOS 13+ System Updater is showing that an update is available and the installation button is showing "Extract".
You'll find the installation zip (named my_manifest_*_patch.zip or my_manifest_*_all.zip for incremental or full OTA) in /data/ota_package/OTA/.otaPackage.
B.2.1 Local InstallThis is using:
OOS 11: System Update>Gear icon (local install)
OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
OOS 13+: On EU and IN Settings>About device>Software update>3-dot menu>Local install; on NA: same as for OOS 12
Note: If the Local install option is greyed out because the System Updater is showing that an update is available, then you can still use Local install by:
Turn on Airplane mode to prevent the System Updater finding the update again after the next step.
Go to Settings>Apps>App Management>3-dot menu>Show system and clear storage from Software update
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Move the update zip to /sdcard (NOT a subdirectory of /sdcard).
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk.
Install the update using the appropriate local installer for your version of OOS and DO NOT reboot.
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it and it is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting, leaving you without root.
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 and 12 reboot.
To re-install TWRP, follow the process in A.2.1
B.2.2 Using CLICLI (command line interface) tools, such as Terminal (I use Termux from https://f-droid.org/en/packages/com.termux/) or ADB shell, allows you to manually download delta updates avoiding the need to wait for full updates or for someone to post a copy of the delta update zip.
If you use Terminal then you can install updates without the need of a PC (my preferred option).
Using line commands, at one level, can simplify some processes by avoiding the need to switch out to recovery and back again. On the other hand, they complicate things by requiring knowledge of how to use them.
The commands you need to be familiar with are:
dd to read-from/write-to the partitions in /dev/block/by-name
grep to scan the output of a logcat
getprop to find out which are the active/inactive slots
logcat to read the Android logs
su to run commands as root
Get a copy of the update zip
Note: I'm running the NA version of OOS. If the URL below for the OTA is different for other OOS versions, please let me know via a PM.
Once the phone tells me that there's an update available I do the following in Termux:
su -c "logcat -d" | grep -Eo "https://android.googleapis.com/packages/ota-api/package/[a-z0-9]*.zip"
This looks for the the Google OTA server file name in logcat and returns the source address. For example, the KB2005 C.11 incremental update was https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Note: You should run these commands as soon as you get a notification that you have the update. If you leave it too long then the log file will roll over and you won't be able find the url.
wget -O /sdcard/oos-ota-update.zip <source address>
This pulls a copy of the file to /sdcard
Note: You could also just paste the URL into a browser to download the file
Find the active slot suffix: getprop ro.boot.slot_suffix
If the result is _a then the inactive slot suffix is _b otherwise it is _a
Restore active slot stock boot/recovery (recovery: only if TWRP is installed) using dd if=<copy of stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>
Note: you could also use Magisk to restore the stock boot using Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update using the appropriate local installer for your version of OOS and DO NOT reboot
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it. It is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting leaving you without root.
The local installer is:
OOS 11: System Update>Gear icon (local install)
OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
OOS 13+: On EU and IN Settings>About device>Software update>3-dot menu>Local install; to be advised on NA
Backup the new inactive slot stock boot/recovery (recovery: only if TWRP is installed) using dd if=/dev/block/by-name/<boot/recovery><inactive slot suffix> of=<new boot/recovery img>
Restore root to the current active slot dd if=<copy of current Magisk patched stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>. This is so you keep root in case the update somehow fails and you're returned to the current system.
Note: You could also use Magisk>Magisk Install>"Direct Install (Recommended)"
(ONLY if keeping TWRP) Magisk>Modules>Install from storage: Select <twrp-installer.zip>
Magisk>Magisk Install>"Install to inactive slot" and DO NOT reboot
Backup the new Magisk patched stock boot using dd if=/dev/block/by-name/<boot><inactive slot suffix> of=<new Magisk patched boot img>
On OOS 11 and 12: Reboot. On OOS 13+ now tap on Install in the local installer to finish the installation.
C. A note on Magisk backup folders in /dataWhen Magisk patches a stock boot image using either Magisk>Magisk Install>"Direct Install (Recommended)", Magisk>Magisk Install>"Install to inactive slot", or is installed in TWRP, then it creates a backup of the stock boot image in a directory named /data/magisk_backup_<SHA1 of stock image>.
When you use Magisk>Uninstall Magisk>Restore images the backup corresponding to the current patched boot image is used to restore the stock image to the current (active) slot.
Clearly, if you deleted these magisk_backup directories then Magisk will not be able to restore the stock boot image. You must, therefore, always keep the current backup.
If you don't delete these backups you can end up with a lot of obsolete backups. So, how to work out which one is the one you need to keep?
The simplest way is to:
Restore the current stock boot image using Magisk>Uninstall Magisk>Restore images
Delete all the /data/magisk_backup_* directories
Restore the rooted boot image using Magisk>Magisk Install>"Direct Install (Recommended)" - this also creates a new magisk_backup directory (no need to reboot)
Great write up. I know some people will appreciate the info when they have that "freak out moment" and something goes slightly wrong.
My question/suggestion would be in regards to your A.2 step. But please, if both options work, my post can be ignored. As you and I discussed in another thread, the update process via TWRP while keeping root has always been, on previous OnePlus Android OS versions.
Download full ROM zip from OnePlus or other available location. I.E. 11.0.12.12
Create Nandroid backup.
Install full ROM zip.
Install TWRP.
Reboot to recovery.
Install Magisk.
Reboot to system.
Assuming it's a full update and not a delta. You outlined...
Manually download the update (from whichever source you use)
Boot recovery
Restore the stock boot and recovery that you backed up previously
Install the update
Boot bootloader
fastboot boot <twrp.img>
Backup current boot and recovery
Install Magisk-*.apk
Install twrp-installer.zip
Reboot system
As you stated, if full update, skip steps 3, 5, 6. Does changing the order and installing Magisk before TWRP allow you to not install TWRP 2x in order to keep the recovery and preserve root?
I used my outlined steps to update to 11.0.12.12 and it worked perfectly. Sorry if this post seems out of sorts, I'm doing it from my phone.
The Apostle said:
Great write up. I know some people will appreciate the info when they have that "freak out moment" and something goes slightly wrong.
My question/suggestion would be in regards to your A.2 step. But please, if both options work, my post can be ignored. As you and I discussed in another thread, the update process via TWRP while keeping root has always been, on previous OnePlus Android OS versions.
Download full ROM zip from OnePlus or other available location. I.E. 11.0.12.12
Create Nandroid backup.
Install full ROM zip.
Install TWRP.
Reboot to recovery.
Install Magisk.
Reboot to system.
Assuming it's a full update and not a delta. You outlined...
Manually download the update (from whichever source you use)
Boot recovery
Restore the stock boot and recovery that you backed up previously
Install the update
Boot bootloader
fastboot boot <twrp.img>
Backup current boot and recovery
Install Magisk-*.apk
Install twrp-installer.zip
Reboot system
As you stated, if full update, skip steps 3, 5, 6. Does changing the order and installing Magisk before TWRP allow you to not install TWRP 2x in order to keep the recovery and preserve root?
I used my outlined steps to update to 11.0.12.12 and it worked perfectly. Sorry if this post seems out of sorts, I'm doing it from my phone.
Click to expand...
Click to collapse
The problem is that delta updates require you to restore both recovery and boot partitions to stock otherwise the installation fails.
The process I describe works for both full and delta updates. But, like I said, if you know that the update is a full OTA, then you can simplify the process and, <edit>if you know it's always going to be a full update, then<end-edit> you can use your "usual" process.
PS: this is a source of confusion because the BA ROMs are always full updates, while the AA ROMs are typically delta updates.
So what works for one user will not work for another even though they are both running OOS on an 8T.
And then there's the difference between letting System update download and install versus manual install, which creates another place for confusion is you just talk about "install update" instead of being specific as to the exact method.
BillGoss said:
The problem is that delta updates require you to restore both recovery and boot partitions to stock otherwise the installation fails.
The process I describe works for both full and delta updates. But, like I said, if you know that the update is a full OTA, then you can simplify the process as per your "usual" process.
Click to expand...
Click to collapse
I guess I don't know why people wouldn't simplify the process, download the full ROM, and eliminate steps. It's worked for years on OnePlus devices across android 9, 10, and now 11.
The Apostle said:
I guess I don't know why people wouldn't simplify the process, download the full ROM, and eliminate steps. It's worked for years on OnePlus devices across android 9, 10, and now 11.
Click to expand...
Click to collapse
Because there's often no AA full rom to download. They can take months to show up while the delta is available immediately from Google.
I've never had that issue. Between XDA and OnePlus forums, someone has always posted a host link... Since OnePlus stopped around October.
Regardless, good info you posted.
The Apostle said:
I've never had that issue. Between XDA and OnePlus forums, someone has always posted a host link... Since OnePlus stopped around October.
Regardless, good info you posted.
Click to expand...
Click to collapse
Thanks. By the way I edited my first reply to you because your "usual" process only works if you are always using full updates.
Hi!
I'm using this method for the update:
Without TWRP
Manually download the update (from whichever source you use) to /sdcard
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update in System Update>Gear icon (local install)
Magisk>Magisk Install>Install to inactive slot
Reboot system
2nd point, if I tap on uninstall magisk, It tells me that I don't have a backup original boot image, how can I proced?
Thanks
Feduz said:
Hi!
I'm using this method for the update:
Without TWRP
Manually download the update (from whichever source you use) to /sdcard
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update in System Update>Gear icon (local install)
Magisk>Magisk Install>Install to inactive slot
Reboot system
2nd point, if I tap on uninstall magisk, It tells me that I don't have a backup original boot image, how can I proced?
Thanks
Click to expand...
Click to collapse
You can't proceed if your update is an incremental update. Otherwise you can go ahead.
You'll need to find a copy of the stock boot image to restore it before installing the incremental update.
BillGoss said:
You can't proceed if your update is an incremental update. Otherwise you can go ahead.
You'll need to find a copy of the stock boot image to restore it before installing the incremental update.
Click to expand...
Click to collapse
I'm on 11.0.11.11KB05BA, to 11.0.12.12. so I need to flash the original boot image via ADB/fastboot? Then proceed with point 3?
Feduz said:
I'm on 11.0.11.11KB05BA, to 11.0.12.12. so I need to flash the original boot image via ADB/fastboot? Then proceed with point 3?
Click to expand...
Click to collapse
You tell me. I use AA, not BA. If you don't know what type of update it is, then you need to replace stock using whatever method you like.
BillGoss said:
You tell me. I use AA, not BA. If you don't know what type of update it is, then you need to replace stock using whatever method you like.
Click to expand...
Click to collapse
It's a full update, about 2.8 GB. I'll flash the stock boot.img so
Feduz said:
It's a full update, about 2.8 GB. I'll flash the stock boot.img so
Click to expand...
Click to collapse
if it is a full update you don't need to restore anything before installing it.
Qnorsten said:
if it is a full update you don't need to restore anything before installing it.
Click to expand...
Click to collapse
Correct, I skipped this part in the first post. I've done the update and then installed via magisk. All went good. Thanks
What should I backup using TWRP before a custom rom update and before a jump from a custom rom to another?
rmroot said:
What should I backup using TWRP before a custom rom update and before a jump from a custom rom to another?
Click to expand...
Click to collapse
Read the TWRP OP posts for the answer.
[CLOSED] [No longer maintained] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (8T / Kebab) (2022-03-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
@BillGoss
I will be a user of an OP 9R in a few days and I saw that it shares the same version of TWRP.
In the 9r forum I still haven't found a well explained tutorial and if it's possible.
The instructions you put here allow you to update OxygenOS on 8T and keep root/TWRP, right? Would they be applicable to the 9R as well?
lvints said:
@BillGoss
I will be a user of an OP 9R in a few days and I saw that it shares the same version of TWRP.
In the 9r forum I still haven't found a well explained tutorial and if it's possible.
The instructions you put here allow you to update OxygenOS on 8T and keep root/TWRP, right? Would they be applicable to the 9R as well?
Click to expand...
Click to collapse
I know that the 8T and 9R share similar architecture so the process I've described may work on the 9R, but I can't confirm this.
I do know that as one point we had a common TWRP version for both the 8T and 9R, but that's no longer the case and there's no official TWRP for the 9R.
So, from my perspective, you're on your own on this. If it works, great. You may want to post your process and results in the 9R forum, but not here (this is strictly an 8T forum and thread).
Thanks very much for this thread, @BillGoss. Just easily upgraded 11.0.12.12.KB05AA to 11.0.13.13.KB05AA with your methods using fastboot boot trwp.xx.img from bootloader mode and simply reinstalling Magisk after letting the update run (airplane mode on, as you suggest). I had just upgraded Magisk before the update, so had the latest apk handy in my downloads.
To backup your boot in TWRP (first know your active slot), you can get to a terminal in the TWRP/Advanced menu. I use the same commands you list in your "Use a CLI" instructions.
Hi, I've updated correctly to the latest OOS, should I need to update Magisk? or will be fine this version?