i was on comrom 2.1, went into cwm wiped data, cache, factory reset, then restored my stock verizon rom. my reason for doing so, is so that i can sell the phone with it looking as stock as possible without actually getting rid of cwm. so it works fine except for one issue, the custom boot screen (it just says android , except that it is messed up and instead of showing horizontally, it flashes vertically) that was on com rom is somehow stuck flashing over the stock boot screens (samsung galaxy s and the verizon logo), is there an easy fix for this? or should i return everything completely to stock?
Thanks for any help!!
You may have a problem if you were on a voodoo setup and just flashed the stock rom with out removing the lag fix...?
My suggestion is to odin dl09 with the atlas 2.2pit file and repartition checked and reboot when its done,
Then ota update to the one you want.
at this point you can power down and odin the recovery you want but you have to have a non stock kernel ready to go on your sd cause if you don't flash one the first time your in recovery, the stock kernel will overwrite it on boot. In the dev stickies there is a list of roms...you can find a non stock, non voodoo kernel to work with stock rom, flash that on there the first time you boot into recovery to make sure cwm sticks.
Sent from my SCH-I500 using XDA App
I searched for a thread like this but couldn't find one similar to my issue. I rooted my Thunderbolt and used ROM Manager to update to the latest Cyanogen Mod 7 Gingerbread flash. I ran the update and now I'm stuck at the boot screen where the blue Android is on the skateboard. It just keeps playing the animation over and over again.
Any ideas on how to get my phone to boot up? Appreciate the help!
Figured it out. I pulled the battery, and rebooted into recovery, then wiped all the data, and rebooted and it booted right up....
Hello.
After running for months cm7 old baseband with no prob, today i decided to try cm9.
So i grabbed my copy of Arjen cm9, latest nightly, gapps, installed it. Then upgraded to new baseband 20G using LGMDP.
The phone booted, all fine, but there was no network. So i tryed reinstalling the new baseband, same story. The third time i reinstalled the new baseband, phone booted with stock lg gingerbread. So i reinstalled arjen cm9, but phone remained stuck at boot animation at the firts rebooot before installing google aps.
Then i decided to restart the process once again and redoing root, recovery etc. These are the step i took:
1) used KDV to reinstall lg stock ginger with 20G baseband.
2)rooted from gingerbread, installed rom manager, installed CWM.
3) reboot in CWM, wiped all, formatted with ext size 256mb and swap size 64mb.
4) copied rom and gapps, wiped everything another time.
5) installed arjen cm9, re booted, again stuck at boot animation.
6) re formatted, re wiped, tryed another rom ([2012.6.5] MIUI PORT by DHK).
7)rebooted, again stuck at boot animation.
No matter how many time i reboot or how many CM9 version i try, after the new baseband upgrade only the lg stock gingerbread seems to boot without remain stuck at boot animation.
Please help me with this new baseband/ cm9 thing, because i seem the only one that doesn't get it!
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Madpiercing said:
Hello.
After running for months cm7 old baseband with no prob, today i decided to try cm9.
So i grabbed my copy of Arjen cm9, latest nightly, gapps, installed it. Then upgraded to new baseband 20G using LGMDP.
The phone booted, all fine, but there was no network. So i tryed reinstalling the new baseband, same story. The third time i reinstalled the new baseband, phone booted with stock lg gingerbread. So i reinstalled arjen cm9, but phone remained stuck at boot animation at the firts rebooot before installing google aps.
Then i decided to restart the process once again and redoing root, recovery etc. These are the step i took:
1) used KDV to reinstall lg stock ginger with 20G baseband.
2)rooted from gingerbread, installed rom manager, installed CWM.
3) reboot in CWM, wiped all, formatted with ext size 256mb and swap size 64mb.
4) copied rom and gapps, wiped everything another time.
5) installed arjen cm9, re booted, again stuck at boot animation.
6) re formatted, re wiped, tryed another rom ([2012.6.5] MIUI PORT by DHK).
7)rebooted, again stuck at boot animation.
No matter how many time i reboot or how many CM9 version i try, after the new baseband upgrade only the lg stock gingerbread seems to boot without remain stuck at boot animation.
Please help me with this new baseband/ cm9 thing, because i seem the only one that doesn't get it!
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Click to expand...
Click to collapse
What do you see when you're booting your phone?
Fastboot Mode? Stuck at LG logo?
Sent from my LG-P500 using xda premium
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Click to expand...
Click to collapse
when you see the battery logo..hold power button again..and your phone will boot normally..
If dont works so go to recovery a and from cwm reboot system..other way to start the phone..
LG-P500-ICS-4.0.4
I've done it guys.. I had to install again gingerbred and 20G with KDZ, then re rooted, donwloaded rom manager, installed CWM, and then i installed again CM9 and it worked.. dunno what's gone wrong last time, i have done the exacts same steps and now it works!
Thanks for the help
Well, this is what happened.
My phone was using cMiui 4.1.2 with the default kernel, and this morning I tried to flash CM7. I wiped everything as always before flashing, after I pushed reboot system and it got stuck in the "Galaxy s2" screen and keeps turning on and off endlessly.
I pulled out the battery, try to get back into recovery, but it hadn't been a successful attempt.
I stayed claim and flash back to stock 4.0.4 via Odin, god-bless I made it through.
I installed a custom kernel and flash to CM9 for temporarily use. Now I don't know what to do.
I really want to try the taste of CM7, please help.
Edit: I also tried various way of flashing, such as flash a codeworkx kernel before flashing, and flash back into GB 2.3.5 before flashing CM7, both didn't work out
it was making me crazy for weeks and here is the solution i found 5 minutes ago :
when it gets bootloop
go to download mod and flash siyah 2.6.14 via odin!
then it boots.
I tried ODIN and successfully got it back to stock rom. But the phone keeps looping back to the Vibrant logo screen. The method I used worked for me for the past three years, it started acting weird when all of a sudden an ICS custom rom from MIUI hanged on me. And then I was unable to get my phone working!
Is my phone permanently bricked?!
MiniGunnR said:
I tried ODIN and successfully got it back to stock rom. But the phone keeps looping back to the Vibrant logo screen. The method I used worked for me for the past three years, it started acting weird when all of a sudden an ICS custom rom from MIUI hanged on me. And then I was unable to get my phone working!
Is my phone permanently bricked?!
Click to expand...
Click to collapse
Can you get into recovery? Did you flash a custom gb boot loader? You wipe data and cache? You could try Odin again and flash stock with the correct pit file and re partition checked I've done this many times and have not had this problem you might just have had a corrupt flash like I've read Odin has been known to fail