On the latest version of A11, running Arter Kernal R12, updated to the latest canary build, and now I am unable to boot into the OS.
Tried restoring a backup I had with TWRP, but still stuck on the boot animation. Any help would be appreciated!!
Try dirty flashing OOS11 OR try flashing the stock.IMG, you can extract it from the ROM package. Could be that some of the modules is failing hence that you're stuck in bootloop.
Adelino80 said:
On the latest version of A11, running Arter Kernal R12, updated to the latest canary build, and now I am unable to boot into the OS.
Tried restoring a backup I had with TWRP, but still stuck on the boot animation. Any help would be appreciated!!
Click to expand...
Click to collapse
You need to match the Kernel with the image of the OS you are on by typing fastboot flash boot boot.img
ekin_strops said:
Try dirty flashing OOS11 OR try flashing the stock.IMG, you can extract it from the ROM package. Could be that some of the modules is failing hence that you're stuck in bootloop.
Click to expand...
Click to collapse
Can I disable the magisk modules by deleting them? if so where can I find them? as for flashing I just need to fastboot boot the correct boot.img?
Switch back to your other slot which should have the stock boot image. Boot into fastboot mode and then run one of these commands depending on which slot you're in. If you don't know, try one, boot up, then try the other. That should get your phone back to a working state.
fastboot --set-active=a
fastboot --set-active=b
Related
Okay, so I had to give lineage a try and have now switched back to stock rom.
On Feb update
Twrp img is 3.2.1.0
No matter what I try I am getting a bootloop when trying to install magisk.
My current steps:
Completed a stock room flash with wipe
Fastboot flash boot --slot all boot.img. ( Stock boot image)
Phone is on slot_a
Fastboot boot twrp.img
In twrp I have tried to just flash magisk 16.0
Restart system
I'll get to the Google splash and it will just sit there forever.
If I manually restart I get a brief Google splash then cycles to bootloader.
Where am I failing?!?!
You don't have to flash any boot.img after installing the stock with flash-all. You can also try to flash the stock to both slots and flashing the twrp after fastbooting it, rebooting and then flashing the Magisk.
FIXED**
So i again did a complete wipe with the most recent feb OTA via flash-all with the -w included.
Afterwards booted, setup completed
restarted to bootloader
fasbooted twrp
flashed elemental x kernel
rebooted system
fastbooted back into twrp
flashed magisk 16.0
rebooted system
Works perfectly now.
Hopefully this can help someone out in the future!
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Sumit Sikder said:
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Click to expand...
Click to collapse
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
I tried the latest v22.1. It worked in Android 11 evolution X ROM but not in realme UI 1! The only reason I installed my Android 10 was because Magisk modules weren't working in Android 11!
oxbowlarry said:
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
Click to expand...
Click to collapse
I have seen another rooting method with ADB and the patched boot image BUT that method first flashes vbmeta.img before flashing the patched boot.img.
Perhaps that is why my boot partition was corrupted because I just flashed the patched boot.img.
Has anyone had success with this rooting method on a Realme 6 pro ?
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)
Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/
Hi I recently made a mistake by flashing Arter97 Kernel on my International/Global OP9 which was on android 12.. I am attempting to fast boot the c39 update via platform tools. I am currently stock in fastboot mode, and whenever I attempt to boot the stock 39 img I have the error, " failed to load/authenticate boot image: Load Error" Any help would be appreciated!!
Edit: SOLVED
You can try downloading and falshing the stock boot img. For whatever version of Android you were on. Like android 11,or Android 12. Make sure you get the boot img. That you had before you flashed the kernel. So download the boot img. Specific for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.
Adelino80 said:
Hi I recently made a mistake by flashing Arter97 Kernel on my International/Global OP9 which was on android 12.. I am attempting to fast boot the c39 udpate via platform tools. I am currently stock in fastboot mode, and whenever I attempt to fast boot boot the stock img i have the error failed to load/authenticate boot image: Load Error. Any help would be appreciated!!
Click to expand...
Click to collapse
you need not fasboot boot boot.img
use fastboot flash boot boot.img
Soft_M said:
you need not fasboot boot boot.img
use fastboot flash boot boot.img
Click to expand...
Click to collapse
I actually did flash the update to both slots, and it would still be stuck in fast boot mode. I ended up having to use the MSM tool to reset to stock.
brandon79 said:
You can try downloading and falshing the stock boot img. For whatever version of Android you were on. Like android 11,or Android 12. Make sure you get the boot img. That you had before you flashed the kernel. So download the boot img. Specific for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.
Click to expand...
Click to collapse
Thanks ended up using the MSM tool. Thank God Oneplus provides us with the tools to flash at a chip level..
Adelino80 said:
Thanks ended up using the MSM tool. Thank God Oneplus provides us with the tools to flash at a chip level..
Click to expand...
Click to collapse
Yes, for that kernel, you need boot, dtbo, & vendor_boot backup to go back to stock or another kernel. Awesome that you already fixed it though, just thought I'd mention.
Samuel Holland said:
Yes, for that kernel, you need boot, dtbo, & vendor_boot backup to go back to stock or another kernel. Awesome that you already fixed it though, just thought I'd mention.
Click to expand...
Click to collapse
Thanks for the information. By any chance how would I normally backup vendor_boot and dtbo partitions which the Arter97 Kernal touches. Can I back that up using TWRP?
You had before you flashed the kernel. So download the boot img. Specific mcdvoice for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.