I flashed OxygenOS 10.0.1 by the fastboot method. Then flashed modded TWRP and then Magisk. This all happened successfully. I wanted to install Youtube Vanced but stock Youtube was causing it to not show up. So I tried uninstalling Youtube through Titanium Backup but it said 'apk not found'. So I downloaded some other app (I think it was named 'System App Remover'). Since then I have been getting bootloops. Phone gets stuck on 'Bootloader unlocked warning' screen then goes into Fastboot mode. I had to uninstall Magisk through TWRP to boot the phone. I don't understand what's wrong in this entire process. Please help.
I think the issue is with the System App Remover. I tried using possibly the same exact app previously but I also got boot loops. I would try a factory reset, reflash twrp and magisk and try the Magisk module "Debloater".
You have to clean temporary magisk files.
Probaby you had enabled some magisk modules on previous system and you forget disable them.
Thanks for the replies. I fixed the problem by restoring System from an earlier TWRP backup.
Usually bootloops from Magisk modules can be fixed by deleting problematic module from twrp file explore /data/adb/modules
Don't have to fart around with uninstalling entire Magisk or installing Magisk debloater anymore
Related
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
did u remove your magisk modules?
Maybe the backup was from slot A and OTA in slot B and something got messed up. In another note there's no need to clean install OTAs from Oneplus, and then having to restore old data is where complications come
Karmonator said:
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
Click to expand...
Click to collapse
I had this problem, minus the TWRP. I had to reset to factory default to fix it. Goto bootloader and reset system settings. You'll end up back on 9.5.10 stock but you should be able to boot. Pain in the ass but it stopped my loops. I didn't have a x.x.10 backup so I had to start fresh.
Try to remove Magisk using Magisk unninstaller and reinstall 9.5.10 on TWRP without rebooting.
After, install TWRP installer again and THEN reboot.
After you check all is working, install Magisk again in TWRP and then install your Magisk modules again.
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
Title says it all....I have deleted system apps fine with previous phones by deleting the folder. The reason I was doing this was because youtube was having a little stutter animation issue that I couldn't resolve so I thought installing as a user app might help. After I attempted to use a play store app to remove youtube the phone would only boot into fastboot mode. I can go to recovery and even fix the bootloop and get back into my phone but magisk isn't installed and installing magisk again returns to fastboot. Did I mess up the boot.img? This seems like an easy fix but I haven't modded in awhile so just trying to be careful at this point.
xlxcrossing99 said:
Title says it all....I have deleted system apps fine with previous phones by deleting the folder. The reason I was doing this was because youtube was having a little stutter animation issue that I couldn't resolve so I thought installing as a user app might help. After I attempted to use a play store app to remove youtube the phone would only boot into fastboot mode. I can go to recovery and even fix the bootloop and get back into my phone but magisk isn't installed and installing magisk again returns to fastboot. Did I mess up the boot.img? This seems like an easy fix but I haven't modded in awhile so just trying to be careful at this point.
Click to expand...
Click to collapse
Just boot a twrp and flash oos,reboot recovery flash magisk and reboot to system.
Also have a backup just in case things go south.
And don't use apps from playstore, because from A10 the system is read only so you have to either delete it from twrp(can cause issues)
or use terminal debloater magisk module(safe this way)
I installed Magisk via twrp(Temp version). and installed a bunch of modules.
Then I decided to complexly uninstall Magisk. I've done that from the Magisk Manager apk(The Complete Uninstall button)..
The phone rebooted and stuck into the phone logo with red danger logo. which means perhaps the boot img is missing ?
I should have uninstalled the modules first, which might have caused this issue..
Now, I Flashed Magisk again via Temp twrp, but now few apps keeps crashing, even after uninstalling and installing them.
i don't have the stock bot image, otherwise i guess i can do fastboot boot boot.img to escape the boot issue after uninstalling Magisk from the app
Note : i tried flashing the uninstall zip file from twrp but that didn't work, Magisk framework still exists !
What should i do now ?
My HTC is the duel sim version (Asia) and i'm using Magisk 22 latest version
Have you tried cleaning dalvik cache?
XDHx86 said:
Have you tried cleaning dalvik cache?
Click to expand...
Click to collapse
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Coldz0 said:
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Click to expand...
Click to collapse
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
XDHx86 said:
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
Click to expand...
Click to collapse
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Coldz0 said:
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Click to expand...
Click to collapse
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
XDHx86 said:
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
Click to expand...
Click to collapse
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Coldz0 said:
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Click to expand...
Click to collapse
You can find your device's ROM here (Literally first google results..):
HTC website
HTC dev center
GetDriodTips (Only for U12+)
**Disclaimer:** I don't own any of those ROMs and I don't hold responsibility whatsoever should you brick your phone or anything goes awry.
had exactly the same issue and exactly due to the same reason (I hate those pseudo-secure banking apps).
I couldn't wipe dalvik as TWRP is still not available for my P5.
But it was fixable really easy by reflashing the patched boot.img:
run command "fastboot flash boot magisk_patched.img"
btw I'm still looking for a solution for that stupid banking app.
I tried the above mentioned "magisk hide" and "safety net fix" and tried hiding the app itself but all that does not help.
Can we delete magisk and still use the phone rooted ? Or will it unroot my phone if magisk is removed. I’m planning to sell my s10 and the buyer does not want the application.
Good information from GetDriodTips (Only for U12+). Thank you.
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).