CELLBASS @ 06/16/19, 23:20
We read the topic header, there is a solution for a long time!
You are almost right, but unfortunately this solution did not suit me:
We have
Alcotel U5 Model 4047D Chipset - MT6580M , Android 7.0, kernel version 3.18.35+ build number 010 04
Body with custom recovery TWRP 3.0.2, Root in SuperSU and Root Explorer
Using SurerSU and RootExploer, I was able to change bootanimation without any problems, just put another file in the directory and it worked.
The task is to change the Logo at boot. So what did:
Uploading the Logo image via FLASH TOOL, unpacking the downloaded file using LogoBuilder, the program reads everything perfectly:
Then we press the pack button, and fill in the received file through the FLASH TOOL on the body
After pressing the power button, the phone vibrates once and that’s all - a black screen and no signs of life.
I fill in the body with the FLASH TOOL logo image, which was before the rebuilding program and the phone comes to life.
But, in fairness,
I must note that the problem is still not in the program .
The body rejects any changes to the file. Conducted a series of experiments with this image Logo. I opened it in the Nex editor, tried to change bit information in different places of the file. Each time, the changes were saved and the changed file was uploaded through the FLASH TOOL to the body. And how was it possible to find out if I change anything within the address 0x0 and up to 008c1ec
The result is always the same - a black screen, the phone does not turn on.
If I change something beyond this memory area (and after that there are only zeros in the file)
The phone boots up and turns on.
To make sure that the file is saved normally, changed the value in the “sick” area of ​​the file, saved it, then returned this value to the original one, saved the file again and uploaded via FLASH TOOL, the phone booted up, i.e. all OK.
Unfortunately, I do not understand binaries at all, and I can not understand what is in this file. I suggested that this file should contain images in binary code, correcting which you could change the download. But apparently, the system, when loading, conducts some kind of check that the uploaded file does not pass, with changes in this memory area.
Logo image file is here
https://yadi.sk/d/r-FLbno4MygU8w. Maybe someone will suggest what can be done.
Yes, and through TWRP I tried the same thing, the result is the same, the body does not turn on.