Related
How To Play Pokemon Go with Superuser (Root enabled)
Note:
IT MIGHT CAUSE BOOTLOOP OR MIGHT BRICK YOUR DEVICE. MAKE SURE YOU HAVE A BACKUP.
Requirement:
Fresh Installation of Rom or Dirty Flash of your current rom (I tested it on CM and RR- Fresh.It might work on other custom roms.)
TWRP Recovery
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
unSU Script : http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Steps:
1. Reboot into Recovery
2. Flash unSU Script and Magisk in order.
3. Reboot into System. (Mobile should boot without bootloop, otherwise you have to reinstall the ROM and try again)
4. Install Phh Superuser from here: https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en.
4. Open Magisk Manager ( Update it,if it is asked) and it will ask you for SU permission. Allow it.
6. Go to Settings and Tick " Enable Magisk Hide " and Reboot your phone.
7. Once again Magisk Manager and it will show status of SafetyNet at 3rd row and It should Passed.
Install PokemonGo and Enjoy
Credits:
@topjohnwu
@phhusson
@Hw4ng3r
@Tikerz
Updates:
8/1/17
Updated the steps with New Magsik version 10.2
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Jowhee said:
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Click to expand...
Click to collapse
This guide is for keeping root AND passing SafetyNet.
BTW, this method also works on CM13 and OOS.
It didn't mention keeping root in the title.
Jowhee said:
It didn't mention keeping root in the title.
Click to expand...
Click to collapse
Sorry for the confusion.
Updated the thread.
SafetyNet Helper fails after following the steps:
SafetyNet request: success
Response Validation: success
CTS profile match: failure
Click to expand...
Click to collapse
Do we need to go back into fastboot and disabled the bootloader unlock?
nphillips said:
SafetyNet Helper fails after following the steps:
Do we need to go back into fastboot and disabled the bootloader unlock?
Click to expand...
Click to collapse
Not necessarily. Some kernels such as blu_kernel bypass the bootloader check. Try it out.
svprm said:
How To Play Pokemon Go with Superuser (Root enabled)
Click to expand...
Click to collapse
can Xposed work along with PoGo ?
samnaction said:
can Xposed work along with PoGo ?
Click to expand...
Click to collapse
I'm not sure. I didn't test it.
But you can install the Xposed Framework module through Magisk Manager.
In CM builds you don't need all this you just need this simple app:
http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I'm gonna assume this doesn't work with CM12.1 right?
Yepi69 said:
I'm gonna assume this doesn't work with CM12.1 right?
Click to expand...
Click to collapse
I didn't try.
But you can try and post the result here that would help others.
I followed the steps in the first post and everything went OK. I'm using oxygen Os nougat 0.9
Thanks for your tutorial.
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
rdar_93 said:
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
Click to expand...
Click to collapse
Yes, cm 14.1 could pass safety net with this.
This works for sure. But if you're running a secondary ROM using MultiROM the modified boot.img will cause safetynet to indeed fail. I hope they do bring an update soon to fix this though.
Daft question, but i'm unable to use an online banking app, due to being rooted. I know this relates to PokemonGo, but wondering if this could fool the banking app?
I am using H2OS beta (Nougat) and I followed the below steps, but safety net is failing.
1. Dirty flash current ROM
2. Flash UnSU.zip
3. Flash magisk and phh zips
4. Reboot
5. Install Magisk Manager and Phh superuser
6. check safety net
Is there anything which I'm doing wrong? Can you help me please. Thank you
Edit: A reboot and everything worked fine. Thank you so much
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
topjohnwu said:
If you're using Magisk v7+ with Magisk version of phh's superuser , or rooted with Official Systemless SuperSU (Android 6.0+ only)
If you choose to use SuperSU (only support Android 6.0+)
Click to expand...
Click to collapse
So I am really wondering about your step 2 ...
svprm said:
2. Flash unSU Script, Magisk and phh's SuperUser Magisk.
Click to expand...
Click to collapse
pathologo said:
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
So I am really wondering about your step 2 ...
Click to expand...
Click to collapse
Actually i didn't try with SuperSu.So i mentioned phh's SU.
It might work with SuperSu too.
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
extra2 said:
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
Click to expand...
Click to collapse
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
just only tipp (i don't use Android Pay) - SuperSu also has a hide similar functionality - Options >> Enable Superuser []
... i'd first try it, instead of uninstall/replace
Hmmmm.... I tried to unroot in SuperSU, now my device stay stuck at the splash screen and won't boot. I'm on FreedomOS, I guess it's incompatible; just a heads up to those users.
EDIT: Nevermind, flashed the zip and all is well!
manor7777 said:
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
Click to expand...
Click to collapse
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
extra2 said:
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
Click to expand...
Click to collapse
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
manor7777 said:
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
Click to expand...
Click to collapse
Thanks, I'm gonna flash FreedomOS and do as you said. It's just you know I'm on the stock OOS and it'll be first custom ROM for this phone (yes it's again oos but anyway). I'll let you know if it (android pay) works for me
[EDIT]
Yeah dude, works great. Thanks
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk
Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep
uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.
Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?
Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.
Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.
Solved: See this post.
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
Sony Devices: If you're using stock kernel, it is using Sony's special ELF format. Magisk will repack it to standard AOSP format, which requires your device to be unlocked.
Click to expand...
Click to collapse
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?
I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.
Chamelleon said:
I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.
Click to expand...
Click to collapse
I guess you must be lucky then since Chainfire has advised Xperia users to stay on 2.79, as per the news article I linked.
Still, regardless of whether SuperSU works for some people or not, I'd still like to find out if MagiskSU is a viable alternative for Sony devices and what the correct procedure is to install it and retain all the phone's features.
Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.
Chamelleon said:
Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.
Click to expand...
Click to collapse
Possibly; can't remember to be honest. Anyway, flashing back to 2.79 fixed the boot loop and I've disabled auto-update until Chainfire says otherwise.
I still want to learn about Magisk though; not keep discussing SuperSU
I found a few bits of info on the subject:
RootKernel can apparently repack the stock kernel with a DRM fix so that all the DRM features can be restored with an unlocked bootloader.
BootBridge can install Magisk without repacking the ELF kernel in AOSP format, which the author says is preferable. However, BootBridge itself requires an unlocked bootloader so the DRM is still an issue I guess... <-- This is only meant for specific older devices; not the Z3C.
Magisk Patch claims Magisk won't work without disabling Sony RIC and provides a fix if you haven't used RootKernel already.
Trying to piece it all together is a little confusing so if anyone has actually done it, I'd be interested to hear from you.
Do we even need the SuperSU updates? 2.79 works fine for me without any issues plus the new versions are maintained by the Chinese company (I'm using some different version compiled by Chainfire himself). The only problem is the update notification in Play Store tho....
nogaff said:
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?
Click to expand...
Click to collapse
actually, i have my DRM partition and Magisk on my z3c UB. Here is what i did, first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition. oh! magisk hide works properly as well giving me full access to SafetyNet.
espaciosalter20 said:
first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition
Click to expand...
Click to collapse
I finally got a chance to try this out and I'm not having much success to be honest.
I'm starting off with an unlocked bootloader and flashing stock MM 23.5.A.1.291, then flashing TWRP.
In TWRP, the current version of Magisk (v14.0) refuses to install; it just complains about Sony ELF32 format and instructs me to use BootBridge, which is only supposed to be required for older devices like the Z2.
Anyway, I tried installing Magisk via BootBridge and it claims to have installed successfully, but then Magisk Manager says Magisk is not installed when I boot into Android (yes, I've rebooted a couple of times as well).
Next, I started over from the beginning and tried Magisk v13.3 instead, which at least begins to install, but then fails to patch the boot image.
Does anyone have a working method they could describe here?
Solution
I figured it all out by myself in the end. For anyone else having trouble, here's what I did:
Made sure I had a backup of my DRM keys!!! I already had one from when I first rooted my phone on KitKat, but I decided to make another backup using Universal TA Backup v2, just in case anything was wrong with the original.
Obtained the official Marshmallow 23.5.A.1.291 firmware from XperiFirm, created a .ftf file with Flashtool, unlocked the bootloader on my device and flashed the .ftf file via Flashtool.
Flashed TWRP custom recovery via fastboot.
Extracted the stock kernel.elf boot image from the .ftf file using Flashtool.
Ran ta_poc on the kernel.elf file, answering "Y" when prompted to disable Sony RIC*. This produced a repacked boot.img with the DRM features added back in.
Copied the boot.img to my SD card.
Booted to Android and installed the Magisk Manager apk.
Used the "Install" button in Magisk Manager and selected the boot.img on my SD card.
Noted the location of the patched_boot.img that Magisk Manager created, then booted into TWRP and flashed patched_boot.img.
Booted back into Android and checked Magisk Manager status.
My device is now fully rooted, has all the DRM features intact and is passing all SafetyNet checks.
As an alternative to steps 7-9, you could simply flash the boot.img from step 6 via TWRP and then also flash the Magisk zip file via TWRP. You'd end up with exactly the same result at step 10.
I believe you could even complete the installation without TWRP or any custom recovery at all, by using Magisk Manager to create a patched_boot.img, then copying it to your PC and flashing it via fastboot.
* Disabling Sony RIC in my boot.img was what solved all my problems. This thread suggests you don't need to do that any more, but I couldn't get it to work without doing so.
Hi, I recently installed magisk 14, I get it to work. However, somehow it broke my wifi and LTE functionality. DNS NOT FOUND. I have a m4 aqua with 6.0.1 ver.1.33. Do you have any idea what could be the cause of this problem?
Enviado desde mi E2306 mediante Tapatalk
any know magisk for Z3 Compact Docomo MM 6.1 Bootloader Lock ?
Hi nogaff,
I tried your solution but there are two difficulties I can't resolve:
1) Where can I download a valid TWRP image for the Sony Xperia Z4 Tablet? My search in the internet was without success, and TWRP doesn't seem to support this device.
2) I used the same procedure to patch the kernel:
TA_POC'd the kernel with disabling DM-verity and disabling Sony-RIC
copied this image to a SD-card
put the SD-card into my SGP771
patched this image with Magisk 22.1 (this version of Magisk supports officially my Android 7.1.1)
flashed this image using FlashTool (because I don't have a TWRP recovery for the SGP771) - flashing ended without error!
BUTThe SGP771 stucks in a boot loop!!!Can you tell me if I forgot something?
Regards
Ansgar
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
bricca said:
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
Click to expand...
Click to collapse
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
zgfg said:
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
Click to expand...
Click to collapse
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
bricca said:
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
Click to expand...
Click to collapse
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
zgfg said:
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
Click to expand...
Click to collapse
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
bricca said:
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
Click to expand...
Click to collapse
I never use the TWRP app. Read instructions from TWRP.me
You can uninstall modules. But, plz read and LEARN (it's more useful for the future how to dožisable modules from TWRP - docs I pointed you in the previous post)