[EVO 4G Q&A, Help & Troubleshooting] jlmancuso:
First off the evo was officially released in june 2010. Only a few months till we are wishing our evo happy third birthday. Oh I have heard a rumor floating around that the Og Evo is one of the most active devices on XDA.

I have been a member here for a few years. I started with the cricket zio. Then the Og Evo, a 3vo for my girlfriend at the time, and then I fell victim to a boot loop of death. So back to my old a$$ Samsung Messenger II (I had already given the zio to my son as a music/media/911 device) till I could pick up another evo. Found a bad esn hybrid black front/white back og with no battery and seller stated vibration did not work. For $40 shipping paid. Thankfully I didn't sell my 3500 mA extended battery or mid-grade otter box case when I sold my first evo on ebay for $80. Remember it had bootloop of death and also a bad esn.

With some of our phones actually being three years old there are bound to be cataclysmic failures showing up. Over the past few weeks I have noticed a common problem spread out over the massive selection of roms we have. There was nothing really that the roms shared except for the fact that just this one person, never the same one that I can remember, would have this STATUS 7 ERROR during the flash causing the installer to abort. The first couple of times it came up I just passed it over as some wierd error due to something completely different than the real problem.

The following is from a the cm7 unchained thread.

Well with these problems popping up I have been thinking about implementing an old trick. You know about changing partion sizes. We can enlarge the boot and system partions and reduce the data size. We then use a2sd to make up for what we used on the other two. Now all I need to do is add the adjustment to the installer-script.

Although there is a side effect of this. When a different kernel is flashed it will not know how to read the partions. So then the user has to flash another script to change the partion parameters in the new kernel.

Now to shine a light on what the issue is that is causing what seems to be a random problem. The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.

Now with all rom flashing we do just takes another write cycle from the evos life. If we start digging further into the lives of our users we will notice two groups with issues. The older phones (from '10 or '11) and the addicted flashers/developers. Both of which have used up some of their lives testing and flashing.

True be told we can bandaid the evos memory with symlinks to the sdext till we only have the files needed to symlink everything else to the sdext. Only problem will be the transfer rate of sdcard.

Hope this was enlightening and informative. Also if you have not noticed I am working on the TNN Rom toolbox which will help everyone in finding a solving the problems as they pop up.

The thread is in general discussion but only gives highlights of what will be coming. I still have to write the install script to copy logcat automatically to the TNN folder and create a md5sum of the rom flashed. Now I will have to add in the partion adjustments and make a kernel fix script so different kernels can be flashed.

Peace,

Love, and

Happiness