Panasonic P81 stuck at boot animation - Upgrading, Modifying and Unlocking

Hi
I just make some changes in build.prop file, and then reboot my device and its stuck at boot animation,
I think i made some mistake in build.prop,
i had taken backup of build.prop, but i forget to install CWM, (So i cant use aroma file manager).
ADB is also not recognizing my device.
Is there any way to make it working agian
Thanks in adv
Sumit.

where i can found animation in panasonic p81

Related

[Solved] Changed boot animation, now I've got blackscreen

Hi Guys,
Used the ROM Toolbox to change my boot animation several times successfully (over numerous months). Last change, on the next reboot, I get the Google splash screen, then black. The phone actually boots fine, but you can't properly wake the screen any more. Nothing appears to happen, until you press the power button again, and then you see the screen-off animation very briefly (old style TV turning off) then black again.
Clearing cache/dalvik/etc in CWM recovery doesn't do anything.
Fastboot and recovery work fine. Problem is you can't do anything about the bootanimation.zip in CWM Recovery and there isn't much you can do in fastboot either. Plus my ADB debugging wasn't turned on and you can't easily do this without the screen so I can't modify files. Its definitely the boot animation that caused it though.
I fixed it when I searched for a recovery that allows file management - TWRP http://teamw.in/project/twrp2
Used fastboot to flash this to the recovery partition ( sudo ./fastboot flash recovery ../../Downloads/openrecovery-twrp-2.3.1.0-maguro.img )
Then booted into that recovery. The file is in /system/media but don't forget you have to mount the system partition in the recovery rom before you can see anything under /system.
For me the old bootanimation.zip.old was there so I renamed the current to .bak and then the .old back to .zip
Reboot all good. In case this helps anyone!
Thanks!
Just now this happened to me and was able to reboot into TWRP2 but did not know how I would rename bootanimation, simples: mount system and use recovery file manager under advanced.
Did not know bootanimation could do such a halt in phone boot.

[Q] Xolo Q700 boot Loop issue

Hello friends,
I have made a changes in boot animation .zip file and i created my own custom boot animation zip file in system /media folder. After I restart my system it got stuck. it working in back end, but I cant see my main screen. I have tried many way to recovery but it didnt work, so plz could you tell how to change that boot animation file from PC. adb is the solutuin?
kindly help me ASAP.

[Q] P601 on boot loop

hello
I was editing "user" files in system directory
after edit I reboot my tablet but my tablet went on a boot loop
I can't delete my data because I need them all and can't make a factory reset or etc
Is there any way to edit files from pc or with recovery menu to restore all changes back?
or any file to install and exit from boot loop?
thank you all

[HELP] I'm having Issue's with the Boot Animation

I'm trying to install a new boot animation it's a flashable zip file but it isn't working for some reason only thing that pops up is "Animation Boot Test 720x1280" help me please

Custom Boot animation

I want to make a boot animation(I have already made an animation)like Apple's.
I put the animation to system/media but nothing changed, Magisk module can change it
mihhut said:
I want to make a boot animation(I have already made an animation)like Apple's.
I put the animation to system/media but nothing changed, Magisk module can change it
Click to expand...
Click to collapse
You need to put the boot animation into /system/system/media. At least, the way TWRP mounts it you do. I think it's because /system is actually mounted as / once the system has come up?
FYI - Here's what I did:
- Boot to TWRP.
- Go to Mount, uncheck readonly and mount system.
- Copy my boot animation to /system/system/media/bootanimation.zip
- unmount system.
- reboot
I had an animation that was packed into a TWRP-installer zip, but it didn't work on the A2 Lite because it wrote to /system/media instead of /system/system/media.

Categories

Resources