I have the T-Mobile variant which I installed TWRP and rooted. I tried to change the boot animation manually by following a guide. After changing the file in system/vendor (i backed up the old file) and changed the permissions to wr-r-r, the phone will only boot into TWRP or the bootloader screen. I went into TWRP and changed the backup file back to bootanimation.zip and deleted the custom one, restarted and it still will not boot.
Any help would be appreciated!
I used the "fix recovery boot loop" option in TWRP and it works now.
Related
My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?
babai001 said:
My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?
Click to expand...
Click to collapse
Yes you should be able to install a custom Rom if you have CWM installed and i think you could try to push your Build.prop Backup to your phone using ADB but i dont exactly know how to do that
@OP, if it's rooted then definitely. My HTC Explorer once stuck into boot loop too, I flashed with JaggyRom and it gave me a great experience.
For me, I had to take out the battery and reinsert and then was able to boot into recovery, and from there I flashed it with the custom ROM.
Thank you all
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?
babai001 said:
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?
Click to expand...
Click to collapse
Google is your friend.
Possiblw Solution
A possible solution is to flash back to your original Stock and try rooting again. the stock should get you out of boot loops
Hi, everytime i flash twrp i get into a bootloop in which i can access twrp. Inside all of the system seems deleted and the only option i have is to format and then flash magisk. Then and only then the phone boots up but completely empty as new. Why is this happening? I used to flash twrp on my s6 and it worked flawlessly...
I was trying to switch from SuperSU to Magisk in what I thought would be a simple process following an online tutorial. I went into TWRP recovery and flashed the zip to clear superSU root. Then I flashed the boot.img that I extracted from one of my nandroid backups, and then flashed magisk. But when I rebooted, it's stuck in a loop, just the initial splash screen for a brief moment, then it reboots. Can't access recovery mode or bootloader because it reboots too fast. I'm pretty freaked out here I only meant to install youtube vanced not brick my phone. It won't connect to ADB on my computer because it's too busy rebooting. Is there any way to save my phone? Obviously the boot.img I flashed was the problem, I'm wondering if I extracted it from the wrong backup (different phone). I know that if I can get back into recovery mode I can restore the correct backup, but at the moment all I can do is let the battery drain down because it's not responding to anything.
Please help!
Well I figured it out on my own, but I don't know how to delete the thread.
PistolSlap said:
I was trying to switch from SuperSU to Magisk in what I thought would be a simple process following an online tutorial. I went into TWRP recovery and flashed the zip to clear superSU root. Then I flashed the boot.img that I extracted from one of my nandroid backups, and then flashed magisk. But when I rebooted, it's stuck in a loop, just the initial splash screen for a brief moment, then it reboots. Can't access recovery mode or bootloader because it reboots too fast. I'm pretty freaked out here I only meant to install youtube vanced not brick my phone. It won't connect to ADB on my computer because it's too busy rebooting. Is there any way to save my phone? Obviously the boot.img I flashed was the problem, I'm wondering if I extracted it from the wrong backup (different phone). I know that if I can get back into recovery mode I can restore the correct backup, but at the moment all I can do is let the battery drain down because it's not responding to anything.
Please help!
Click to expand...
Click to collapse
i was on 12.2.5.0 rooted with magisk (by patching boot image pulled from zip firmware).
Phone will no longer boot (stuck at MIUI logo) after i upgraded to 12.2.6.0 with magisk patched 12.2.6.0 boot image. I don't understand why. My steps for updating as follow:
1) flash stock 12.2.5.0 boot image to phone via fastboot before upgrade
2) downloaded 12.2.6.0 full receovery zip file, extracted the boot image and patched it via magisk; copied the patched file to PC
3) copied 12.2.6.0 rom to downloaded_rom folder in phone, upgraded phone with it via Settings
4) phone rebooted to 12.2.6.0 normally after upgrade
5) rebooted to fastboot and flashed 12.2.6.0 magisk patched boot image
6) phone will not boot (stuck at MIUI logo)
7) phone again boots normally if I flashed back stock 12.2.6.0 boot image to it
Any enlightenment to what i did wrong and how to rectify deeply appreciated. Thank you.
(I have used the above method to upgrade rooted LG phones previously and it always went uneventfully; unsure what other steps are need for Xiaomi.)
potatohead said:
i was on 12.2.5.0 rooted with magisk (by patching boot image pulled from zip firmware).
Phone will no longer boot (stuck at MIUI logo) after i upgraded to 12.2.6.0 with magisk patched 12.2.6.0 boot image. I don't understand why. My steps for updating as follow:
1) flash stock 12.2.5.0 boot image to phone via fastboot before upgrade
2) downloaded 12.2.6.0 full receovery zip file, extracted the boot image and patched it via magisk; copied the patched file to PC
3) copied 12.2.6.0 rom to downloaded_rom folder in phone, upgraded phone with it via Settings
4) phone rebooted to 12.2.6.0 normally after upgrade
5) rebooted to fastboot and flashed 12.2.6.0 magisk patched boot image
6) phone will not boot (stuck at MIUI logo)
7) phone again boots normally if I flashed back stock 12.2.6.0 boot image to it
Any enlightenment to what i did wrong and how to rectify deeply appreciated. Thank you.
(I have used the above method to upgrade rooted LG phones previously and it always went uneventfully; unsure what other steps are need for Xiaomi.)
Click to expand...
Click to collapse
steps are good what u tried, at least i root mine every time with patched boot.img same like u. But im on Indonesian rom. didn't try 12.2.6.0 global or eu. But for sure steps u using is good. U can try older magisk manager app (maybe problem is new magisk)
Dadovvv said:
steps are good what u tried, at least i root mine every time with patched boot.img same like u. But im on Indonesian rom. didn't try 12.2.6.0 global or eu. But for sure steps u using is good. U can try older magisk manager app (maybe problem is new magisk)
Click to expand...
Click to collapse
After troubleshooting, I realized issue lies with Magisk modules. I neither deactivate nor remove the modules before updating the rom. It didn't occur to me this is necessary in the first place as previous experiences (on LG phones) did not call for it. After removing them, I am able to root the update via the patched boot image method.
For those facing the same problem, you can remove Magisk modules the following way (downgrading to the previous rom will not work as data partition will be corrupted):
1) grab a copy of the latest TWRP from MB
MBROMS - Browse /TWRPLMI at SourceForge.net
sourceforge.net
2) fastboot boot the twrp img file
3) decrypt your data partition using your phone's lockscreen PIN
4) download Magisk uninstaller from Github and install it
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
5) go to File Manager /data/adb/ folder and check whether there are any leftover traces of Magisk, manually delete any magisk, modules folder or files if they exist
6) reboot the phone into system and root it using the latest Magisk app (for patching of the previously extracted boot image)
Hi, I run LineageOS 19.1 on my Vayu. It is obviously unlocked and I have Rooted it with Magisk.
I have put off updating the System but did it just now through the Updater in the Settings. From 20220916 to 20221104.
I ran into a Bootloop and went into Fastboot, installed TWRP with ADB sideload. (Had stock Recovery before)
I then tried to just revert back to 20220916 (which was not so smart). I tried to sideloaded the boot.img, but it showed "failed".
--> Still in Bootloop after Rebooting
Now I am unable to flash any boot.img or boot at all.
I tried to flash something else (Magisk.zip), which worked. I have removed all magisk modules, tried to boot with
magisk --remove-modules.
Does anyone have any Ideas? I don't really want to Reset my Phone, even though I have abundant Backups.
Thank you )
Moving back to old version almost all the times is not possible without full reset, new version contains new scripts and possibly new files, how would you explain this for system?
By flashing old version over new one, you probably messed up your system, might as well just backup your data and start from scratch.