Hi,
I was trying to install the new version of Magisk 22, by patching my recovery image since Ramdisk is indicated as No in Magisk, but I can't figure out which recovery.img I should be using. I have OrangeFox 11 recovery installed, but I tried with its .img and it didn't work. My phone got encrypted, and I had to format my data thus reseting my phone in order for it to boot.
I also tried to flash the Magisk.apk file renamed as .zip but same issue, password at reboot which made me format my data partition again.
It's bugging me and I don't know what to do.
If someone can help me I would be very thankful!
U need only a recovery, flash the apk as zip. That's working
I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have
Ti64CLi++ said:
I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have
Click to expand...
Click to collapse
Then use magisk from orangefox. It's 21.4 I think
Thanks I will.
But it's still bizarre that Magisk 22.0 doesn't work on my phone
I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore
Ti64CLi++ said:
I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore
Click to expand...
Click to collapse
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737
svendsvin said:
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737
Click to expand...
Click to collapse
You too have a Redmi Note 7?
Did you manage to install Magisk 22.0 or an older version?
Thanks I will ask on the general Magisk support thread
Yes I have. I used Magisk from Orangefox first time and since updated to Magisk 22.1.
I whould suggest flashing Magisk v20.4 zip for Redmi Note 7 using OrangeFox recovery, cause this worked for me, then using the Magisk app, update it to 22.1 using the app itself, its quick and painless and also can remove force encryption. I hope it could work for you.
The required files for root are in this link (i used the same files) https://drive.google.com/drive/folders/1bpvlCnRFNQS8hIrYY5ePWS6WXfeSyt9x?usp=sharing
P.S. dont unzip anything cuz the zip file has to be flashed all together
update : the apk is deleted cuz the zip already installs it
Related
Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.
Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works
First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.
Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!
Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!
no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Code:
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script
- Found Boot Image: /dev/block/mmcblk0p58
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v14.0-zf2-20170906.zip'
Updating partition details...
...done
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Kaisogen said:
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Click to expand...
Click to collapse
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Saktis_STi said:
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Kaisogen said:
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Click to expand...
Click to collapse
Reflash newer TWRP and try again.
Saktis_STi said:
Reflash newer TWRP and try again.
Click to expand...
Click to collapse
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Kaisogen said:
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Click to expand...
Click to collapse
Try this method:
1) Flash Oreo RAW
Link: https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456 (end of the main post)
2) Boot phone until homescreen
3) Flash TWRP 3.2.1 by @planet9 (make sure you flash the latest version of TWRP)
4) Flash Magisk Beta (v 16.3)
5) Reboot
P.S: Make sure you've backed up all of your important data before flashing
With "Please restore stock boot image" the Magisk installer just want's to tell you to reflash the currently installed ROM: Simply reflash the zip of your ROM (LineageOS), then flash Magisk. No data will be lost by doing that.
The word "stock" is quite misleading here as it doesn't refer to the asus rom.
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
INSTALLATION
1.back up your system, data and boot partition. If the process fails restoring those will revert the changes.
2.Download and flash Magisk 15.3 (later versions didn't work for me, phone wouldn't boot at all) through twrp.
3.Flash the latest f2fs loop back work around.
4. Flash magisk manager for recovery (mm-2018.8.1.zip attached below)
5.Boot your phone
UPDATING TO MAGISK 16.0
Once the phone has booted:
1.install magisk manager 5.8.3 (attached below)
2.Open magisk manager
3.if any update is available for magisk manager, install it.
4.click on the button that tells you to update magisk to latest version.
IMPORTANT:
5. Select the direct installation method. Flashing the update through recovery will render the phone unable to boot again.
That's it, thanks.
=======
Downloads:
Magisk 15.3
f2fs-loopback-bug-workaround-2018.8.1.zip
mm-2018.8.1.zip
Magisk Manager v5.8.3.apk
freeZbies said:
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
....snip
Click to expand...
Click to collapse
Interesting.
For what is the magisk manager for recovery needed?
Wolfcity said:
Interesting.
For what is the magisk manager for recovery needed?
Click to expand...
Click to collapse
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
EDIT: Mm for recovery is actually a module that allows you to list and Uninstall modules from Twrp in case your phone no longer boots after flashing a module.
and you're correct, magisk 15.3 does include magisk manager and will install it. the problem I had is that I flashed magisk 15.3 over a system where either the boot.img was already patched, and I experienced that magisk manager sometimes wont be installed in these cases
Sent from my Moto G (5) using Tapatalk
freeZbies said:
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
Click to expand...
Click to collapse
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
nicolap8 said:
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
Click to expand...
Click to collapse
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
freeZbies said:
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
Click to expand...
Click to collapse
At least it's inside the official 15.3. But I remember that MM was often not installed in earlier builds.
Sent from my Moto G5 Plus using XDA Labs
I Got Another Method Also
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Sonisudhanshu said:
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Click to expand...
Click to collapse
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Sent from my Moto G (5) using Tapatalk
freeZbies said:
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Click to expand...
Click to collapse
I'm on 3.2.2.0 and it offers the ability to backup EFS, 3.2.1.0 also.
As said, for persist there are several unofficial builds but you can back it up with those commands in TWRP terminal:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
for backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
for restore.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
1. Because I didn't have any option to backup efs in twrp.32.bit
2. I was not sure but I just flashed it so that no problem occurs like booting issue..
Hope this helps
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming..... If this helped , i would be gladed
Do the magisk modules work ?
llucas_br said:
Do the magisk modules work ?
Click to expand...
Click to collapse
Which magisk module?
Sent from my Moto G5 Plus using XDA Labs
TWRP flashable Oreo 8.1 OTA updates
Sonisudhanshu said:
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming.....
Click to expand...
Click to collapse
There are already TWRP flashable Oreo 8.1 OTA updates available.
https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913
thanks
Chekm8Qc said:
I just installed magisk 17.1 and it worked right away. Even safety net passes.
Click to expand...
Click to collapse
Chekm8Qc confirmed here https://forum.xda-developers.com/showpost.php?p=77906610&postcount=56 that he could directly install the latest Magisk version (currently 17.1) on Oreo 8.1 OPP28.85-16 eliminating the need to install an older version first as recommended in this thread.
I can also confirm, installed straight away 17.1 and worked flawlessly, no bootloop and safety net passed.
Please Update!
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
G5-User7080 said:
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
Click to expand...
Click to collapse
in oreo stock you dont need f2fs bug module, because is working without it
I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.
So for some reason, my phone decided to install the new OTA update of OxygenOS.
I wanted to reinstall Magisk after flashing TWRP back but when I did so, got stuck in a bootloop.
I managed to get my phone back by re-flashing OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d3e44852.zip but everytime I try to flash Magisk, I go back on that bootloop.
What should I do ? Do I have to wait for a Magisk Update ?
Thanks
I'm glad u asked this bc my op5 keeps asking me 2 download the latest update. I want it but u don't wanna use ADB again. So how I avoid the problem above and update and keep root?
Mouchoir said:
So for some reason, my phone decided to install the new OTA update of OxygenOS.
I wanted to reinstall Magisk after flashing TWRP back but when I did so, got stuck in a bootloop.
I managed to get my phone back by re-flashing OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d3e44852.zip but everytime I try to flash Magisk, I go back on that bootloop.
What should I do ? Do I have to wait for a Magisk Update ?
Thanks
Click to expand...
Click to collapse
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What installation steps did you followed?
My oneplus 5 had a similar problem during the flash of Android 9, to fix this issue make sure that you are installing the full zip of the rom, and make sure to remove Magisk with its uninstaller before flashing the rom.
Right after the flash in the recovery it's possible to reinstall the latest version of Magisk stable. Keep in mind that without hte isntallation of Magisk you will lose the custom recovery, because the phone restore automatically its original recovery, so it's better if you flash it right after the installation of the full zip.
strongst said:
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What installation steps did you followed?
Click to expand...
Click to collapse
Thanks for your answer.
Current TWRP : twrp-3.3.1-0-cheeseburger.img (but I have to flash it back every time I go to recovery)
Current ROM : OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d 3e44852.zip
Current Magisk : None, trying to flash 20.1 (20100) ; Magisk manager 7.4.0 (253)
I think my storage is encrypted
Installation steps :
- My phone made an OTA update
- I lost root
- Downloaded Magisk 20.0 from the Magisk Manager
- I flashed TWRP twrp-3.3.1-0-cheeseburger.img via fastboot
- Flashed Magisk 20.0
- Wiped Cache/Dalvik
- Reboot
- Phone automatically turns off and opens Recovery
- Lost my TWRP, had to flash it again
- Flashed the latest OOS img found here : https://www.oneplus.com/fr/support/softwareupgrade/details?code=5
- Could turn on my phone
- Realized there's an new 20.1 Magisk version
- Tried to flash it, it failed again, flashed OOS back.
Click to expand...
Click to collapse
This is everything I did. I have access to my phone now with the OOS rom but can't install Magisk
Mouchoir said:
Thanks for your answer.
Current TWRP : twrp-3.3.1-0-cheeseburger.img (but I have to flash it back every time I go to recovery)
Current ROM : OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d 3e44852.zip
Current Magisk : None, trying to flash 20.1 (20100) ; Magisk manager 7.4.0 (253)
I think my storage is encrypted
Installation steps :
This is everything I did. I have access to my phone now with the OOS rom but can't install Magisk
Click to expand...
Click to collapse
Magisk 20 is known to have issues on pie. Also you have official twrp which has also sometimes problems.
And as mentioned already: missing to uninstall magisk can also lead to boot loops.
Recommend instructions are within the stable rom thread https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
I would try magisk uninstaller and then msgidj 19.3 in your situation as twrp won't stick without magisk.
Watch out for errors within twrp log.
Solved by running the uninstaller and reinstalling Magisk, thanks
I try everything, Try to Wipe System, Dalvnik,cache, and install latest Stable Rom, also before that I uninstall Magisk. And still BOOT loop, try also to flash form SIDELOADbut still BOOT loop.
also follow this:
Recommend instructions are within the stable rom thread https://forum.xda-developers.com/one...3/post72799040
I didnt try Clean Flash, because I have so much thigs for my job, and I can't delete it.
Can you help me to sole this problem?
djolehotsauce said:
I try everything, Try to Wipe System, Dalvnik,cache, and install latest Stable Rom, also before that I uninstall Magisk. And still BOOT loop, try also to flash form SIDELOADbut still BOOT loop.
also follow this:
Recommend instructions are within the stable rom thread https://forum.xda-developers.com/one...3/post72799040
I didnt try Clean Flash, because I have so much thigs for my job, and I can't delete it.
Can you help me to sole this problem?
Click to expand...
Click to collapse
Please answer the question same as op, maybe I can, can't promise
Your link is broken
strongst said:
Please answer the question same as op, maybe I can, can't promise
Your link is broken
Click to expand...
Click to collapse
Current TWRP : twrp-3.3.1-0-cheeseburger.img
Current ROM : OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d 3e44852.zip
Current Magisk : None, trying to flash 20.1 (20100) ; Magisk manager 7.4.0 (253)
djolehotsauce said:
Current TWRP : twrp-3.3.1-0-cheeseburger.img
Current ROM : OnePlus5Oxygen_23_OTA_052_all_1910082005_d4a454d1d 3e44852.zip
Current Magisk : None, trying to flash 20.1 (20100) ; Magisk manager 7.4.0 (253)
Click to expand...
Click to collapse
And you already followed the tips with magisk uninstaller and lower magisk version as above?
You didn't mention if your storage is encrypted or not?
The link from you to the instructions is broken.
strongst said:
And you already followed the tips with magisk uninstaller and lower magisk version as above?
You didn't mention if your storage is encrypted or not?
The link from you to the instructions is broken.
Click to expand...
Click to collapse
Yes I followed whole instruction
I think is encrypted, how I can know are they encrypted?
here is the link:
https://forum.xda-developers.com/one...3/post72799040
---------- Post added at 08:16 PM ---------- Previous post was at 08:16 PM ----------
strongst said:
And you already followed the tips with magisk uninstaller and lower magisk version as above?
You didn't mention if your storage is encrypted or not?
The link from you to the instructions is broken.
Click to expand...
Click to collapse
Yes I followed whole instruction
I think is encrypted, how I can know are they encrypted?
here is the link:
https://forum.xda-developers.com/on...-7-1-1-ota-t3627003/post72799040#post72799040