[Solved] Changed boot animation, now I've got blackscreen - Samsung Galaxy Nexus

Hi Guys,
Used the ROM Toolbox to change my boot animation several times successfully (over numerous months). Last change, on the next reboot, I get the Google splash screen, then black. The phone actually boots fine, but you can't properly wake the screen any more. Nothing appears to happen, until you press the power button again, and then you see the screen-off animation very briefly (old style TV turning off) then black again.
Clearing cache/dalvik/etc in CWM recovery doesn't do anything.
Fastboot and recovery work fine. Problem is you can't do anything about the bootanimation.zip in CWM Recovery and there isn't much you can do in fastboot either. Plus my ADB debugging wasn't turned on and you can't easily do this without the screen so I can't modify files. Its definitely the boot animation that caused it though.
I fixed it when I searched for a recovery that allows file management - TWRP http://teamw.in/project/twrp2
Used fastboot to flash this to the recovery partition ( sudo ./fastboot flash recovery ../../Downloads/openrecovery-twrp-2.3.1.0-maguro.img )
Then booted into that recovery. The file is in /system/media but don't forget you have to mount the system partition in the recovery rom before you can see anything under /system.
For me the old bootanimation.zip.old was there so I renamed the current to .bak and then the .old back to .zip
Reboot all good. In case this helps anyone!

Thanks!
Just now this happened to me and was able to reboot into TWRP2 but did not know how I would rename bootanimation, simples: mount system and use recovery file manager under advanced.
Did not know bootanimation could do such a halt in phone boot.

Related

Factory Reset - Now Bootloop

So I was using a cooked MCR ROM, but wanted to factory reset to start fresh. I went into the bootloader and selected factory reset and now it loops the boot animation over and over.
I've tried different ROM's, I've re-partitioned the SD (at one point I was seeing errors about not being able to access Apps2SD) and each ROM will boot up, take a long while on the first animation and then loop itself afterwards.
This isn't a normal boot loop, it doesn't actually reboot, just loop the animation.
Any ideas?
well yes you will need to flash your rom again, can you actually access your clockwork recovery menu by holding down the volume key when the system boots up ?
(fYI, it may come up with the with fastboot screen first)
oooo sorry forgot to mention, youll need to go into the recovery menu and also format the following by selecting mounts and storage before you reflash
- Data
- Cache
- Boot
- System
then once you reflash you should have it sorted, some boot animations do loop on first start up, if it takes longer then say 10 mins then you know its done, unfortunately there is no sure way to tell.
Okay thanks, wasn't sure about formatting boot and system.

[Q] Soft-bricked One-V?

I seem to have soft-bricked my one-v and could really use some pointers.
The things I did to get the phone bricked:
- Unlock the bootloader
- Try to flash miui.
Since this attempt the phone only boots until the "quietly brilliant" screen appears (with a red "This build is for development purposes only..." warning, but I guess this just indicates the bootloader is unlocked right?)
Since then I have installed ClockWorkMod recovery image. This seems to work, I can get in recovery mode and do things like install specific zip files from sdcard.
Unfortunately whatever ROM I try to flash the result is the same: boot until the quietly brilliant screen and then nothing.
For instance, I tried to flash shpongle_primou_20130521.zip (the One-V is the GSM version) using the following steps:
- Download the above zip file
- Extract boot.img
- Copy the above zip file to sdcard using another phone (cannot boot with the one-v so I cannot use it to write to sdcard)
- Put the sdcard back into the One-V
- Start the phone in fastboot mode and connect to USB
- use fastboot to flash boot.img (flashboot flash boot boot.img)
- Switch to recovery mode
- Use ClockWorkMod to flash the zip file
- Reboot the phone
Result: hang in quietly brilliant screen. If I just let the phone alone it seems to reboot every 5 minutes or so.
I fear that I am doing something stupid due to a lack of understanding of some basic concept. Can you guys give me some pointers on how to proceed to unbrick the phone?
it seems u have not flashed the correct kernel for shpongle (the boot img inside zip doesnt work)
try this kernel (ONLY FOR SHPONGLE) http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img
Also do factory reset from recovery everytime u flash a rom( u can backup data via titanium backup)
Also, your command command should be fastboot flash boot boot.img.
Sent from my HTC One V using xda app-developers app
Awesome, I got SHPONGLE to work. Installing the correct boot.img and clearing all data did the trick.
Now I can try to install miui again but I have a stable situation (and backup ) to work with.
Thanks a lot!
I have the same issue with my HTC one V but it is the virgin mobile version ( I live in the east coast of U.S.A.)
Will I be able to use the same solution?
which is the right ROM and Kernel for me?

[c190x] [CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download
Warning! PhilZ recovery is currently in ALPHA stage for Xperia M. Some features may be broken!
Known bugs:
- Half-broken touch (you can use touch, however not select anything) - use hardware keys like in non-touch CWM recovery
- Broken navigation bar
- You tell me
XDA:DevDB Information
[c190x] [CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Sony Xperia M
Contributors
JustArchi
Version Information
Status: Alpha
Created 2014-07-05
Last Updated 2014-07-05
[size=+1]Flashing and updating instructions[/size]
If you have pure untouched stock
Before you begin: Make sure that you have the ROM you want in .zip format and this recovery in .zip format on your external sd card. If you don't have one, on your internal.
1. Install Towelroot APK.
2. Launch it, click on magic button, bah, you're now rooted.
3. Make a backup of your TA partition using i.e. Backup TA. DON'T SKIP THIS STEP, or you will lose your warranty forever. You need root for this step, so don't try it without 1 and 2.
4. Get familiar with fastboot.
5. Turn off your device.
6. Hold Vol-up button, don't release it.
7. Plug your phone to your PC, while you're holding Vol-up.
8. It won't boot (black screen) but LED should indicate that device is turned on.
9. Execute fastboot -i 0x0fce getvar version. Use fastboot.exe instead of fastboot if you're on windows, do the same for all fastboot commands, you should already know it.
10. If you got return value, such as "0.5", you did everything correctly, congratulations! If you did not get return value, don't go further until you get it, because your fastboot connection doesn't work.
11. Get bootloader unlock code from Sony here. You can view your IMEI with *#06# code if you need it.
12. Unlock bootloader with fastboot -i 0x0fce oem unlock 0xCODE where CODE is the code from Sony. I.e. if you got "ABCD0011" code on your e-mail, execute fastboot -i 0x0fce oem unlock 0xABCD0011
13. You should get response like "Okay".
14. Extract boot.img file from the zip you downloaded from this thread. Put in the same directory as fastboot.
15. Flash boot.img with fastboot flash boot boot.img.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
18. If you did everything correctly, you should have booted custom recovery right now.
19. Enter "mounts & storage", and format: /system /cache /data. If you don't have anything important on your internal sd card, I strongly suggest to format /data and /data/media as well.
20. Flash any ROM you want
21. Remember that your ROM will overwrite your recovery (kernel), so if you want to preserve recovery, flash this zip right after every ROM flash.
22. Finally, reboot, be patient, you shouldn't get any bootloop.
If you already have CWM, TWRP or any custom recovery installed
1. Simply flash this recovery with install zip option.
I'm using CM11 (Free Xperia) with CWM Recovery , is it possible to install this recovery on the current? would it be possible to make any kernel related issues? (phone not booting up and else).
bugggmenot said:
I'm using CM11 (Free Xperia) with CWM Recovery , is it possible to install this recovery on the current? would it be possible to make any kernel related issues? (phone not booting up and else).
Click to expand...
Click to collapse
This kernel has been only tested on my private ArchiDroid 2.X build (not public yet), but it's based on FreeXperia sources so it should be compatible with all CM11 ROMs that don't need any kernel-ramdisk-based changes, including your CM11.
In case of issues you can always reflash, as this recovery boots and works properly, apart from some functions we're currently fixing with Phil.
JustArchi said:
This kernel has been only tested on my private ArchiDroid 2.X build (not public yet), but it's based on FreeXperia sources so it should be compatible with all CM11 ROMs that don't need any kernel-ramdisk-based changes, including your CM11.
In case of issues you can always reflash, as this recovery boots and works properly, apart from some functions we're currently fixing with Phil.
Click to expand...
Click to collapse
I also tried to build Philz and was succeeded, but it has same issue. I contacted Philz he told to me to enable Axis parameter in BoardConfig.mk but still the same. What you think, why this issue is caused? Due to faulty Touch screen events?
icoolguy1995 said:
I also tried to build Philz and was succeeded, but it has same issue. I contacted Philz he told to me to enable Axis parameter in BoardConfig.mk but still the same. What you think, why this issue is caused? Due to faulty Touch screen events?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53933204&postcount=4745
Failed to download ..
Can u give me mirror link like dev-host, mediafire, etc?
Edit: ok now fix
Edit again: i get bootloop, after flashing your phill touch -_-
itsnie said:
Failed to download ..
Can u give me mirror link like dev-host, mediafire, etc?
Edit: ok now fix
Edit again: i get bootloop, after flashing your phill touch -_-
Click to expand...
Click to collapse
Why you shouldn't get bootloop? It's only for CM11.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
Click to expand...
Click to collapse
Upto step 16 was okay. 17th step won't work. Device is not getting into recovery mode when volume key is pressed.
no thing changed
JustArchi said:
[size=+1]Flashing and updating instructions[/size]
If you have pure untouched stock
Before you begin: Make sure that you have the ROM you want in .zip format and this recovery in .zip format on your external sd card. If you don't have one, on your internal.
1. Install Towelroot APK.
2. Launch it, click on magic button, bah, you're now rooted.
3. Make a backup of your TA partition using i.e. Backup TA. DON'T SKIP THIS STEP, or you will lose your warranty forever. You need root for this step, so don't try it without 1 and 2.
4. Get familiar with fastboot.
5. Turn off your device.
6. Hold Vol-up button, don't release it.
7. Plug your phone to your PC, while you're holding Vol-up.
8. It won't boot (black screen) but LED should indicate that device is turned on.
9. Execute fastboot -i 0x0fce getvar version. Use fastboot.exe instead of fastboot if you're on windows, do the same for all fastboot commands, you should already know it.
10. If you got return value, such as "0.5", you did everything correctly, congratulations! If you did not get return value, don't go further until you get it, because your fastboot connection doesn't work.
11. Get bootloader unlock code from Sony here. You can view your IMEI with *#06# code if you need it.
12. Unlock bootloader with fastboot -i 0x0fce oem unlock 0xCODE where CODE is the code from Sony. I.e. if you got "ABCD0011" code on your e-mail, execute fastboot -i 0x0fce oem unlock 0xABCD0011
13. You should get response like "Okay".
14. Extract boot.img file from the zip you downloaded from this thread. Put in the same directory as fastboot.
15. Flash boot.img with fastboot flash boot boot.img.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
18. If you did everything correctly, you should have booted custom recovery right now.
19. Enter "mounts & storage", and format: /system /cache /data. If you don't have anything important on your internal sd card, I strongly suggest to format /data and /data/media as well.
20. Flash any ROM you want
21. Remember that your ROM will overwrite your recovery (kernel), so if you want to preserve recovery, flash this zip right after every ROM flash.
22. Finally, reboot, be patient, you shouldn't get any bootloop.
If you already have CWM, TWRP or any custom recovery installed
1. Simply flash this recovery with install zip option.
Click to expand...
Click to collapse
i installed it by cwm and by fastboot and cwm still exist

Cannot boot in TWRP Recovery!

Hello,
So today I got a nice surprise. It looks like I can't boot into TWRP recovery no matter what, but I can in Stock one.
Yesterday I changed /data filesystem from ext4 to f2fs and the ROM flashed works fine.
Everything works fine but not the recovery.
If I try to boot into it then it shows me the TWRP logo for 3 seconds and after that the phone reboots into ROM. If I chose from reboot menu to boot in recovery then it becomes an infinte loop trying to boot in recovery and rebooting over and over again.
Any idea what can it be!?
Other recoveries cannot acces /data.
Try this:
Open Odin 3.07 and uncheck everything except f.reset time;
connect phone and flash TWRP;
when you see the word "Reset" in the status window, remove use cable, remove battery, replace battery, use button to boot into recovery.

OnePlus 3 bootloader defaulting to recovery

Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone

Categories

Resources