HTC wildfire not able to boot - Wildfire General

after rooting the phone. i have installed CyanogenMod "update-cm-7.0.3-buzz-signed.zip" and google apps. after rebooting i can only see the cyanogemod animated logo. i have restarted the phone but still the same,
pl guide me how can i resolve the issue.

You got yourself into a bootloop.
To get out of it repeat the procedure you used to flash cm7.0.3 . Just this time realy wipe everything. And i mean wipe system, data, cache, dalvik cache. And try to flash something else. Like a nightly (nightly 119 is the most stable for me). And first boot the system without flashing anything on top (like a nightly then boot into the rom and just after that flash gapps).
Sent from my HTC Wildfire using XDA App

cheekugr8 said:
after rooting the phone. i have installed CyanogenMod "update-cm-7.0.3-buzz-signed.zip" and google apps. after rebooting i can only see the cyanogemod animated logo. i have restarted the phone but still the same,
pl guide me how can i resolve the issue.
Click to expand...
Click to collapse
Re-Flash the ROM.....and select appropiated gapps...!

I wipe factory... and reboot. Working perfect.
Sent from my HTC Wildfire using XDA Premium App

Related

CM 6.1 Stable

Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com

[Q] cant load roms past bootanimation

everytime i flash a rom, it gets stuck at the bootanimation or the setup wizard any suggestions? i used to flash roms before but it started happening recently and i cant pinpoint why it freezes
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
estallings15 said:
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
Click to expand...
Click to collapse
I use 4ext app and do a ext 4 wipe and it seems to work okay for me. sometimes ill manually wipe all partitions but usually dont need to.
Yeah I tried wiping everything
I did factory and cache
Then dalvik
Then under mounts and storage I format system,data,and cache
Maybe I'll try 4 ext
Look at the logcat.
If you have clockworkmod lower than v3, and you flash a gingerbread rom, it naturally get s stucked by bootanimation. But if you have the latest one of the recovery, which supports ext4, and it stuck at the bootanimation (not the white splash screen), then you must wait until the drivers are initialized.
Sent from my Black Ice'd Glacier using XDA App
My cwm is the latest one I believe (5.0.2.0 or something like that)
I tried loading zipnets ice rom and it hangs at the clock animation
I tried the new sense 3.6 rom. (Forgot name) and sometimes it freezes at the bootamimation,setup, or at the home screen
What do you mean wait for drivers to install?
Sent from my Transformer TF101 using XDA
The first start after a rom install is always the longest one. That is usual. Try to wait about three - five mins and then it is done. After that you can use it.
Sent from my Black Ice'd Glacier using XDA App
Also after it boots, give it a few minutes to settle in and turn on mobile netowork ect.
Sent from my Sense 3.6 Glacier using XDA Premium.
How long should I wait? Last time I waited 20 mins and it was still frozen
edit: ok i tried 4ext and used the format everything except sd card and still get a frozen boot animation any other suggestions?
Did you follow Jack_R1's suggestion and run logcat?
so after hours of tinkering around these boards and through everyone's help, i found out i have the bad emmc which is what im assuming the problem is but why was i able to flash roms before? or was it just luck?

a little help, almost there

ok i am learning, i have my bravo rooted now, i have the ginger break on there and all i put the cm-72 nightly rom on the sd card. i booted up with the blue led and held volume down and this is what i got, reboot,boot,system,recovery ,tools and shutdown. how do i get to the sd card for the rom. i dont want to screw up . also is that a stable rom.
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Dr. Orange said:
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Click to expand...
Click to collapse
Yeah, pretty much that.
To answer your other question, yes, that nightly is a stable rom.
I also ported a CM9 release from yesterday over to the Bravo and its working really well in the initial first 24 hours. I'm also an ass who didn't post install instructions either, but they're the same as CM7's which is to install 2nd init, reboot to recovery, wipe data/factory reset, flash rom, flash gapps, reboot. If you're going inbetween releases (like cm7 0605 to say 0610) then all you have to do is wipe cache, wipe dalvik cache, flash rom, flash gapps, reboot.
And if you didn't know, skeevy420 is a freakin' boss and will help with everything you need.
Sent from my Bravo using XDA: Freshmaker

'fixed brick' - now always have to configure settings after boot

Hello,
bricked my defy a few days ago after rom flashing failed. Phone wasn't booting properly, always showing the big red 'M' letter. Fixed it via rds tool, roms are running again but they don't keep the settings.
After every reboot I have to do systems setup again (language, accout, time). It's like having a wiped phone.
What's going wrong? What can I do?!
Few odds:
- can't wipe dalvik cache in recovery. Something pops up very short, couldn't read.
- cannot install apps. Market doesn't start Download.
...
Flashed my rom+gapps again. This time market tells me there's not enough memory on my phone.
Anything's wrong with my recovery? How do I install a new one? Via sndinit again? Any alternatives?
Hi there,
I had exactly the same problem few days back when I tried to make my phone dual boot and wanted to run CM7.2 as primary ROM and CM10 as a test ROM. Experiment failed miserably and the CM7.2 was wiped out and on top of that CM10 was overwritten as primary ROM. Then the same problem as you. It was going through boot loop and every time I had to start the phone setup.
I had to flash SBF using RSDLite and root it again using superone click.
Then installed the CM7.2 again and then later flashed CM10 Nightly just on top of the CM7.2 with out wiping the data.
CM10 I used was Quarx one from Aug 25th and it works great.
I know I am not that smart but I try stuff so I can experience latest stuff.
Not sure if this helps but, let me know if you need more details.
Regards
Kalyan
Sent from my MB525 using xda app-developers app
In the meantime I found out that /data isn't and can't be mounted...
Maybe you should start again with flashing a stock sbf...
Edit: or check out this :
http://forum.xda-developers.com/showthread.php?t=1787541
Sent from my MB525 using xda app-developers app

[Q] stuck on blinking droid screen - paranoiddroid rom

I flashed paranoid droid rom to my nexus.
After first reboot an blinking droid is on the screen - and nexus is stuck on it (now abou 25 minutes).
Whta should I do - my english is poor, so I have problem to find answer 9i'm still looking for it searching XDA foruns)...
Please help....
hmm
IAmNice said:
Have you full wipee before flashing rom? Make sure you do that next time. Just go back to stock and reflash rom
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I had original 4.1 + root + twrp
in TWRP i wiped both cache partition and dalvik cache
then i flashed with paranoid
I didnt factory reset, but in this case (as I think) it was not necessary
Am I wrong?
BTW -stock 4.12 is on board
Going from stock or from any rom to another . I always do factory Reset Format system dalvik and Cache...
With paranoid there are way to many framework changes to do it any other way. Going from paranoid to paranoid say version2.3 to version 2.6 you would only have to wipe as you did..
Paranoid is on the verge if huge changes You might wanna wait until version 3 comes out... Read the last two pages in there thread .
Good Luck..

Categories

Resources