Greetings,
I am running an HTC One with CyanogenMod (Android 4.2). I had attempted to create and load a custom boot animation. I was able to pull from the source zip (/system/media), and confirm that I could reload it. I greated jpg's which were the same pixel count as the Cyanogen Animation (I didn't touch the desc.txt at all) and recompressed it (mac user so zip -0r bootanimation.zip). I pushed it back to the same location, and rebooted the phone. I was greeted with the wonderful message saying my bootloader has been tampered with, and then nothing for the rest of the phones boot until the lock screen.
Reloading the original animation zip still works. I have also tried a couple other tested HTC One boot animations, and none have succeeded. I ran the bootanimation command straight from the bin folder, and nothing happens. It just skips to another line, no message, no animation.
I am from the world of windows originally, and am still getting used to the mac/linux structure of things. Any help would be greatly appreciated as I am not sure how to troubleshoot this problem further. All googling on the topic has produced solutions for others, but not myself. I understand this is a new piece of hardware, and it just may not be possible yet.
Thank you!
Related
For folks that have been having the issue of being stuck at the boot animation (the threading nexus one logo), after updating your ROM. Try this...
- NOTE: You'll need adb.exe, available in either the superboot package or the Android SDK (WITH usb drivers!).
1. [FROM N1]Connect your N1 to your computer, if it isn't already (Even though it's at the boot animation, the adb.exe app should actually still be able to detect and send commands to it).
2. [FROM PC] open a command-line window into the location of the adb.exe app
3. [FROM PC] Enter 'adb.exe devices' and verify you can see your N1 listed.
4. [FROM PC] Enter 'adb.exe logcat > n1-log.txt' and let this run for a minute or 2... The logcat command displays the ongoing actions of your N1, watching it live is overwhelming hence piping it to the text file.
5. [FROM PC] After the couple of minutes, enter ctrl-c to stop the logging.
Now open that n1-log.txt file and look for any clues as to why your N1 isn't booting properly.
Tips for searching through the log:
- Use something like Notepad++ for hunting through the log, the regular notepad ain't gonna get you far.
- When looking through the log, look for lines that start with; 'W/', 'E/' and 'F/' (they indicate Warning, Error and Fatal). Priority is finding the Errors and especially any Fatals
- Once you've found some W/ and E/, use the associated process ID (the number inside the parenthesis) and find all lines that have that PID. Notepad++ has a cool feature where you can copy just the found lines, then you can create a new blank page and paste the details in. You now have a full snapshot of a specific process that had issues, from start to finish.
For me, I had updated my ROM to the CyanogenMod Beta4 and on reboot it would get to the nexus one animation but go no further. After going through the logs I saw a pattern of processes that kept crashing at a certain thread within the PowerManager startup sequence (looked like an issue with loading something). Unfortunately I'm still very new to all this, so was unable to discern the specific issue so I just did a wipe and started over and it worked.
Good luck!
Hey Namuna,
Just wanted to say THANK YOU for this information. I'm not currently having problems (my nexus is on a fedex truck at the moment) but I'm sure this info will come in handy, so I really appreciate you sharing it.
Regards,
Beta
What about a non-threaded nexus logo.....
and also not after flashing a mod, but right after unlocking the bootloader and flashing the recovery image. That's the problem i'm facing....it will run the bootloader but not recovery or the OS.
Any Thoughts?
byalansmithee said:
and also not after flashing a mod, but right after unlocking the bootloader and flashing the recovery image. That's the problem i'm facing....it will run the bootloader but not recovery or the OS.
Any Thoughts?
Click to expand...
Click to collapse
If you can't even get to recovery, go back and fastboot recovery again. Redownload the recovery image and check its MD5 to ensure that it downloaded without error. Make sure you've followed the flash instructions precisely.
Also, you can start to pull logcats surprisingly early. If you have a hung boot and you need one, it's worth trying even if you never get to the fully-animated logo.
I had the same issue. The fix for me was a wipe, and repeating the flash of rom...
When i first flashed the rom i forgot/skipped the Wipe step.
Finally found the answer in the Nexus forums: http://forum.xda-developers.com/showthread.php?t=1379875
--------------------------
Please tell me I'm not missing the obvious. Here's the deal.
When the phone is booted and running normally, adb works fine. No problems looking around/pulling/pushing/changing permissions/etc...
But when I boot into recovery, it says it has found a new device (Android Samsung SPH-L710 or something like that) and wants to install drivers for it. I have searched thoughly using just about every combination of "adb" "Samsung" "recovery" "Galaxy S3" etc, etc, etc I could think of. They all point to the drivers I already have !!!
I like to make custom icons for things like the title bar, you know, just add a little color to the signal strength, data in/out arrows, things like that. My usual routine with my old EVO was to hook up to the computer, use the batch files I have written to pull framework/SystemUI or whatever, drop in the png I changed, then reboot the phone to recovery and push them back. I don't like using root explorer to put them back while the phone is running normally, but that's what I've had to do so far.
Can someone point me in the right direction? Am I missing the obviuos (wouldn't be the first time ) ?
Nobody? Is adb working for you in recovery?
I've zipped via store method, checked and rechecked desc.txt, left an extra line, made sure the permissions are correct on my phone, 644, and still can't get it to work. The downanimation works fine (even compressed), but I've yet to get the bootup animations to work. Mounting system in recovery and pushing to /system/customize/resource/vzw_bootup.zip. And every reboot, nothing beyond the HTC Splash (with their nice little dev unlock warning). After that, it's black.
Any ideas?
http://azconceptphoto.com/kernel/Droid_Peeing_On_Apple_store.zip
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
HI all,
Did anyone figure out a way to apply a customer boot animation since we can't simply go an change the bootanimation.zip file and so far all magisk modules i tried simply don't work.
Unless you have a fairly short animation, by the time it thinks of getting moving you've already booted into the home screen. In the past I created a couple of custom boot animations. I stopped using them when I chose to use rooted stock firmware instead of custom ROMs. As a result I haven't searched for a long time for a replacement boot animation: not that I need to given I still have my boot animations stored on a HDD.
it is a short one well kinda, wanted to put the nokia handshake as the bootanimation for fun but couldn't figure out how to actually do it due to android 13 read only limitations and i think the modules i tried didn't work due to the pixel now having a dynamic animation not quite sure, seems like its not worth it anymore