View Single Post
  #3642 (permalink)  
Old 08-27-2010, 07:02 AM
jelive's Avatar
jelive
PPCGeeks Regular
Offline
Location: San Antonio, Texas
 
Join Date: Nov 2008
Posts: 104
Reputation: 140
jelive is keeping up the good workjelive is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: OMJ's HTC EVO 2.2 Custom ROM v3.0 | FroYo 3.26.651.6 | *Updated 8/13/10*

Quote:
Originally Posted by iknowsquat View Post
Weirdness for sure. So how do you recover from the boot loops? Battery pull and then the next boot is ok or does it take a few attempts to get it to go?
It IS a boot LOOP right? Not just a long boot TIME? (Just checking)

You reflashed amon but how? Via ROM Manager? Have you tried flashing amon manually as it's decribed in FastRX8's root tutorial?
http://forum.ppcgeeks.com/showthread.php?t=123714
Step 2K or 5Z (same thing)

Looking at all you've done, a common denominator is your SD card. The card itself could be bad or maybe just a rotten file.
If you havent already then back up your card and then reformat with fats32.
Load the card into your device completely blank and reboot. Once the card is prepped by the phone try and test the stability.
If that takes care of the boot loops you're all set but potentially have a rouge file on your card. Be careful with how quickly you put files back onto your card so you dont put a funky one back and return to Boot Loop City.
Thanks for input and suggestions.

I usually pull the battery, go back into recovery, re-wipe, and if lucky it will then reboot OK. Makes flashing stuff not a fun adventure sometimes.

Flashed Amon RA manually through fastboot. Just redid it again to make sure I had a "good" flash.

Have not tried SD card deal...will do that if problem persist.

Thought of something last night to look at...I had SetCPU enabled at boot and looked at my profile settings...I had apparently OC'd to 1152 on a couple settings. I generally UC, not OC...guess I screwed up in rush way back when. This could potentially cause problems at boot couldn't it? Well, fixed nevertheless and will find out today when I flash something new...perhaps an updated kernal
Reply With Quote