[Q] Boot animation problem - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Hello,
A couple of weeks ago I decided to change my boot animation on my Archos 101. With Super Manager I copied a bootanimation.zip file to the right folder. When I rebooted my Archos, I saw that the boot animation was very slow and that my tablet wasn't booting anymore. I tried to reboot a couple of times, but still it wasn't working.
Then I went into the BIOS and I saw an option to reset my tablet. I chose that option and after that I booted my Archos. The boot animation was still there, but this time it was booting (after a couple of hours). I tried to delete the boot animation, but unfortunately my tablet wasn't rooted anymore. I tried to root it again, but I couldn't get in the BIOS. I've tried dozens of times, but I still cannot enter the BIOS.
Can someone help me with this issue?

Related

Sero 7 Pro - won't boot

I have a Sero 7 Pro that has sero7pro-bld60220-dopa-v2.0 installed. It has been working fine for months until last night when I picked it up and it was powered off. It was plugged in to my PC usb port like I usually keep it so the battery should have been fully charged and I don't know why it powered itself off. Now it won't boot up. It sticks on the bootanimation screen. I tried to get into Fastboot using the volume/power button but it just hangs on the Fastboot screen and never goes any further. I am able to get into Recovery and have tried various options from just clearing cache and data to restoring the original OS using sideload and Adb on my PC. Nothing allows me to boot beyond the bootanimation. I have also tried to replace the bootanimation.zip file in the /system/media folder but it continues to try to boot with the same animation file. Is this somehow related or am I replacing the file in the wrong folder? Any ideas what might be wrong? How do I retrieve a log file to help diagnose the problem?
I attempted return to totally stock using XE-Sero7Pro-factory-4.2.1-stock_v2. I booted to Recovery and used adb sideload to install. No errors were reported during the wipe, format and install, but nothing actually got changed. Any ideas?

[Q] DOPO d7020 stuck in loop with mysterious issues

I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.

huawei phone wont turn on

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.

Remix OS black screens during varying parts of first boot/install

Hi there everyone,
Never thought I'd start off a post listing PC specs, but here we go. I have an Inspiron 14 3452 with a dual core Celeron N3050 processor and 2GB RAM. I'm trying to boot ROS from a 2.0 USB on a 2.0 port. I've disabled secure boot.
I've tried this install a few times, the first time dumbly with Secure Boot on. This got me to the flashing boot logo. I turned Secure Boot off and tried again. This time it started to boot but never got to the ROS logo before black screening. I tried a different initrd provided somewhere on XDA, which did nothing. I then reformatted and tried from scratch.
This time it was quick. It blackscreened right after the Android x86 logo. I restarted and tried twice more, stuck on "formatting data partition" before hitting the black screen again.
I'd be happy to provide a log, but I tried using Verbose and can't find a log file anywhere on the drive.
Any and all advice and help is very much appreciated. Thanks in advance!

Razer Phone 2 stuck in Boot Loop

Hello all, I am having some issues after attempting to root my Razer Phone 2. The root failed but I initially had TWRP installed, and afterwards I tried to flash the factory image. This is where things started getting strange; I flashed the factory image and it seemed to run, but then I got a TWRP screen come up that said it was attempting to uninstall something, but that failed. It then went back to the initial boot screen, and then looped between the boot screen and the TWRP screen a few times after which it just resided on the boot screen. I initially was unable to get the bootloader to come back up on the phone but found it was still running in the background and I could interact with it via my PC. I have tried a few more times to flash the factory image but to no avail. I am still in the loop and I am not sure if there is anything that can be done.

Categories

Resources