Hi all,
I just experienced a boot loop when updating to the latest Magisk + Manager.
Now, I'm still on Nougat (rooted my T820 ~ 2y ago) and also was still on Magisk 18.1.
(Tablet was manually debloated and worked exactly as it should, so I was a bit lazy on the updates)
Yesterday apps, including manager, suddenly started crashing, so I updated Magisk, which resulted in a loop on reboot.
Nothing worked, except fully removing Magisk (via TWRP) and installing 18.1 + manager 7.0 again.
Haven't tried versions inbetween.
Anyone else experienced problems?
Thanks a lot everyone for your help!
Related
Hello,
These past two days have not been a good day for my phone lol. Some background:
BEFORE:
I had a 4.4.4 Custom ROM [Forgot the name...]
TWRP: 2.5.0.2
AFTER:
I clean flashed http://forum.xda-developers.com/gal...m-cyanogenmod-12-0-nightlies-verizon-t2998057
I cleared cache + Dalvik after the flash and it asked me if I wanted to fix root (From what I read before, you're never supposed to press Fix, rather you're supposed to prses Do not Fix and you'll still keep your root.
However, I accidentally pressed Fix Root and Now I lost my root. The ROM I flashed is glitchy because from what I read is because I have TWRP 2.5.0.2.
Now I'm stuck on this ROM, I have no idea how to upgrade to the latest TWRP and don't know how to get my root back . [Can't get TWRP Manager because I don't have Google apps (I tried flashing the GAPPS by Paranoid but it keeps crashing because I think it's the outdated TWRP)]. I tried to download TWRP manager on my phone via another site, but it doesn't install on my phone for some weird reason.
Thank you,
Jerry
Download, install and run the towelroot.apk file. This will root your phone, takes about 2 minutes
I got old Samsung Galaxy S2 / i9100 and it still had Android 2.3.3 on it. The owner said it worked fine for him. I updated it to latest stock (4.1.2) using Kies and the phone started freezing heavily - it freezes anytime (during post-install process with Android icon, configuring apps, typing password for wifi, adding google account etc) - I didn't manage to go thru the initial setup. Sometimes there are dots/dashes on screen when it freezes and sometimes it reboots itself after the freeze.
When I flashed 2.3.5, it started to work normally again, without freezes.
When I flashed CWM-KitKatCompatible-i9100.tar (probably CWM on KitKat kernel for Odin), it freezes anytime during navigating thru CWM and it won't boot. Although flashing CWM with CF-Root-SGS2_XX_OXA_KI3-42-v4.2-CWM4.tar (2.3.x kernel with SU and CWM integrated) works fine and CWM and phone work fine.
I tried flashing also 4.0.3 stock or different 4.1.2 over 2.3.5 with Odin, but it was freezing again.
I didn't give up and followed a guide to install LineageOS 14.1, installed TWRP (it was sometimes freezing after a while of inactivity) and managed to install the LineageOS.
Surprisingly, LineageOS 14.1 seems to run stable so far without freezing, but when I tried erasing it and installing LineageOS 11 (kitkat) instead, it was again freezing and phone didn't manage to start properly.
What do you think could be causing problems with Android 4.x on this phone?
EDIT: it seems to be related to kernel. LineageOS 14.1 was running stable, both OS and TWRP. I wiped it and installed DU 10.6 (MM) and I got crashes again - system doesn't boot and TWRP freezes anytime in a few seconds, I didn't manage even to do wipe in about 10 attempts. I only flashed DorimanX kernel via Odin (tried both Linaro and Uber and they do the same result) and crashes stopped, TWRP seems to run stable and ROM is doing 1st boot now for already over 20 minutes without any freeze.
I suspect it may have something to do with CPU voltage, frequency, memory access or something like that...
No reply so far?
I did some more attempts and found I can run KitKat (e.g. SlimSaber), but only with DorimanX kernel. If I use stock or some different kernel (like Apollo), it freezes and won't boot. So KitKat with DorimanX or LineageOS 14.1 (with stock or DorimanX kernel) seem to work stable, except charging the phone. When I am charging the phone, it reboots in both systems every few minutes when the screen is off. Any ideas how to mitigate that, e.g. using some tweaks in Stweaks? What could be different in DorimanX kernel that makes the phone stable (extept the charging)?
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
Flashed gapps nano
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Edit 2: mentioned gapps
SaraKumar said:
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Click to expand...
Click to collapse
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Noter2017 said:
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Click to expand...
Click to collapse
Thank you for replying.
Twrp was replaced by stock recovery everytime after I installed the rom zip and restarted the phone.
Someone had suggested lazy flasher in the forum. I don't know what it does but it fixed the problem. Is there a way to remove it? And will the recovery problem come back again if I remove it?
Sorry I forgot to mention gapps, I flashed nano after every rom except Pixel CAF(built in gapps).
Hey guys, so I tried flashing the latest Magisk version like a week ago and it worked perfectly, I downloaded Viper4Arise and flashed it but I got stuck in a bootloop and I didn't have a backup at the time, to fix that I installed the stock rom back and flashed old stock Recovery, I got Android 5.1 anyways, I re-rooted using kingroot, flashed TWRP Recovery using Flashify app, then switched ro SuperSU from Kingroot, now, I try flashing Magisk with no luck, it gives me "Space running out" error but I have like 23 GB free, I uninstalled Magisk, and everything went back to normal, I lost my root but I recovered it easily by flashing it since I already had TWRP. Can you guys please help me here? I need MagiskSU ASAP. Thank you.
I suspect your /system partition is running out. of space. I have no experience with migrating your root manager but I'd try unrooting the device as fully as possible and flashing Magisk in TWRP after that.
Good evening, I updated my Galaxy s9 + to the latest firmware, I completed the installation and everything is fine. Then I wanted to root with TWRP and Magisk, but when I restart the phone after installing TWRP and Magisk, during the new configuration the Samsun account no longer works, in the sense that when I enter the email and password I get the message "processing failed". I repeated the procedure (firmware + root) and the problem recurs. How can I solve? Seeing as everything works fine after installing the firmware, isn't there a way to root some app without installing TWRP and MAgisk from Odin like I've done so far? Thanks
I don't remember how was possible to fix this issue. But it's fixed for some custom ROMs, like the one in my signature. I would recommend it.