Develop Bugs

Anyone got anys ideas on whats wrong with my TP2???

I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.

Shaolinstyle said:
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Click to expand...
Click to collapse
Are you able to re-do the Hard spl?

Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.

Shaolinstyle said:
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Click to expand...
Click to collapse
I know this sounds obvious and dont take it the wrong way but are you sure that the rom you are trying to flash as been unzipped properly and is named correctly. Try re-downloading a fresh rom and unzip it and rename it Rhodimg.nbh and put it on the root of your Sd card and try flashing it from the card. Also is the battery charged?

I am certain that the roms that I have been using are unzipped and named properly, there was actually a flahed rom on this phone that was workig fine until it started resetting with the rom on it, I wasn't updating or anything when it started to act up. Plus I use the same roms on a second TP2 which are working fine. I did try now to flash from my SD card, Hard SPL said it installed correctly but when I rebooted phone its doing the restart thing over and over still. Battery has been at 100% or close to for all flashes.

[Problem] Touchscreen Issues/ Software related?

Okay guys this one has been screwing with me for a while now and is getting progressively worse.
I have a launch day EVO 0002 hardware and I believe an Epson panel but don't remember that one 100%
My evo was running great up until the 31st/1st. I put on a CM6 rom and a snap kernel. Phone was running fine then started lagging horrible so I did a reboot.. Phone went into bootloop. So I went into recovery wiped data/ cache/dalvik 2 times (clockwork recovery).
Restored the phone to Freak E Froyo which I had been running for 2 weeks. Next day I tried the senseless Freak E Froyo and wasn't as much of a fan of it so I installed AVA v6(then flashed king kernel 8 over the top) then the touchscreen issues arose. My screen would think it is being touched when it is not pages would flip, apps would open and no buttons would work. When i hit the home button it opens whatever is on the left of the screen and when I push the back button it opens whatever is in the middle of the screen.
So I nandroid'ed to My Freak E froyo after wiping all again. Still did it. Flashed CM6 6.0.0 after wiping all. Still same problem but worse and even more noticeable on CM6 .
I then switched to AMON RA recovery, tried the same thing: wiping all 4 times, reinstalled CM6, same problem.
Tried reinstalling stock 2.2 odexed and rooted was fine until about 5 hours after running then almost every time I could only use the phone for about 6 seconds and the touchscreen would become unresponsive...
I am thinking it is a piece of a kernal not flashing correctly so It is causing problems maybe?
If not that do you think it could be a CPU problem itself? Maybe going out and unable to hold up anymore and causing freezing?
Any suggestions will be tried. If not work then...I will most likely try a 2.2 RUU and format my sd card and see if that does anything.. and lose root/nand unlock

Yes my v002 EVO had the same issue and all 002 are novatek but I dont think its a screen problem.
I gave up trying to figure it out but I know with mine if I ran ANY rom that came out before the 1.47 OTA then it would NEVER have this issue..
If I ran ANY rom after the 1.47 OTA then it would always do it..Sometimes it might take hours for it to happen but it will..I'll bet yours is probably the same way.
The offical HTC 2.2..yup same thing
The offical HTC 1.47 OTA..yup same thing and this is when it started.
I wiped/flashed/wiped whatever you can think of and the problem NEVER went away on any newer ROM's but as soonas I load a older ROM it never happened.
Look for the EVOlution v9 ROM..Its the ROM I ran until I exchanged the phone..I'll bet if you load that ROM you won't see a single touch screen issue.
Just my 2 cents but save yourself the headache and exchange that damn phone..

That is what I will most likely do tomorrow. Will take it back to stock to do it tonight but it is just weird because I never once had a problem until the bootloop. My buddy who has an evo we got em at the same time store ..etc.. His alot of times will do this and he is not rooted or anything...Just hoping they dont give me any problems tomorrow at sprint...

2.29.405.2 update bugfest - any way to roll back?

Did the 2.29.405.2 update OTA initially and noticed problems. So reinstalled it from SD card but no help.
Bought sim free, unbranded/locked and never rooted:
Cannot dial out from phone lists or contacts. Going to phone and clicking on an entry in the call list does not launch phone call any more. Going to contacts, opening one and clicking on an available phone number does not launch phone any more.
The only way I can make a call is to punch it in on the keypad! Grrr.
Wifi connects to my home base after a reboot but, after an undetermined amount of time it drops the connection and cannot get it again. Going to Wifi settings shows it scans, connects and tries to obtain IP address. After a short time it gives up, turns wifi off and starts over. Again & again.
Cannot get it to connect again without another reboot.
This is a crippling loss of functionality for me. Can anyone suggest a way to roll back this update so my phone works as id did?
Many thanks all,
M1

First try a hard rest(you will lose all personal data on the phone,pictures and other stuff on the SD will be fine). If that does not work try either the 2.29.405.2 or 2.10.405.2 RUU.

More info - to my horror, around 15 minutes after I had tried and failed to make calls from contacts the phone started making them one after the other as if they were stuck in a spool or something! Ouch - any thoughts?

Backup everything you can and flash the same ruu from shipped roms.
Sent from my HTC Desire using XDA App

> flash the same ruu from shipped roms
where do I find this? - android noob!

http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
And if it works, keep it safe!
Sent from my HTC Desire using XDA App

Thanks to all for help on this. Decided worth a trouble shoot before a hard reset and culprit seems to have been an app - extended controls widget. Removed this and all seems well again.

Try this one. This definately works! i have used it.
http://forum.xda-developers.com/showthread.php?t=768256
I was stuck at 2.29 update.
Then i used this guide and windows tool.
So i did this process and it rolled my phone back to stock android 2.1 rom 1.X
The first version that the phone was bought with.
This tool will boot the phone into bootloader and load a stock 1.x rom ota off the sd card as the tool will extract it to sd card and then load it.
This will wipe all your data not sure about the sd card as i dont remember any of that because i formatted my sd card after i had used the tool.
Thats because i had rooted my phone and tried custom sense hd rom.
The only reason i had was of the battery usage as the consumption was very badly increased and that the 2.29 rom was unstable.
PS: I did first try the htc service in Denmark. They couldn't help me and said i was stuck with the 2.29 rom update. :/

After my phone got rolled/flashed back to stock android 2.1.
The next day in the morning i could upgrade again to android 2.2 rom ver. 2.10 OTA from htc servers.
Maybe this works for you as i did for me and others.

Turns out it wasn't the app.
After a couple of days playing ok my sim free stock htc desire is unstable again.
Cut me off mid call - went to phone and clicked on last call entry - absolutely nothing happened, repeated with same problem. Exited phone to home screen then opened contacts and tried to make call from there - same behavior, a complete hang.
No web access either so opened wifi manager to find it hanging on "obtaining IP address" from my home network and continually shutting down and restarting wifi automatically at this stage.
Noticed general UI lag and several apps failing to open too.
Left phone alone and again, around 10 minutes later all of the actions - including trying to make the phone calls started running one after the other. Like everything had been caught in a spool or something. After this all seemed OK until it happened all over again later.
Although the UI seemed OK and some apps worked as expected, the only way to get phone and wifi working whilst it was hung was a warm boot.
Dreading a hard reset as it's going to waste another day or two getting everything reconfigured just so (can't find a back up solution that does everything - multiple mail account settings etc) but looks like only option.
Will try going back to mikep99's suggested rom as soon as I have time and will not be responding to an HTC OTA auto update offer again.
Grrr.

I still suspect an app conflict.
Can anyone recommend a util that might give me a clue which app / sys process could be hogging system / radio resources?

just got another OTA update pushed to me. installed (nothing to loose) and Congratulations my phone has been updated to 2.29.405.5.
Not sure whats going on here as that was the update I got 2 days ago. This time round it was only 4.8mb download so I'm assuming it's an update update. Hope it fixes things .....

[Q] Rooted Inc2 Keeps rebooting

So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?

WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
Click to expand...
Click to collapse
Bumping, no one seems to be able to tell me a thing on what this means, what can be done to fix, etc. Any help is appreciated.

Wipe cache, dalvik, and system, then flash a different ROM.
If it continues after that then its likely the phone. And nothing to do with root.

WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
Click to expand...
Click to collapse
Any chance you can take a picture of said screen?
What's weird, it sounds like you're describing the stock recovery screen. But you're still able to access CWM?
You probably want to update CWM on the phone and see if that helps out, one thing you want to do instead of changing kernels is re flash the rom again. Once it reflashes wipe data/cache (Do a factory reset basically) as well as the dalvik cache and boot into the ROM without restoring anything.
Just sign into google and see if it stays up and stable at this point, if it does something that's being restored is probably the culprit or a bad app that continuously tries to run.
By the way, the phone comes with stock sense 2.1, above that is sense 3.0
2.3 is the version of android that runs behind sense. Either 2.3.3/2.3.4/2.3.5 are all versions of gingerbread.

Try a different rom, if it continues, it's probably a hardware problem. My wife's first Incredible rebooted constantly, probably upwards of 2 dozen times a day. We had it replaced and the new one has been fine.

Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)

I thought I read some where that other INC2 users were having similiar issues and it was due to the new android market OTA update.
Edit: Nevermind the other thread here in the forum suggests it could be some kind of HTC OTA update that is messing things up.

WorldOfJohnboy said:
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
Click to expand...
Click to collapse
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?

klarson said:
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
Click to expand...
Click to collapse
I am in the process now, but I have had a GB/Sense 3.0 ROM as well as stock GB Rooted, both have ended up doing the same thing. I think I am going to manually cancel the OTA after flashing a new ROM to see if that will stop it from automatically doing so (if that is the issue).

Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.

Conduitz said:
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Click to expand...
Click to collapse
It's not the new market. It has something to do with the OTA's on your phone. Regardless if the OTA was actually downloaded onto your phone or not it's going to fail because the stock recovery is no longer the default recovery which is one of the prerequisites it needs to install.
A wipe is needed to keep this from happening, at least load up the gingersense ROM and that should get rid of the temp OTA file that was downloaded to your phone.

jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.

WorldOfJohnboy said:
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
Click to expand...
Click to collapse
What i'm hoping is that the OTA files are on the phone and will get wiped with a new ROM. However if they're stored on the SD card all the wiping in the world won't help.
I'm not sure where the OTA files are stored and would like someone to verify for certain if that's the case. I'm just speculating right now on where it's stored but I know the market update is done just like the apps not an OTA.
I also know that the OTA will prompt you for the download. You know the whole download and install now or install later deal?

Well, did a wipe of all things (twice) and installed my fresh ROM. This time after installing all my Apps and doing my restores, etc, I went into the Settings under Software Update and did a check new, it says "No New Software Update Available." Also, under status, it just says the Source is Verizon Wireless, the rest are blank. (I believe at one time, all the fields were populated.)
I am holding out hope that this will work for us. Anyone know of a piece of software, etc. that will log all of the phone's operations? I am curious to see if it is trying to auto-update with OTA software updates.

I'm having the same problem. I can't even get it to wipe because when I start in recovery it goes straight to do you want to start update and if I try to start the phone it restarts and I get the exclamation point. Anyone have any ideas? Thanks!

Update
I took the sd card out and was able to boot to recovery and do a wipe. Phone is working normally for now, how would I go about disabling the OTA's so it doesn't happen again?

I can confirm this is being caused by an ota update. Have 2 inc 2's and both locked up. Both running rmk gingersense. Fixed by clearing cache and davlik. Rebooted phone and saw failed ota update error. Renamed otacerts.zip until rom is fixed. Otacerts is located in /system/etc/security.

[Q] Constant reboots after ROM flash

Hey, guys!
I am in a desperate need of help. Here's my situation:
I've got an HTC Desire (obviously), which reboots every time the ROM starts. It all began after I decided to move back to a Sense ROM after having been testing ICS for the past couple of weeks. So, I flashed RCmix S - a ROM I knew to be stable and working snappily on my phone. Everything went well, I restored my apps with Titanium and then decided to remove some of the junk stock apps. When this was done, I restarted the phone, only to be faced with a series of reboots every time I got glimpse of the Sense UI (i.e. seconds after unlocking the SIM card).
I thought this might be a ROM-related issue, so I tried another one - Supernova. Same thing. Tried flashing it several times after full wipe always. No luck.
During the whole process I switched HBOOTs a few times - from stock, to Fatsys (IN2SD), back to stock. Tried several recoveries (AmonRA, 4Ext touch).
Even flashed official RUUs at least 3 times in order to get the phone back to its factory state. Once the stock ROM worked fine. Then I went on to root it and tried flashing one of the customs ROMs again, which, predictably, began rebooting just after SIM unlock.
I thought this might be connected to problems with the SD card, so I reformatted it completely - 6,8 GB FAT32 + 1 GB Ext4, using GParted. All by the book.
No I've got a clean SD (removed all the previous folders), but it doesn't seem to solve the problems.
Can anyone, please, think of something that I could do in order to get my phone back?
P.S. I forgot to mention, that my phone is S-Off. It struck me as strange, though, that it stayed S-Off even after flashing the RUUs.
New development: this morning, after successfully creating a Gold Card, I went on to try and flash a 2.2 RUU again. This time, however, the installer announced it was unable to access certain files and thus the flash process had failed. Meanwhile, the phone itself displayed a triangle and an exclamation mark on the 4 corners of the screen. I no long can access Recovery or the Bootloader. Help me, please!
Never mind, I managed it myself.