Related
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
Use this guide to install OTAs manually in case you haven't received the update yet or you are bootloader unlocked/rooted.
1.) Download the corresponding OTA package from the links posted here by @mickey36736 - https://forum.xda-developers.com/zenfone-5z/how-to/zs620kl-fota-update-links-update-20-08-t3831794.
2.) Rename it in the format UL-Z01R-WW-{version number}-user.zip (excluding the braces).
3.) Drop it in the root of your internal storage and reboot.
4.) You should see the update notification once the phone boots up.
5.) Start the update (or) in case you are rooted using Magisk and want to preserve root, skip to step 6.
6.) Open Magisk Manager and select Uninstall > Restore Images
7.) Start the update.
8.) Once the update is done, don't reboot yet. Open Magisk Manager and select Install > Install to inactive slot (after OTA).
9.) Once the installation is done, reboot.
Note: Make sure 'Preserve AVB 2.0/dm-verity' is checked in Magisk Manager and you didn't flash vbmeta with the disable verity and disable verification flags, or the OTA won't install.
Pie is here peeps
https://forum.xda-developers.com/zenfone-5z/how-to/zs620kl-fota-update-links-update-20-08-t3831794
If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"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"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.
Perfect manual and working great
gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!
Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?
Yes if you are offered the aa rom in the updater
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk
SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.
hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.
The 1+ updater has a setting to auto download updates or not. You can change it.
If we have TWRP installed could we get a guide for using the updater app?
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).
i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)
Hey everyone, sorry if this has been covered already but I don't recall seeing these instructions anywhere. After doing the standard tethered re-root every time there was an OTA update I discovered that you don't need to tether. I've been doing it this way for the past several updates and it has worked perfectly every time. Not sure if this will work for major version updates though. As usual, YMMV, back up your data, I'm not responsible for data loss, bricks, etc. etc.
Install TWRP and Magisk the usual tethered way the first time you root. There's no way around this.
When an OTA update comes out, allow it to download but do not let it install itself.
Download the latest TWRP Fajita zip to your device if you don't already have it. https://dl.twrp.me/fajita/
Reboot to recovery and decrypt if necessary.
Back up your data if you don't feel like living on the edge.
Hit the install button and browse to /sdcard/.Ota and select the latest zip, which was downloaded automatically earlier.
Tap the button to add another zip, and select the TWRP zip that you downloaded earlier.
Swipe to install, reboot when done. It is crucial to install both zips without rebooting in between, otherwise you'll have to tether.
After the post-boot update process completes, open the Magisk Manager app and hit the Install button for Magisk (not Magisk Manager). Choose to download zip only.
Reboot to recovery and decrypt if necessary.
Hit the install button and browse to /sdcard/Download and select the Magisk zip that you just downloaded. Swipe to install, then reboot.
Magisk app should now show Magisk is installed again.
Profit.
If we have twrp retention script we simply can retain magisk and twrp, i think everyone knows that
what is the twrp retention script? have you a link?
Hey Guys,
I don't found any similar thread about this topic, so I will create a new.
I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image -> Download OTA -> Install OTA -> Install to inactive Slot in magisk.
But on Android 12 it downloads the OTA, then it extract and verify it. After Clicking on Install it will reboot directly. Does someone know how I do the OTA Updates on Android 12 correct?
Many thanks!
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
This behavior is kind of weird from the OnePlus but I probably understand it. Anyway it will be better to offer full OTA straight forward. System can decide whether it's needed or not I think?
Anyway i reinstalled Magisk via fastboot when this happened.
Once twrp is available, there won't be those issues I assume.
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
Thank you very much! I will try this for the next update
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?
paper88 said:
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?
Click to expand...
Click to collapse
Yes, you can. When the button to install now appears in the automatic update of the system, switch to magisk and install it to inactive Slot, then return to the system update, click the button to install now, and the phone will restart automatically. Remember not to click restart on the magisk interface
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
Do you know if this is also a possible way for the C.20 Update of Android 13? Would be helpful if someone tested this already