I woke up today to a prompt to upgrade Magisk Manager to 7.3.5, and Magisk to v20. v20 is the one that adds support for Android 10 and complete changes how system_as_root works (which made me nervous).
I was running Magisk v19.3, having never been prompted to install v19.4.
I'm here to report that both install just fine. I have a bunch of modules installed: busybox, debloater, f-droid, magisk manager recovery, riru, edxposed, tzdata. I can't tell if it's using "compat mode" or not. I guess that depends on the specific modules you've got?
I created a new patched_boot for 10.0.14.0 with Magisk v20 (not sure if this is necessary for re-patching now that 19.3 is not current). https://yasmar.net/xda/patched_boot_10.0.14.0_20.img.gz
I'm using it on cr driod works well
on what rom are you running this? i am on 10 gsi rom from here and in v19 riru and edexposed gave me bootloops no mather what i did
Using it on latest stock, no problems so far
loop4444 said:
on what rom are you running this?
Click to expand...
Click to collapse
Stock 10.0.14.0
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.
a1291762 said:
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.
Click to expand...
Click to collapse
And it's back. Stupid mobile network blacklisting me for rebooting
Coincidentally, my TWRP is dead so I'll need to put that back when I get home. Probably affected by the Magisk upgrade.
After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).
a1291762 said:
After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).
Click to expand...
Click to collapse
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'
yashinodon said:
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'
Click to expand...
Click to collapse
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
Right, thanks for the info.
Haven't tried Magisk 20 yet, I still use 18.1. Maybe we need an updated TWRP, but since 33bca aka offain left this device I don't have high hopes...
yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
When you see "your system has been destroyed " ,it's most likely conflict between magisk and some module , the easiest fix is to 1.boot to twrp via PC , use magisk manager for recovery. zip and disable all modules.
2. if your recovery says :data is encrypted -flash different kernel , that will disable magisk , reboot to recovery , use magisk manager for recovery , disable all modules and flash magisk again .
In both of the cases you won't need to reflash stock rom every time you see that message , if you want to use twrp again
P. S. BTW , there is an 20.1version of magisk and magisk manager 7.3.6 already
Related
So, i just updated Magisk to 14.0. After rebooting, my phone gets stuck just before the lockscreen appears, then it automatically reboots to the recovery menu. Here i can only download a new stock rom, reboot (which goes the same way), and shutdown. Now, i would like to boot in TWRP and uninstall Magisk, but i have USB debugging disabled, so i don't know if i can access TWRP and run the uninstaller from SD.
Is there anyway i can get out of this situation without the dload method and therefore wiping my internal memory ? I have most of it backupped, but some important files i spent weeks getting are still there.
Ok, i resolved it. To fix this you can go into TWRP (pressing Power+Volume Up before the screen turns on and Up until you enter recovery) and apply the Magisk Uninstaller (it does not need a boot image to work). Hopefully this will help anyone who had this problem.
The best version of magisk yet is v13.3
mine just updated to 14.0 without any problem , i use direct update from app.
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Magisk 14, no issues here either. Stock rooted L04.
stuckoutside said:
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Click to expand...
Click to collapse
Glad it was fixed.sometimes same things work for few but not for others. Thats wiered but still fact remains the same
stuckoutside said:
That"s what i did, too. Apparently after uninstalling i had lost root. I flashed the latest SuperSU, which caused another bootloop like the first one. To fix this one i flashed UnSU (which did nothing) and then SuperSU again (but root wasn't there)
Click to expand...
Click to collapse
Try magisk 14.0 directly not from 13.3 , but mine is smoothly worked from 13.3.
venugopalu007 said:
Try magisk 14.0 directly not from 13.3 , but mine is smoothly worked from 13.3.
Click to expand...
Click to collapse
These are weird issues. Works for one but not for others.
Strange
You can report this to the Magisk support thread.
Sent from my DUK-L09 using XDA Labs
So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?
OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.
Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.
FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: twrp-3.3.1-1-guacamoleb.img (from https://twrp.me/oneplus/oneplus7.html)
Magisk: problem started with v19.1 but repeated itself with v20.0
UPDATE: I've found someone else with the same problem https://github.com/topjohnwu/Magisk/issues/1920
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Try to enter TWRP from recovery but boots to stock recovery
Can anyone help me? The feature I need the most is a full system backup
ColOfAbRiX said:
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: 3.3.1-1-guacamoleb
Magisk: 20.0
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Install MagiskHide
5) Try to enter TWRP from recovery. Doesn't work.
Can anyone help me? The feature I need the most is a full system backup
Click to expand...
Click to collapse
Hello,
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Please use Magisk 19.3 on your pie rom.
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Hi!
strongst said:
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Click to expand...
Click to collapse
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
strongst said:
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Click to expand...
Click to collapse
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
strongst said:
Please use Magisk 19.3 on your pie rom.
Click to expand...
Click to collapse
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
ColOfAbRiX said:
Hi!
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
Click to expand...
Click to collapse
Thanks for the update!
Yes, please use the twrp from mauronofrio, it's unified for OP7 and OP7 Pro (check file name like twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip)and and 19.3 magisk.
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
ColOfAbRiX said:
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
Click to expand...
Click to collapse
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
Really? I have the problem with Magisk version 19.3
strongst said:
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
Click to expand...
Click to collapse
I tried to use 19.3 and nothing.
ColOfAbRiX said:
Really? I have the problem with Magisk version 19.3
Click to expand...
Click to collapse
Hmm, really strange, with 19.4?
lvints said:
I tried to use 19.3 and nothing.
Click to expand...
Click to collapse
Something prevents twrp to stick from magisk side
strongst said:
Hmm, really strange, with 19.4?
Something prevents twrp to stick from magisk side
Click to expand...
Click to collapse
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
lvints said:
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
Click to expand...
Click to collapse
Sorry, I'm out of ideas at the moment...
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
ColOfAbRiX said:
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
Click to expand...
Click to collapse
I'm sad about what happened to you, friend
If you can find a solution put the topic.
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
lvints said:
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
Click to expand...
Click to collapse
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
See other thread(cross posting) https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
@strongst
Do you think it's best to answer this topic or the other?
lvints said:
@strongst
Do you think it's best to answer this topic or the other?
Click to expand...
Click to collapse
Where the discussion starts
Otherwise you'll lost the line when switching between threads.
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
I have the same problem as yours. I've tried countless scenarios, followed tutorials on XDA and Youtoube but can't make TWRP work.
Out of curiosity I restarted the device through slot A after flash zip from magisk. My phone has accessed TWRP, but I cannot access my files. When I restart from slot B I have the opposite. Twrp doesn't work, but my files are accessible.
So I believe I somehow "broke" slot A. I just don't know how I did it or how to fix it.
EDIT: Please refer to my other thread here.
thanks
how to flash via fasboot ?
---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------
thanks
how to flash via fasboot ?
SHAY820 said:
thanks
how to flash via fasboot ?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img
Testing now to see if this worked. Thanks OP!
---------- Post added at 20:31 ---------- Previous post was at 20:30 ----------
remewer said:
Here are the stock and Magisk patched boot images:
Android 10 OB1:
http://www.mediafire.com/folder/2ffhwvqplh9ui/OnePlus_6_OOS_OB1
Flash using fastboot.
Click to expand...
Click to collapse
Worked perfectly using the command:
Code:
fastboot flash boot magisk_patched.img
Thank you!!!
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Does it not work for OB2?
bright2541 said:
Does it not work for OB2?
Click to expand...
Click to collapse
Which OB2 are you talking about?
Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
I think it's impossible without TWRP, unless you do a data wipe.
Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
I was in the same situation and can confirm flashing the stock boot.img recovered from bootloop. Now to wait for compatible TWRP
alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
Flashing the stock boot runs the system but so I'm not magisk so I'm not the root. I'm just trying to remove the magisk modules to prevent it from installing when I flash the boot patched because if I let it bootloop
Hello!!
Thank for your work.
Work perfect with conmand fastboot flash boot magisk_patched.img, and after instal magisk manager
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
There's no way. Unless you flash stock boot image, then factory reset, which will remove all traces of Magisk.
vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
Try to flash back to the same build you just came from, at this point it's try or lose everything anyways. Flash last version you had installed along with whatever twrp/magisk you had.
---------- Post added at 06:26 AM ---------- Previous post was at 06:04 AM ----------
Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
Have you tried fastboot to change the slot you are booting to? If not you can try using this command in adb
fastboot set_active b
If that does not work try switching to slot a
fastboot set_active a
If you get an error you may need to update your SDK tools. Here is the link to the latest updates
https://developer.android.com/studio/releases/platform-tools
This is for OnePlus 6 with Android 10 beta 1 of 19/10/2019 ?
Will flashing this wipe my phone? and will I still be able to update to future OTAs?
whone99 said:
Will flashing this wipe my phone? and will I still be able to update to future OTAs?
Click to expand...
Click to collapse
No, it won't wipe your phone. Yes, you'll still be able to update, but it will download the whole update, not increment since your bootloader is unlocked.
Flashing this magisk patched doesn't work for me. It's true, i didn't erase anything from magisk when i upgraded, might need to do a autumn cleaning
Until then, winter is coming and i will wait for a working solution.
Does it is work on OP6_o2_Beta 30?
I also have magisk installed and vanced, so it's time to wait for a solution to come out.
Chrome reports virus !!!
After install newest Magisk,Force-encryption disabler,I met bootloop. (Test in android 9 pie,sovled after using Magisk 19.3 and Disabler 08.18.2019)
Twrp for Motorola g6 : https://twrp.me/motorola/motorolamotog6.html
Magisk 19.3 : https://github.com/topjohnwu/Magisk/releases
Disable_Dm-Verity_ForceEncry_08.18.2019 : https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Follow this step by d412:
Flash twrp, hit cancel when prompted for password
Wipe>Format data>type yes
do not hit reboot system, Hit the back button multiple times until main menu
Go to reboot tab, click reboot recovery
Wipe>format data>type yes
do not hit reboot system, hit the back button until main menu
Reboot tab> click reboot > click recovery
TWRP reboots > Install tab
select Universal DM verity
Swipe to install, wait for it to finish
Backbutton
Select Magisk, swipe to install, you're done
My ROM Version PPSS29.55-37-4-5,twrp 3.3.1-0 Ali official,Universal DM-Verity, ForceEncrypt 10/20/ 2019,magisk v20.1 stable
Use magisk 19.3 and the August version of the disabler, newest won't work
Jemec26 said:
Use magisk 19.3 and the August version of the disabler, newest won't work
Click to expand...
Click to collapse
Thanks a lot. It works for me.
Deleted
chaningbox said:
Yes,it works for me,but the system get slow I don't know why,so I flash the stock rom again.
Click to expand...
Click to collapse
If you will be rooted, at least for me, it is better to install any Android 9 gsi that are very stable and not stock. This device has issues when it comes to root and stock rom.
Jemec26 said:
Use magisk 19.3 and the August version of the disabler, newest won't work
Click to expand...
Click to collapse
Which august version? There are two; one from early august, and a mid-month update.
Johnny_Wishbone said:
Which august version? There are two; one from early august, and a mid-month update.
Click to expand...
Click to collapse
Mid month
Johnny_Wishbone said:
Which august version? There are two; one from early august, and a mid-month update.
Click to expand...
Click to collapse
Can you please post links for the version of disabler you are using?
After few trial and error.
Flash TWRP and boot from there.
Flash Magisk 19.3 (DO NOT flash 20 or it will boot loop)
Reboot and open Magisk Manager and install 20.1 from there
That's it
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
saishash_09 said:
Can you please post links for the version of disabler you are using?
Click to expand...
Click to collapse
Actually, you just install Magisk 19.3 in TWRP and it disables verity for you
mingkee said:
After few trial and error.
Flash TWRP and boot from there.
Flash Magisk 19.3 (DO NOT flash 20 or it will boot loop)
Reboot and open Magisk Manager and install 20.1 from there
That's it
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Actually, you just install Magisk 19.3 in TWRP and it disables verity for you
Click to expand...
Click to collapse
Why my system get slow after install disabler and magisk
saishash_09 said:
Can you please post links for the version of disabler you are using?
Click to expand...
Click to collapse
Updated download link
Greetings. I have made the mistake of doing what this post says not to do. So I have the dreaded bootloop. I did try reflashing from TWRP the links from this post but to no avail. Anyone know what to do once you have already encountered the bootloop? Thank you.
DarkQuark said:
Greetings. I have made the mistake of doing what this post says not to do. So I have the dreaded bootloop. I did try reflashing from TWRP the links from this post but to no avail. Anyone know what to do once you have already encountered the bootloop? Thank you.
Click to expand...
Click to collapse
For anyone having this same problem (caught in the boot loop) I used RSDlite and resent the latest retail firmware back to the phone. Then I had to put TWRP back and of course then ran the aforementioned versions of Magisk and the DM-verity script. After that everything was good. Pro-tip, to get RSDlite to work I had to use a Win7 VM. It did not like Win10.
DarkQuark said:
For anyone having this same problem (caught in the boot loop) I used RSDlite and resent the latest retail firmware back to the phone. Then I had to put TWRP back and of course then ran the aforementioned versions of Magisk and the DM-verity script. After that everything was good. Pro-tip, to get RSDlite to work I had to use a Win7 VM. It did not like Win10.
Click to expand...
Click to collapse
Lenovo Moto Smart assistant is your friend. It will rescue your phone and update it even when it's rooted. Free to download just google it BTW thank you for this post. I had boot loop problems until I followed your guide and I have an XT1925-2
hello Guys!
You saved me my life!!
but one question...why is it not possible to use the newest version?
Update:
After the routine from post 1, you can directly update to 20.4
Magisk YouTube add remover....
I'm not sure who to ask about a Magisk Module because I don't know who created it, but there used to be one that would remove all the ads on YouTube. It was really cool but I can't seem to find it anymore...Anyone know anything about it??
chaningbox said:
After install newest Magisk,Force-encryption disabler,I met bootloop. (Test in android 9 pie,sovled after using Magisk 19.3 and Disabler 08.18.2019)
Twrp for Motorola g6 : https://twrp.me/motorola/motorolamotog6.html
Magisk 19.3 : https://github.com/topjohnwu/Magisk/releases
Disable_Dm-Verity_ForceEncry_08.18.2019 : https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Follow this step by d412:
Flash twrp, hit cancel when prompted for password
Wipe>Format data>type yes
do not hit reboot system, Hit the back button multiple times until main menu
Go to reboot tab, click reboot recovery
Wipe>format data>type yes
do not hit reboot system, hit the back button until main menu
Reboot tab> click reboot > click recovery
TWRP reboots > Install tab
select Universal DM verity
Swipe to install, wait for it to finish
Backbutton
Select Magisk, swipe to install, you're done
Click to expand...
Click to collapse
I can't find this magisk version.
Fast question after this can I reboot to my android 9? I just want root my phone