Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea
dre-z said:
Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea
Click to expand...
Click to collapse
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.
tabletalker7 said:
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.
Click to expand...
Click to collapse
Thank you very much, the tip with flashing magisk 16.4 worked! I didn't need to go back, I just reflashed 5.1.9 without magisk and the error was gone.
Hi, I got the same problem.
Until I flashed my custom kernel ElementalX the messege disapeared
Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?
why dont you guys stick with stabe 16.0?
I did uninstall of 16.6 and then install 16.4, no error message anymore. Didn't flash directly over it.
Tried as you said but still got that message.
Deacon-Frost said:
Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?
Click to expand...
Click to collapse
When you install the update to 5.1.9 you have to reflash Magisk. I just used Magisk 16.4 when I did it.
I can confirm completely uninstalling magisk and then installing 16.0 with an upgrade to 16.6 solves the error
Try this.
https://forum.xda-developers.com/sho...&postcount=386
I had the same problem and this fixed it for me.
The easiest way is explained by XDA user "airtower", read his response at:
https://forum.xda-developers.com/on...-oneplus-6-t3794232/post77104551#post77104551
Thanks!
This hint was really helpful and is highly appreciated. The message is gone. :thumbup:
Uninstall in Magisk app, select restore images. Do not reboot and install it via app again and now you can reboot that's it. very simple
Guys just flash magisk 16.6. It will work without the error message. Just after you flash, boot into system. Then go into magisk manager and click on Uninstall and then Restore Images. Then right away, without rebooting, install using the Direct Install method and making sure that both of the "preserve" options are checked in Advanced Settings before installing it.
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Maybe you have some Magisk module causing this. There is an option to disable Magisk modules through command line.
memocatcher said:
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Click to expand...
Click to collapse
If you used magisk uninstaller and the reboots are gone then just flash magisk again. Also it's best to use 19.4 magisk
Ive tried uninstalling magisk using the un-installer and no go. Ive tried booting into twrp then flashing the twrp zip then rebooting into recovery and it goes to the stock recovery. How do i get back TWRP?? Im on Pie and was using twrp .65
NVM: I had to re-flash 9.5.11 then twrp then reboot then magisk 19.4
I am in your same situation oneplus7.
Currently I was with twrp 3.3.1.1 but there is no way to catch any recovery. By flashing the image either version 1/65/70 (more current) by fastboot it enters correctly img you access twrp to later flash the zip But it never gets installed.
I tried to uninstall using img twrp Magisk zip uninstaller and install the 19.3 / 20v uninstall it completely and flash back to zip twrp but I am in a dead end.
Right now I am with Magisk v20 root edxposed and everything goes phenomenally as a result that I am going to "peel" without having twrp for my backups or anything.
Anyone have any idea how to install twrp again?
boot into twrp.img then flash the last rom you were using, then flash twrp.zip, reboot into recovery and install magisk 19.4. After reboot you will have to enable all your rooted apps again and install your magisk modules again.
after updating OS to 10.3.5 i cant boot after installing Magisk 20.4
i hade to uninstall or not installing Magisk to be abele to boot
any help ?
i guess uninstalling should fix
I'm having same problem.
Both magisk 20.3 and 20.4 don't work for me.
The canary build doesn't work either.
I had a somewhat similar issue.
I used Oxygenupdater in 'automatic mode' and it flashed 10.3.5 but lost root.
So I did fastboot with TWRP 3.2 (the same with which I initially rooted) which did not work. I got Qualcomm Crashdump error Ugh.
Then I downloaded TWRP 3.4.0.3 (latest version) and that worked and flashed this TWRP and then Magisk and so I got root back.
So NEVER use Oxygenupdater in Automatic mode, even when you specify you are rooted.
For TO: try latest TWRP and latest Magisk, and more importantly, the latest ADB and Fastboot tools ! And use original USB cables.
I've tried latest TWRP and magisk. Still same problem, I'm stuck at bootloop
Edit :
Turns out one of the magisk module was causing the bootloop. After removing modules folder in /data/adb the bootloop was fixed
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).