Hi All
I m using nexus 5(Marshmallow v6.1). Well, i was trying to change my boot animation, I downloaded and installed a corrupted one. So, when i rebooted, the phone shows ANDROID like always, but after, a black screen appears and stays forever. I can access recovery, and the phone is rooted. No backup. I deleted the corrupted bootanimation.zip file under System\Media folder and rename it's original name (bootanimation.zip) through recovery mode TWRP. But stuck again in same place in boot animation after reboot and can't go inside. Could you please tell me anyone how to fix it because i don't want to reset or wipe the data it or install another ROM, unless necessary.
Thanks
XDA Visitor said:
Hi All
I m using nexus 5(Marshmallow v6.1). Well, i was trying to change my boot animation, I downloaded and installed a corrupted one. So, when i rebooted, the phone shows ANDROID like always, but after, a black screen appears and stays forever. I can access recovery, and the phone is rooted. No backup. I deleted the corrupted bootanimation.zip file under System\Media folder and rename it's original name (bootanimation.zip) through recovery mode TWRP. But stuck again in same place in boot animation after reboot and can't go inside. Could you please tell me anyone how to fix it because i don't want to reset or wipe the data it or install another ROM, unless necessary.
Thanks
Click to expand...
Click to collapse
Hello,
This seems a duplicate thread of http://forum.xda-developers.com/general/xda-assist/how-to-fix-bootanimation-nexus-5v6-1-t3523810
Thread closed!
Regards
Vatsal,
Forum Moderator.
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
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
XDA Visitor said:
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to flash a custom recovery through fastboot, wipe and flash a rom. For your computer to recognise your device, you need to install the corresponding drivers on your pc.
Good luck!
I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
ikaushalsha said:
I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
Click to expand...
Click to collapse
Greetings and welcome to assist. It appears you have already asked your question in the correct place here
http://forum.xda-developers.com/showthread.php?t=3517583
So I will close this one up
Good Luck
Sawdoctor
Hello there ...,
I have manually (with a root explorer) changed the bootanimation. Now I am stuck in this animation. Is there any chance to flash the correct bootanimation.zip via twrp, if yes, how? Or do I have to flash everything and loose all my data?
nevermind. it wasnt stuck just very long booting.
can be closed.
I own a Samsung Galaxy Grand Prime Plus (SM-G532F/DS) that I recently rooted. All was good till I messed with permissions of some partitions so I had to stock flash it & re-root. So I downloaded the original recovery.img file (or so I think), restored it through TWRP but got a SELINUX POLICY NOT ENFORCING error & previously, my data partition was corrupt & needed to be wiped (due to my permissions tinkering) but TWRP was unable to mount data partition for that. I then tried flashing just the stock recovery.img extracted from stock firmware on which I eventually flashed the lot. Now my phone is fine but everytime I turn it on, the screen is black as it no longer displays the “Samsung Galaxy Grand Prime Plus & Powered by Android” logo anymore. This is actually bothering me so, does anyone know how to restore it or something I can try? Flashing boot.img didn't help so I am stuck with this.
If a similar thread exists please direct me to it. I was unsuccessful in searching for one here & elsewhere..
CuteHunkie said:
I own a Samsung Galaxy Grand Prime Plus (SM-G532F/DS) that I recently rooted. All was good till I messed with permissions of some partitions so I had to stock flash it & re-root. So I downloaded the original recovery.img file (or so I think), restored it through TWRP but got a SELINUX POLICY NOT ENFORCING error & previously, my data partition was corrupt & needed to be wiped (due to my permissions tinkering) but TWRP was unable to mount data partition for that. I then tried flashing just the stock recovery.img extracted from stock firmware on which I eventually flashed the lot. Now my phone is fine but everytime I turn it on, the screen is black as it no longer displays the “Samsung Galaxy Grand Prime Plus & Powered by Android” logo anymore. This is actually bothering me so, does anyone know how to restore it or something I can try? Flashing boot.img didn't help so I am stuck with this.
If a similar thread exists please direct me to it. I was unsuccessful in searching for one here & elsewhere..
Click to expand...
Click to collapse
Try boot into download mode and reflash stock ROM ( www.samfw.com )?
@CuteHunkie
On Samsung devices the boot logo is stored in file param.lfs. If you explore param.lfs, you will find a file called logo.jpg. Thats it, the BOOT LOGO.
That didn't work at all..
LR7875 said:
Try boot into download mode and reflash stock ROM ( www.samfw.com )?
Click to expand...
Click to collapse
That didn't help at all..
jwoegerbauer said:
@CuteHunkie
On Samsung devices the boot logo is stored in file param.lfs. If you explore param.lfs, you will find a file called logo.jpg. Thats it, the BOOT LOGO.
Click to expand...
Click to collapse
Thanks for this. It isn't so much as getting the logo.jpg file but flashing it. I just flashed the param.bin (the one that comes with my stock ROM, 5 files by the way) on the AP section which worked. All along I had been flashing it on the Bal section since I had 5 files to flash..