Develop Bugs

[Q] Phone Bricked. Please help!

Okay, so I was unrooting my droid incredible and it brought it to stock 2.1 i was trying to install the update.zip to update it to 2.2, but it wasnt working...so i tried installing the 2.2 RUU onto it...and now when i try to turn on my phone it always boots into the Bootloader...what should i do?
Note: LED charging light still comes on, and i can still go into recovery(stock recovery though since my phone is no longer rooted)
If theres no way to fix it, can i just play dumb and tell verizon its not starting up, because doesnt HTC have to reflash everything anyway for security purposes....the only downside though is they would probably send me an SLCD Incredible

First and foremost, your phone is not bricked... not even close.
Simply try reinstalling the 2.1 RUU. Being that it's signed by HTC, you should be able to do what you need to in the stock recoveryThat being said, your update.zip probably failed because your phone was restored to a state prior to the May OTA. Without being at the correct software version, you cannot use the update.zip to install Froyo.

If you get the bootloader, you should be ok. I think the zip has to be on the root of the SD and named update.zip for the stock recovery.
Sent from my DInc

Look in the android development forum for "the ultimate back to stock thread". download the "PB31IMGxxxxx" file there, rename it to just PB31IMG.zip and put it on the root of your sd card. Go into the bootloader and let it run the update. This will bring you back to a 2.2 stock. From there you can re-root and do whatever else you like.
Sent from my ADR6300 using XDA App

Okay, well it was the get back to stock thread that i followed...and i know that i was trying to do the update.zip from a version of android that was too old, because i was the one who posted a thread a few months back with the update.zip in it. However, i was obviously stupid enough to not save teh "May" OTA and now the link is dead. Some people were reporting however that it still worked without it, so i wanted to see for myself.
In any case, it seems that a 5 hour battery pull seemed to do the trick, go figure. Can someone explain to me what a battery pull on this kind of stuff makes a difference and why the length of time sometimes makes a difference as well?

[Q] Evo bricked ?

I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?

From what you said...yes....I guess its time to plead ignorance and get another replacement
Sent from my nightly EVO

So what went wrong ? I've done this same method about 6 other times with my previous phone and friends phones with absolutely no problems. Any insight so this doesn't happen again ? I'm on my way through traffic to a sprint store to pick up another one and want to root it but not brick this guy too.

My guess would be that it was either interrupted or a bad install...I really couldn't tell you though
Sent from my nightly EVO

tayden812 said:
I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
Click to expand...
Click to collapse
Whenever you flash a radio, NV, or PRI or something like that, when you first flash it, it then tells you that you need to reboot to complete the installation. When it reboots, you will see that odd screen, which will either be an arrow facing down with a phone, an arrow with a box, or some kind of a droid guy with a box or something. That is very important to not pull the battery during that phase (it's when it's actually writing the radio, or pri, or whatever), otherwise a brick is the result, 99% of the time. Never pull the battery during any kind of a radio flash whatsoever. As far as why it told you that the installation was aborted, I've got no idea on that one. Maybe the file you were trying to flash was corrupted, or something to that nature.
If you're sure the battery is charged up, yet you get no LED light when the phone is powered down and plugged in, the phone won't boot to the bootloader, and seems completely unresponsive, then you are most likely indeed bricked. Sorry for the bad news. Don't pull the battery during any kind of a flash, especially a radio, pri, wimax, hboot, recovery flash etc. Battery pull during flashing of important things = bad idea.
EDIT: after thinking about it for a few minutes, after you updated your radio and wimax (which you said updated successfully), did you complete the installation by rebooting? After you flashed the radio, did you reboot, and see the black screen with an arrow coming out of a box, or something like that (that screen varies based upon your hboot version or recovery version)? If not, and you just tried flashing all of them, one after the other, without rebooting inbetween each one...then that may be why the installation of the pri aborted. Then when you went to reboot, it tried to finish the installation of the radio and wimax (which if you didnt reboot initially after selecting to flash, those installations would not have been complete, so as soon as you tried to reboot, it'd have tried to finish writing the radio image, which appears to be where you pulled the battery out)

If I remember right, that screen is part of the radio update. After it flashes, when you reboot you will see that screen. You're supposed to wait until it finishes and it should send you back to the recovery screen. After that you can reboot into the rom.
I'm scratching my head though because you said the installation aborted. Maybe part of it flashed successfully but the rest didn't?
EDIT: Didn't see that the radio flashed successfully. If you can still get to that screen, letting it run it's course should eventually solve the problem.
EDIT 2: K2buckley beat me to the punch. At least I know I was right and not giving you wrong info. Sometimes it takes pulling the battery 20 or so times to actually brick the phone, so hopefully you can still recover.
My Evo + xda Premium App = This post.

Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.

tayden812 said:
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
Click to expand...
Click to collapse
Unfortunately, if its bricked there's nothing that can be done. Since it doesn't turn on, sprint wont be able to tell it was rooted. Just be sure your SD card is "clean", and take it to sprint. See what they say about it. I'd just tell them it wont turn on. Still under 1 yr warranty...
Sent from my PC36100 using XDA App

Great idea. Never even crossed my mind to take it back. I know if they know its rooted they wont touch it which is why I was hesitant to take it back. I'm gonna try that tomorrow, thanks.
BTW - Any suggestions as to a ROM and kernel for absolutely the best battery life without sacrificing any of the Evo's stock options ?
Again, thanks for all the help guys.

Evo vibrates 5X, green light blinks, does come on, can - Please help!

Hi,
I need some help please. Running CM7 7.0.0, using RomManager and ClockworkMod 3.0.0.5. I've been very busy with work and school so have not had much time to play with the phone, so two days ago I wanted to checkout one of the nightlies and installed nightly#101. Then I thought I haven't updated the PRL in a while and dowloaded the stock odexed version 4.20 from RomManager. I updated and then went back to the nightly#101.
This time though everytime I tried to make a phone call I would get a "Call has been lost" message. I figured must be a bug in this nightly or something. So using clockworkmod went back to CM7 7.0.0 backup. That's where my problems started. When the phone came on it was not reading the SD card (I tested it in my girlfriend's phone and it is good, I borrowed hers and the evo didn't read it), I could not turn on the bluetooth and when I rebooted it vibrated 5X and then the green light would blink. I though maybe the battery is dead, so I let it charge for 30 mins and the phone came on. I tried to reboot into recovery so I could reinstall the backup, but it would vibrate and blink, and sometimes it would come on and others not, almost randomly it seems.
Today, I found this fix for the SD card http://forum.xda-developers.com/showthread.php?t=1017387 and it worked.
However, the bluetooth is still not working and can't go into recovery. It seems that the only time I can get the phone to turn on and vibrate and blink is if I 1)put the battery in, 2)Press the power button and 3)plug the power in. Don't know why that works.
Any help would be greatly appreciated!

Recovery works now!
So I turned the phone on, went to RomManager and reflashed clockworkmod and tried to go into recovery from there, but it vibrated and blinked. I took the battery out, put it back in pressed power and vol down together and selected recovery and it didn't work (by the way, hboot.97 and it says s-on even though I had rooted with unrevoked and it was s-off).
I turned the phone back on figured let me try amon-ra since I have an amon-ra created backup in my computer. I turned the phone off, turned on with power+vol down, went to recovery and clockworkmod 3.0.0.5 loaded up.
I tried the reflash my backup and then once it completed, i hit reboot and it vibrated and blinked. Took battery out and put back in procedure again. went back to clockworkmod wiped cache and dalvik (not sure if needed, but figure it can't hurt). Rebooted from Cwm, but vibrated and blinked, and I did my boot up procedure again.
Bluetooth still not working, wifi works, wimax works.
I think maybe I should unroot go back to stock and see if that works. If it doesn't at least I can bring it to sprint and get a replacement.
I love CM7 and don't like Sense or Sprint bloatware.

I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.

HipKat said:
I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.
Click to expand...
Click to collapse
i second that!!!
to the OP....what I would try (as a last resort) is factory reset your phone and unroot (run the 2.2 RUU or any other method that unroots), then try to reroot your phone....and flash Amon_RA as opposed to RM and CWM. then reflash the rooted 4.22 ROM, do your updates of radios, prls, etc. and then CM7....that might do the trick. I'm suggesting this cause you said:
topollillo said:
by the way, hboot.97 and it says s-on
Click to expand...
Click to collapse
and question for ya....you had used Amon_RA but then went to RM and CWM?? why???

I rooted with unrevoked and then installed rommanager. i had then installed amonra, because of what i had read about CWM and the rsa keys backups. but went back because of the convenience when flashing roms.
So now i have discovered that the Usb is not working. I tried the fix in the same thread as the sd card fix, but it did not work.
I'm going to go back to 2.2 see if that fixes it and then follow your steps.
If it doesn't fix then will go to sprint for a new phone
Will report back on what happens. Thanks.

do u have an sd card reader
and yeah amon ra is way better than clockwordmod

back to 2.2 bluetooth not working, usb not working, vibration + light still happening.
If I call sprint to get a replacement phone, they will prob ask me to make sure I have the latest software. should I just accept the OTA and see what happens, or am I risking losing root? Does it not matter?
I don't have an sd card reader, downloaded to phone over wifi.
how can s-on happen automatically. I had rooted and had s-off with unrevoked forever?

Apparently you messed something up, because with s-on, you aren't rooted. I would boot into the bootloader, do a clear storage [factory reset], then try unrevoked again. Make sure you have the hboot drivers, installed then uninstalled htc sync.

Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App

topollillo said:
Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yup, that is fine. Though if the new phone has 2.3 on it, you can't root it yet; if still on 2.2, use unrevoked and good to go.

I had the same blinking light and vibrating probelms on my evo. Mine was overheating really bad. It would run at a constant 102 degrees and when it hit 104 it would shutdown. I called sprint and told them what was happeningand without any questions or problems they sent me a brand new one in the box(non refurbished)
Sent from my PC36100 using XDA App

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?

If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time

Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!

1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?

Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk

plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!

I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...

Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.

And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.

79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.

Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048

Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.

MIUI, for the win, man!

OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.

It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it

stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.

prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.

stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.

HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?

same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

[Q] Battery overheating, causing reboot

Okay, so I'm brand new to this board, so I appreciate any input you can give. I have an HTC Droid Incredible, have had it over a year. Have had the phone replaced 3 times due to excessive rebooting.
I have the OEM HTC extended battery, and have had numerous issues on the battery overheating and rebooting the phone. It seems to happen mostly when using the GPS in the car. Its also happened while excessively texting.
After having the phone replaced three times, I decided to root, and am now on CM7. It was working fine for a couple weeks, then rebooted again. I then took the phone to the Verizon store, and they replaced the battery. The phone still tends to reboot!
Please give me any advice you guys might have. I'm at my wits end here!
Again, Dinc, rooted, on GB, and using CM7.
Thanks!

Undervolt. Use incredikernel and incredicontrol. Drop the minium 25 or 50 and do the same to the Max.
-My life is a shooting range, people never change-

Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?

ari-nj said:
Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?
Click to expand...
Click to collapse
It bricked your phone? Can you give some more details at to what happened?

It just came back on the "HTC Incredible" white screen and did nothing. Had to reboot, and restore.

Well at least your phone isn't "Bricked". If it was your phone would not work period. How long did you let the phone sit? I'm running CM and I have Chad's latest Incredikernel and it runs like a champ! I'm assuming you are running the latest AOSP kernel correct?

I have no idea what an AOSP Kernel is, so I highly doubt I am. Last night, I had my phone in my hand for a few minutes, when to download something from the App Market, and it kept resetting. Do you think I might need to uninstall and re-install the App Market? I'm at a loss here...

CM is an AOSP Rom and needs an AOSP Kernel to run not the sense kernel. If u go to the downloads section at incredikernel.com you will see the AOSP Kernels. Download the latest version and flash it when you reboot just set the phone down and be patient. As far as the app that you installed, what app was it? You can uninstall the app and see if that fixes ur reboots
Sent from my Droid Incredible

I downloaded the kernel, and when I went to flash it from the sd card, I still get the same thing. The white "htc Incredible" screen comes on and nothing else. I've let it run for 10 minutes, then I have to pull the battery and the restore to my last backup. Am I doing something wrong?
Thanks again for your patience, I'm just a little retarded when it comes to this stuff...Btw, I like your sig, I actually sell Jager, so I truly appreciate it!

I just wanted to bump this back up to the top to see if anyone else has any ideas. I did a restore to when I first rooted the phone, and everything seemed fine. However, last night, I was watching a couple Youtube videos, and in about 5 minutes the phone reset.
I have tried to flash kernels, but cannot figure that out, so I'm still using the stock kernel from CM7. PLEASE help, I'm beyond clueless, and am about to throw this phone out the window!
Thanks in advance!

If you are flashing the latest AOSP (Gingerbread) Incredikernel it should work. You can try wiping your dalvik cache in CWM and then flash the kernel again. I have read in many posts that people have waited up 15 minutes after flashing a kernel for there phone to boot. Try that and be patient.

ok so the reason why incredicontrol didnt work is because the stock kernel doesnt have HVAS. so do this.
download :http://www.incredikernel.com/wp-con...php?id=2.6.38.8-incredikernel-gb-11272011.zip
also can you tell me which hBOOT you are running and what radio you have.
to find out what hBOOT you are running please turn of the phone.
once off hold power and vol -
at the top left of the screen please post all that is there.
for radio go into settings > about phone > Baseband Version
please post this info.
boot into CWM do not use rom manager to install.
flash zip above.
reboot and wait. it should take up to 2 min for the phone to rebuild dalvik and boot into the os.
then install incredibcontrol from market.
go to the HVAS tab and lower min by 25 and max by 25.
reboot.
report back please
(note the instructions above will only work for CM7.)

Wow, thanks for all that info! I'm working on installing that kernel now, but before I do anything, I am on Baseband version 2.15.00.07.28
It also says:
Incrediblec XC Ship S-Off
HBOOT-0.92.0000
Mircrop-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010,18:06:51
I will report back later on with my progress.
Thanks again!

I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!

ari-nj said:
I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!
Click to expand...
Click to collapse
What happens when you try to go in recovery (CWM)? Don't freak out, if you can't get into recovery you may just need to reflash it. This can be done with Rom Manager or Hboot.
Also you need to update your radio to a Gingerbread radio if you are using CM7. That is more than likely the reason your phone stays on the HTC screen after you flash the Incredikernel. If you have never updated your radio do some research first or just ask and I'll help you thru it.

I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App

ari-nj said:
I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Go here http://pvillecomp.com/?page_id=18 and download the 2.15.10.07.07 (Gingerbread) radio. All you need to do is name the file PB31IMG.zip and place it on the root of your SD card, basically not in any folder. Just to be safe make sure you don't have any other PB31IMG files on the root of your SD card. Then go into Hboot (Volume down = Power button), just wait (like 5-10 seconds) and you will see that it will auto load the file. When it is ready it will ask you if you will like to install, accept by pressing the volume up button. Let it do its thing, when its done it'll ask you if you want to reboot, hit the volume up button to say yes. Make sure you have a good charge or leave it plugged in to your charger. After you do this wait and see if the phone boots properly, wait like 10 minutes or so. Let me know how that goes...

I'm at a loss here...I did just what you said, and when I get into Hboot, nothing happens....I really don't know what else to do. Is there any way to un-root the phone, and start from scratch? At this point, I cannot get into CWM, and cannot revert back to a restore, so what are my options?

Is your SD card in FAT32 format? You can check on you pc/laptop, just right click on it go to properties. If it is not in FAT32 format you will need to reformat your SD card. Before you reformat it copy everything from your card and paste it to a folder on your desktop. Then reformat your SD card to FAT32, then paste everything back to your card. This could be why your phone is not loading the PB31IMG file (The radio you are trying flash in Hboot).

Ok, stupid me renamed it .zip, as opposed to not...got the radio on there, but still cannot get it to boot into CWM. I feel I'm making a little progress. However, when I go to into Hboot, it still comes up asking if I want to upgrade the radio...It shows Radio 2-15.10.07.07