Can somebody help me with the boot issue when I tried to apply the backup file of build.prop? If possible someone can provide me the original build.prop and guide me to flash it with stock recovery since I'm not having any custom recovery installed?
Hello. I recently used elementalx kernel and now want to switch back to stock. I backed up my kernel through EX kernel manager but unfortunately it fails to restore the backup. I am trying to manually restore the backup from the .img file created by EXKM in twrp. It is asking me whether I want to flash it in recovery system image or bootloader. The most obvious choice seems to be bootloader but I want to confirm as I do not want a bricked phone. Please help. Thanks.
You could always just dirty flash the rom.
Haha I flashed the image file in the bootloader and it worked. Thanks for answering though.
tl;dr: Updated to 7.1.1 OTA then installed twrp 3.1.1-0 had it apply what I assume is the F2FS kernel fix, now phone won't boot into system
Yesterday I was trying to update my rooted phone from MM to the latest software. I did this by reverting everything back to stock using this guide and that worked without a problem. Once it was back to stock I upgraded all the way up to the most recent OTA from Motorola (7.0.1 I believe), and then I upgraded up to the most recent 7.1.1 OTA manually using this guide. After all the updating I then flashed twrp 3.1.1-0 and booted into it. This is where things went wrong, after booting into twrp for the first time I asked me if I'd like to like to apply what I'm assuming is a kernel with the F2FS fix, I didn't think much about it and accepted it. In retrospect this was a very bad idea seeing as the F2FS fix for 7.1.1 hasn't been released yet. Now whenever I try to boot into the system the bootloader warning screen shows "ID: bad key" and won't boot. I can still get into the bootloader for fastboot and the twrp recovery but I don't know what to do from here in order to fix it. If anyone could help me fix this I'd really appreciate it!
f2fs fix is Kernel. You need an original boot.img of your currently installed firmware version and flash that to uninstall f2fs. Then it should work.
My advice in general:
Before doing any updates: do a full Nandroid backup.
Before modifying boot partition (f2fs fix, install Magisk or SuperSU or phh superuser) do a backup of at least boot.img. it may be a good idea to do a system backup (system boot recovery logo oem). Will help for OTA updates.
Before modifying recovery, back it up.
Before doing any modifications, save your data (data partition, but careful: /data/media is excluded here! You need that additional).
I hope I'll learn to keep all this in mind too without getting out of patience
I just spent the last day going through your exact issues. Pm me if you need instructions and files. I can look up exactly what firmwares and fastboot commands I used to get back to normal.
I flashed the magisk module for using the auxiliary cameras in the Google-camera, and it resulted in the phone only booting to the flashboot mode and nothing else. I tried that twice and I'm certain that flashing it was the only problem.
I reflashed the stock boot image to solve it.
Is there a way now to safely flash it ?
Can anyone help combine a list for some other Magisk modules that may cause bootloop for the device?
PS: The device was rooted without using any custom recovery.
ha ha.. same thing happened with me.. flash stock boot.img and you'll be able to boot back to your system.. but if you need magisk back, custom recovery needs to be there.. which will help you to uninstall the module you have installed..
fathomer said:
I flashed the magisk module for using the auxiliary cameras in the Google-camera, and it resulted in the phone only booting to the flashboot mode and nothing else. I tried that twice and I'm certain that flashing it was the only problem.
I reflashed the stock boot image to solve it.
Is there a way now to safely flash it ?
Can anyone help combine a list for some other Magisk modules that may cause bootloop for the device?
PS: The device was rooted without using any custom recovery.
Click to expand...
Click to collapse
Factory reset will remove the rogue module
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/