I have a nexus 5 rooted using 'Towelroot'
I wanted to change my boot animation, and did so using an animation installer. At first, I had the Android L boot installed and it worked flawlessly! Then, I came to XDA and found the "Boot Animation Hub".
When I was linked to his dropbox, I could not see any of the files so I randomly downloaded one. I installed it with ease, and kept using my phone. When the time came to see the animation, only the "Google" logo pops up for a few seconds, then the backlight takes over. No image is shown after that; the nexus boots fully (I can tell because I receive notifications/LED is blinking/ the screen responds to my touch with vibration and tones.
The problem: As I said, the backlight is only there. I cannot see any pictures whatsoever. The phone is completely on, but is not visible. I can reboot into recovery, and see Andy the Android, but cannot install anything, for when I go to recovery mode, it says "No Command"
Does anyone have any help?
Please, anything.
Thank you
Related
Question from a Noob user.
My Galaxy Nexus crashed while I was simply attempting to go to the Play Store. (i.e. I wasn't trying to do any app install or software upgrade or anything.)
After that, when I turned it on, it went to the Google splash screen only, turned off and continually kept rebooted itself back to the Google splash screen. The phone would do this continuously.
I tried the Recovery start next, with the "Press Start, hold down volume up/down buttons," and it got to the symbol of the Android. Then I selected Recovery. When I did that, it went to the Google splash screen and held there without going anywhere. I have to keep removing the battery to try repeatedly try the things I mentioned.
What can I do now?
Help! I just got CM 10.21 emmc running on my 8 GB NT and was becoming familiar with the system. I installed AdAway and after setting it up allowed it to reboot. Mistake!
This is the first time I've rebooted or turned off since the ROM flashing. I get the "N" screen, then an unnerving flash, followed by the Cyanoboot universal bootloader screen and it says "Loading (EMMC)...". Then all goes black :crying:
There is still backlighting and holding the power button will eventually extinguish it. Plugging the tablet into the charger (or the PC) has no effect (off or on).
It did the flashing according to this thread and everything went as described. The tablet has behaved flawlessly until this. I could theoretically recover to stock and start over again but if there is a way to fix this, I'd rather.
EDIT: Update. I tried booting with the CWM SD card that holds the recovery files as well as the files used to flash the CM 10.21 ROM. I get a red bar message that says "booti: bad boot image magic (in memory)". Underthat is "(SDC) LOADING BOOT...." and it's just stuck on that screen.
EDIT2: Solved itself eventually after a number of attempts. Really freaky behavior.
Hi,
I've a Kindle Fire HD 7. I've installed on a cyanogenmad Rom there is a long time ago (maybe two years...). But I wanted to reset all to factory setting today.
I went to setting, and choose "reset factory system". But after the reboot, I saw the orange logo, after the blue logo, and the blue screen with the logo Teamwin on. The screen is flashing, but that all...
When I reboot, it do this all the time and I really don't know how to do :/
I tried to hold the up volume to access to the boot menu, but I doesn't work, and I'm totally stuck.
Could you help me ? Thank you very much !
Same issue!
Help please, it only shows teamwin logo time after time.
Hi I have a huawei Y360 - U61 smartphone which I can't turn on.
The phone has a custom ROM (cyanogenmod 12) which worked great so far.
I have changed the boot animation in the past few days a few times to a gifs i found on the internet using the program "boot animation creator".
It worked great but when i changed it again and tried to reboot the phone, now its shows this picture (ht-----------tp://cdn.androidbeat.com/wp-content/uploads/2015/02/Screenshot_2015-02-01-11-36-36-576x1024.png) (delete the "-----") as it should be but instead of a boot animation after that it just shows a black screen and nothing after that.
I tried to get into recovery mod and it worked.
What can I do to fix this problem?
Thanks.
nevermind, problem solved.
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.