can not change or load default splash screen - Thunderbolt Q&A, Help & Troubleshooting

I loaded the Bamf 2.1 GB remix on my phone. I used the included toolkit to change the splash screen before the boot animation. Now I want to return to the default splash screen. I have tried the following: Going back to the toolkit and changing the splash screen to the default, reloading the rom, installing a new rom, manually loading a copy of the boot animation file to the system/media folder. None of this has resolved the issue. Any ideas? Thanks.

You need to find the zip file. Then rename it PG051img.zip and place on the root of your SD card. Then shut down and boot into hboot. You'll have the option to flash it, up volume for yes.

Thanks! I found a factory image so trying that now

noodle1278 said:
Thanks! I found a factory image so trying that now
Click to expand...
Click to collapse
where did you find it? i need it too.

http://forum.xda-developers.com/showthread.php?t=1117935&highlight=1.70.605
this is the one i loaded, worked perfectly

Related

Stuck at white splash after flashing!?!? HELP

I've tried flashing over and over, and keep getting stuck at the white HTC splash screen after flashing cm7!?!
I've tried flashing through RM and manually.
What I've done:
Downloaded MR2.5 Radio, renamed to PG05IMG.zip, put on root of sd, reboot to recovery, updated it. Booted into my current rom (Gingeritis 3D) and had a signal and everything. So I renamed the PG05IMG to MR2.5-PG05IMG.zip.
So I rebooted into Recovery, did factory reset, wiped dalvik cache, cache partition, and then went to install zip from sd, and went to the Zoom kernel I had downloaded (which I was told works with CM7),
I then did the same thing with the CM7 update rom image which is: update-cm-7.1.1-Thunderbolt-signed.zip
(I have it in a folder called ROMs, is that ok? or does it need to be on the root while flashing?)
I then reboot, and it doesnt ever get past the white HTC splash screen.
I've done it 3 times, making sure everything is wiped, etc and still get the same thing.
What am I doing wrong?
Can someone give me a link to a CM7/Kernel/radio combo they KNOW works???
I don't know what else to try.
I've Googled it, and found lots of people with the same issue, but find no solutions....
I had been doing everything right, but it seems Clockwork Mod Recovery was corrupt or something.
What I did:
I restored back to my last backup.
Opened Rom Manager
Click "Flash Clockwork Mod Recovery" (the top one, even if it says your up to date)
after it flashes CWM successfully, either download and flash a rom from Rom Manager, or do it manually as I did.
And after the flash, I rebooted, and it went right to the CM7 boot animation, and loaded perfectly.
If you were like me and searched google, and found lots of posts with the same issue, but no solutions. So I hope this helps others.
Thanks for all the help guys!
(goes to show sometimes you just gotta try anything and everything)
Did you flash the radio in recovery? Nooooo thats not how you do it. Rename it to PG05IMG.zip and place it on the root of your sd card. Turn your phone off. And then turn it back on by holding power and volume down at the same time. it will take you to the bootloader and it will ask you if you want flash the radio. I think that might help
Sent from my HTC Mecha using Tapatalk

Bootanimation doesnt change

I installed a couple of custom roms that have custom boot animations and they display beautifully. However I decided to go with clean rom which has the stock bootanimation and I've been trying to change it with a custom one but it never changes. I used the root explorer method, doesnt work, I downloaded one of those utilities on the market to change bootanimation, when I hit preview current boot animation it display my custom one, but when I reboot or even re-import the custom one and reboot it displays the stock one.
I searched but I cant find an answer. Help please? How is it even reading the stock animation with the custom file replacing it?
EDIT: I thought to mention I am using a P7510 16GB

[Q] CWM Touch won't "stick" Galaxy Nexus Verizon

I have been trying to get my rooted Galaxy Nexus to load the CWM Touch recovery image, and I just can't seem to get it to stick. I originally just tried to install the basic non-touch version from Rom Manager. When it rebooted, I got the red ! and a dead robot. So I booted into fast boot, and flashed the touch recovery. After flashing if I go straight to recovery, I do get the CWM recovery and can backup. My problem is that if I the reboot the phone, I can never get back to it again. I always end up at the red ! and a dead robot.
I read on another thread to rename the file "/recovery-from-boot.p" to "recovery-from-boot.p-bak" and that it might require reflashing the image. I moved this file and re-named it, reflashed, booted into android. Then powered off and booted into recover mode, just to see the red ! again.
It seems that when I first flash I can go into it, but anytime after that it just dies. Anyone have a deeper knowledge of what is going on here and care to point me in the right direction? I could probably just go ahead and flash a new image to the phone but I don't feel good doing that while the recovery image seems to need re-imaging every time.
Hi there,
You're correct, you need to rename/delete that file to make cwm stick on the nexus.
If you reboot the phone before removing that file, the file will update your settings to point to the old recovery instead of cwm.
Since you've just renamed it, reinstalling cwm should do the trick.
You're renaming the wrong file. You need to rename or delete install-recovery.sh from system/ect

Installed bootanimation and now it's bricked?

UPDATE: OK I re-installed the Omega ROM again and the default custom animation is running, looks like it will be OK now, so I won't bother trying to change it to a custom animation. I will update post if it doesn't work. Thanks!
I thought I had to install a custom boot animation via CWM.
So I did after I installed Custom Boot Loader via CWM aswell
It said Installation Aborted in the log and when I rebooted, it has a TINY DOT on the top left of screen and rest is black.
I read on Google that to install a custom boot animation I need to rename the file .zip correctly and place it in a folder.
Obviously I did it the wrong way by using CWM!

Bricked, any help appreciated !

Just got back into ROMs again, but made a few mistakes.
I was attempting to install Cyanogenmod
Got the Boot.img file to work, however I realized I didn't add the files to install the ROM, into the SD folder.
(Went into the "install" option on TWRP, but there are no files to install at all)
Now my phone just boots up to the splash logo, and stays there. Any way to fix it?
Note: Already tried RUU, I get the version error like everyone else. I don't know what else to do.
akim33 said:
Just got back into ROMs again, but made a few mistakes.
I was attempting to install Cyanogenmod
Got the Boot.img file to work, however I realized I didn't add the files to install the ROM, into the SD folder.
(Went into the "install" option on TWRP, but there are no files to install at all)
Now my phone just boots up to the splash logo, and stays there. Any way to fix it?
Note: Already tried RUU, I get the version error like everyone else. I don't know what else to do.
Click to expand...
Click to collapse
Create a folder "0" on the sd card and put the file in there. You can also side load in recovery it just takes forever to transfer the ROM.
TheRealDeadApe said:
Create a folder "0" on the sd card and put the file in there. You can also side load in recovery it just takes forever to transfer the ROM.
Click to expand...
Click to collapse
Thank you for the side load recovery. That managed to work, however I encountered another problem.
I am now stuck on the cyanogen 10.1.3 screen, same deal as before.
I've tried everything to solve this:
Deleted cache, factory reset
Made sure I had correct kernal
Etc.
Please, really need to use my phone. Thank you for the help.
Extract the kernel (boot.img) from the ROM file and flash it from your pc using fastboot. Rom doesn't boot is typically due to wrong kernel, maybe it failed to flash from recovery. You are s-off, correct?

Categories

Resources