Develop Bugs

cm7 just wont install

Hello all...I am currently running cm6....everything works great...mytouch slide 3g rooted, and s-off with alpha-rev
I downloaded the cm7 rc2 and the correct gapps as well...gb-20110307....I reboot into recovery, and select wipe data/factory reset etc....I clear cache etc....I then choose install from sd card....pick the cm7....it says installation complete, I then do the same for the gapps...says it installed....then I reboot phone....and it just sits at the s-off alpharev boot screen.....no cm android screen comes up.....ive tried like 5 times now and I wait like 20 minutes each time, but nothing evr happens.....Can someone give me some advice?...what the heck am I doing wrong?.....Thanks so much for your time.....DIrtylarry

Are you running the latest clockworkmod? No clue if it makes a difference, but an idea.

ummm....I think so?.....I guess I dont know for sure.....link maybe?....

Download Rom Manager from the market or make sure its updated if you already have it installed.
Open Rom Manager and hit "Flash ClockworkMod Recovery". Then try again.

Try the 0120 gb gapps, some people have had issues with the latest 0307 ones.

ok....so i reinstalled 6.0 cm and now want to go to 7.....so clockworkmod recovey.....then wipe etc....then 7.0 from sd card.....and then gapps?....what i find weird is that 6.0cm has a yellow status bar that goes across screen when installing, and neither of the 7.0 rc and rc2 have this, and neither will install.......make sense?,,ty

Do you have custom MTD partition sizes setup? If so, it's possible that your system partition isn't large enough..
Have you tried pulling a logcat while booting the phone?
JTB

Had a prob like this once b4 on mt3g and I fixed by putting latest radio....do u have the latest radio 7.15 cux cm7 have wifi calling and hotspot.....just putting in my 2 cent

thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....

dirtylarry10 said:
thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....
Click to expand...
Click to collapse
Do what I do and delete all the ringtones/notfications/alarms that you don't use. What radio are you on?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

CM7 Bootloop problems

Hi
So since yesterday I have been having bootloops problems after installing cm7 nightly 23/25 and was wondering if anyone had insight on it.
Basically after moving apps to sd the phone would get stuck at the boot screen with the circling android guy. at other times it would be stuck at the screen before that and this only happens when I reboot with wifi on.
So far i've tried reformatting the sd card, factory reset, calk's zip to reflash everything.
I use amon ra 2.2.1 and the nandroid restore doesn't work either.
I'm not exactly sure if apps2sd is the problem but after testing doing different things to the phone, I only get this problem after moving apps to sd.
any suggestions on what I can do to get cm7 running again?
edit: oh and the kernels I've tried were sz 2.1 bfs or 2.0 bfs
2.0 worked fine for me on the other nightlies

First I would recommend you do a clean install, then flash the latest gapps.

teh roxxorz said:
First I would recommend you do a clean install, then flash the latest gapps.
Click to expand...
Click to collapse
that's what i did
formatted my sdcard
factory reset, flash calk
then flashed the nightly and gapps from 3-07
it boots up fine first time around. only get bootloops when i move apps to sd or reboot with wifi on. the boot loops are at different screens as well so it's kind of weird

That's pretty awkward. You have enough space, ect to move them. You're not moving any like system files are you?

Are you using the native (Gingerbread/Froyo-style) A2SD, or something like a2ext?
I've got all of my emulators and games on my SD card, no problems whatsoever. :/

yeah i'm not sure what the a2sd style is. just the normal kind that is apart of the cm7? i've never done any extra settings with the external because i just use the stock one.
it's working for now i think but im afraid to add more programs haha. so far moving a few items on nightly 25 with sz 2.0bfs is working with wifi.
we'll see how it goes.
i think i reflashed like 15+ times from 3am till now ugh

Wait, are you having issues when you DON'T use a different kernel?

Well its hard to tell what was causing the bootloops. I don't feel like its a kernel problem.
On my ride from socal back up to norcal today i moved apps individually from internal to SD and rebooted to see effects. I realized it may be because I put the launcher on the SD. I've done it in the past though so I'm not sure why its not working now.
The other change I made was from 2.1 bfs to 2.0 bfs.
It's working for now so ill just be more careful with moving apps to sd
Sent from my PC36100 using Tapatalk

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] Virus' Roms

I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?

DNarsingh said:
I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?
Click to expand...
Click to collapse
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.

drgonzo712 said:
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.
Click to expand...
Click to collapse
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.

You don't need to flash the stock kernel fyi. It's already baked in. He put it there to d/l in case you try an alternate kernel and don't like the results, you can always flash back to stock kernel. Most alternate kernels Bork the camera and our video capability. I have only stuck with the stock kernels, i have no suggestions on alternates.
Sent from my Infected EVO using XDA Premium App.

DNarsingh said:
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.
Click to expand...
Click to collapse
As far as I know, none of the alternative Kernels work 100% since the devs don't have the actual release to rip apart. Most of the kernels were built for Froyo and can run on Gingerbread and Sense 3.0, but like KB112 said it will bork the cam.

I came from CM7 as well, I loved it but I missed sense, this kingdom rom virus is working on is really nice, unless you are a sense hater I recommend trying it. I would also just go ahead and partition your sd card, roms and just getting bigger and bigger and htc still havent figured out that we always need more system space then they give us.

it is not required, but it will give you a lot more space to install your apps from the market

Ok thanks guys, now I guess I just need to get my new card and then I will partition it

Sense 3.0 Roms...cant get past White HTC EVO 4g screen
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.

scorpio1107 said:
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.
Click to expand...
Click to collapse
Not sure of your issues as it both had worked well for me. (though I am back on gingersense b4 until a bit later tonight) You may want to do a bit of reading in the roms thread.
As a side note though the original card is only class 2 (read quite slow) and therefore will not be of much use to run data or apps from anyway. 16gb class 10 cards can be gotten on amazon for about 25 - 30 bones. (maybe cheaper)

Thanks for the response. I was wondering if the SD card was the problem. I will look into getting another one. Just curious to see if anyone else had any ideas.

can anyone help?

i had troubles flashing last night. mine would actually hang on the white evo 4g screen and not go any further. i would pull the battery and reflash and it would work.i must have flashed about 6 or 7 times trying to get everything in order. finally got all the icons to show up and seemed to work right except the weather would crash and the gallery would just show a white screen, never partitioned the sd card though. so now i am loading all my stuff back to the sd card after a partition. there was two parts to the partition, first size i put was 1 gig and the second size it asked for i put 512k. i don't know what each one is for but what do i do after i finish transfering everything back on. just flash as normal? do i actually see the extra partition and put something in it?
from what i saw last night this sense 3.0 is true eye candy. you can't get enough of it. it looks really sexy!

Rooted, Flashed Evo Classic, Loved it... now it keeps rebooting!

I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?

I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.

Did you wipe dalvik? And what recovery are you using?

I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.

Is it rebooting if you don't use that particular app at all?

Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik

Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.

Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.

I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.

Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots

I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.

You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.

Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.

Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you