can anyone explain what the numbers in the desc.txt file mean? It would be useful if I knew exactly what that was doing
I know this thread is old and I have a metropcs huawei ascend, but this guide helped me change my boot animation. The only thing is, I had to put the zip file in the platform-tools folder and run the adb command from there.
Ok so I got everything working fine until I get to the adb push. When I type in the command "adb push bootanimation.zip /data/local/" I get a message saying "adb is not recognized as an internal or external command, operable program or batch file." Someone please tell me what I'm doing wrong. One guy had the same problem and fixed it but didn't post how. Yes, I have debugging on, all the drivers are properly installed. Yes, I put a space in between .zip and the /. I'm even open to someone texting me and telling me how to fix this. Reply here or email me @ firstname.lastname@example.org or text me at "seven four zero - two five one - three nine three four. Thanks for anyones help !!!!!!
I think I may have.
Instead of keeping it in the (x86) folder (it requires admin access) move the folder to your desktop, then install all of the tools you need. Once installed, go ahead and try the steps again, this time utilizing desktop as the path and not folder X86
One more question about this....
I have a Gnex.
I wanted to see what would happen if I did an adb push of an arbitrary file to /data/local... you know, something like a "foo.txt" test. I wanted to see if I could delete it afterwards... all I got was "permission denied"
Bottom line, I don't recall anyone flat out saying this but:
does the file HAVE to be named bootanimation.zip in order for the push to even work?? That would imply that there is something in /data/local that holds a place for it with open permissions, yes? But on my rooted d1, I see nothing there named bootanimation.zip with open perms.
So IF I push bootanimation.zip to /data/local, it "just works" and an "adb shell rm /data/local/bootanimation.zip" .... also will just work even though I cannot adb ls anything that's IN /data/local?
I'm thinking this MUST be how it works otherwise nobody would get it to work, but I'm asking for peace-of-mind please....