I'm having a weird bootloop issue that I can't find an answer for...
If I simply boot the magisk-patched boot.img (./fastboot boot), it will reboot, go into "Preparing for Ram dump", then boot normally; as if I did not just tell it to boot the patched version. (I'm guessing this means that something about the patched version that is causing issues)
If I flash boot the magisk-patched boot.img, I will enter bootloop. It will flash the Google logo, then flash "Preparing for Ram dump" in red.
I'm not sure what I can do here.
I've tried using both Magisk stable 24.1 and Magisk Canary to patch the boot.img
I tried both verified boot and disabling it
Related
I tried to upgrade magisk to latest from magisk manager and device boot loop at Tmobile logo. I can get into download mode, fast boot, and twrp recovery.
However, I do not wanna to reinstall the kdz from download mode .So, flashing the stock boot img from fastboot will fix it ?
Please attach stock boot img or magisk patched boot img . Thanks
My TWRP was not loading (just a logo) and I forgot to root my device. I tried other versions and OrangeFox instead, and then "swipe to unlock" appeared, but touches are not working at all. Only side buttons are working.
*Everything works fine in MIUI
Twrp recovery works without root. That's why you can install magisc to root your phone using twrp. Try more twrp project and try to enter multiple times to recovery. I had the same problem and after 2-3 attempts it works. I'm using pitch black recovery And I recommend it with confidence
You can find this recovery here :
https://forum.xda-developers.com/t/...crypted_data-v2-9-0-base-twrp-v3-3-1.4000857/
As I tryed a loot of twrp project this was the most stable for me. Just flash it using fast boot. Or you can boot it Instead of flashing.
Code for boot : fastboot boot twrp.img
You can use this if you have problems on flashing the recovery.. So after you boot on it you can flash the zip file using twrp if it won't flash using your pc / cmd.
INFO:
If you want root and you got boot loop after flashing Magisk with TWRP(Phone stuck at boot process up to 2-3minutes ) boot twrp and format your DATA. DON'T WIPE! FORMAT!
**WIPE/FORMAT DATA**
*Restart your phone and be patient the boot may take some time after perform data format*
Now you should have the Magisk installed! (The data format does not wipe Magisk Manager from the system (!). It will be there.)
-------------
(!) If something goes wrong you can flash again the stock rom downloaded and repeat the process (!)
------------------
I flashed a Magisk patched A.16 global rom boot to my boot, but I mistakenly didn't add the boot_a code to it making my phone bootloop. I've tried flashing the myogui boot.img again to try fixing it, but it didn't work. I downloaded the A.16 firmware, extracted the OFP, and took the boot.img. I flashed that one in both partitions but it didn't work, my phone is still boot looping.
What can I do to fix this? I'm so confused and angry over this. I just wanted to root my device.
Wrong post sorry
Can you boot to bootloader manually with vol down and power keys?
Then rerun boot.img flash to current partition. Make sure the patched boot.img is for the correct version currently on phone.
If you already tried this, then maybe other files didn't flash right. You can reflash myogui global A.10 and repeat the process
It took me a few tries to get it working. Not sure why but eventually it booted
I updated via flash.android.com and it booted into the OS then I rebooted and flashed the patched boot.img (Magisk 25201) using command fastboot flash boot --slot=all magisk_patched.img and when it booted it got to the lockscreen but then gets stuck on Phone is Starting... indefinitely. So I tried rebooting with power+volume down and flashing back to the stock boot.img with the same slot=all and it booted to the lock screen but the display flashed on and off 4 times then it brought a message up saying rebooting and it's stuck in a boot loop now on the Google logo. Tried flashing back to magisk patched without slot=all and it again gets stuck on Phone is Starting... I used adb shell magisk --remove-modules to clear any modules that could be causing it and that didn't change anything.
I can perform the flash.android.com again successfully but it still has the same boot loop issue after. I was only checking Disable Verity and Disable Verification as usual for the update. I tried unchecking those both and running it again but still stuck in the boot loop. Is there anything I can do besides factory reset? I don't want to lose my data.
slickrasta said:
I updated via flash.android.com and it booted into the OS then I rebooted and flashed the patched boot.img (Magisk 25201) using command fastboot flash boot --slot=all magisk_patched.img and when it booted it got to the lockscreen but then gets stuck on Phone is Starting... indefinitely. So I tried rebooting with power+volume down and flashing back to the stock boot.img with the same slot=all and it booted to the lock screen but the display flashed on and off 4 times then it brought a message up saying rebooting and it's stuck in a boot loop now on the Google logo. Tried flashing back to magisk patched without slot=all and it again gets stuck on Phone is Starting... I used adb shell magisk --remove-modules to clear any modules that could be causing it and that didn't change anything.
I can perform the flash.android.com again successfully but it still has the same boot loop issue after. I was only checking Disable Verity and Disable Verification as usual for the update. I tried unchecking those both and running it again but still stuck in the boot loop. Is there anything I can do besides factory reset? I don't want to lose my data
Click to expand...
Click to collapse
You don't need to disable verity/verification if you aren't running a custom kernel.
Try sideloading the OTA. I'm not sure what went wrong in your case.
Are you sure you're using the Android 13 boot image? I would remove all old images and start over just in case. As I'm sure you've noticed by now, there's absolutely no way to tell what version a boot image is, as they're all named the same regardless of what update they're from.
Am having serious issues here
Each time I flash TWRP on my a/b device,when I flash stock boot and then install recovery ramdisk .I always end up device either booting to fastboot or endless boot loop.pls ies there anything am not doing right?
I need help