• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help LG LUCKY (L16C) IN BOOTLOOP ON CUSTOM BOOTANIMATION

I

Iaanajn

Lurker
Hi,
I've modified the stock bootanimation of an Lg Lucky (L16C) with another one (custom) from XDA.
Once I gave root permissions to the smartphone with KingoRoot, downloaded a file explorer, copied the "bootanimation.zip" file in the proper folder (/system/media), edited the R/W permissions to "R/W" for all categories (user, admin, system) and rebooted the smartphone, the LG Lucky phone booted up with LG logo, then the custom bootanimation, but then the sequence of images slowed down and the smartphone booted up again: this continued to happen until I disconnect the battery from back.
I saw on the Internet lots of guides and tutorials of how to unbrick a soft-bricked smartphone, and I even tried to disassemble the unit to replace the phisycal memory with a new one, but I turned out that was all soldered together and I couldn't find any parts on Internet. Now I have no idea of what to do, because I discovered that it can't enter in Recovery/Fastboot/Download Mode, even if it's an Android Phone (android phones usually have their own stock recovery installed, so I didn't installed a custom one), because it continues to goes in bootloop, ignoring mine inputs from the buttons.
Obviously there's not a chance trying to connect with ADB, because it goes in bootloop before the launcher can open. Is it possible to repair the smartphone with a JTAG process?
Then, I tried to search if it was possibile to wipe data out of the memory without using recovery/fastboot/download mode: i found some over-complicated tutorials that I couldn't understand.
I finally wrote on this forum to see if someone can help me (note: not go into specific terms or commands because I'm quite a beginner).
Thanks in advance!
 
Last edited:
ocnbrze said:
do you have a custom recovery? if not then that was your first mistake.

but your xda thread has a good suggestion:
https://forum.xda-developers.com/t/lg-lucky-l16c-in-bootloop-on-custom-bootanimation.4203949/

if you have usb debugging enabled and you have adb setup, you can try the suggestion there.
Click to expand...

Hi!
Thanks for the fast reply! Ok, I'll try asap the XDA thread's suggestion.
But in the meantime, I've got a question (for future modding tries on other devices): if I had installed a custom recovery, like "TWRP", the smartphone could have entered the same in the custom recovery mode and I could have wiped all the data out of it? Or the situation would have stayed the same?
 
Iaanajn said:
Hi!
Thanks for the fast reply! Ok, I'll try asap the XDA thread's suggestion.
But in the meantime, I've got a question (for future modding tries on other devices): if I had installed a custom recovery, like "TWRP", the smartphone could have entered the same in the custom recovery mode and I could have wiped all the data out of it? Or the situation would have stayed the same?
Click to expand...
one of the main features of having a custom recovery is that you can make nandroid backups in case something like this happens. as long as you have a custom recovery you can always restore a nandroid backup and your phone will be like nothing ever happened! of course some of the other features is that you can also wipe the different partitions as well.....including data.
 
ocnbrze said:
one of the main features of having a custom recovery is that you can make nandroid backups in case something like this happens. as long as you have a custom recovery you can always restore a nandroid backup and your phone will be like nothing ever happened! of course some of the other features is that you can also wipe the different partitions as well.....including data.
Click to expand...

Hi!
Thanks for the clear explanation! Yesterday I've tried, as the XDA's thread suggested, to connect the smartphone to the PC (firstly wih "FILE EXPLORER" and then, also with "ADB") and see if it recognised the LG Lucky... but what happened was only that a screen on the PC said that the linked device was only configured in "USB CHARGE ONLY".
In the end, from what I've learned, the big mistake was to not use a custom recovery (like "TWRP", "CWM", ...): but, if the stock recovery couldn't open once changed the "bootanimation.zip" file, the custom recovery would had behaved in the same way?
 
You must log in or register to reply here.
Back
Top Bottom