haha blunt but useful.

I didn't ever get involved in the whole radio stuff. I figured that would make or break a rom... if it's slow.

Originally Posted by ricsim78

I decided to write this to clarify a lot of the misconceptions around here. This is also good information for people who are new to modding their phones, the Evo in particular. I see a lot of the same questions being asked over and over so here is some information that some may find useful. I will also warn people if I know that what they are doing can potentially destroy their phone or cause it to stop working properly.


RADIO/WIMAX/PRI/NV UPDATES: I see a lot of questions concerning this. Like, "Oh wow, the new HTC build # 3.29.651.5 is out. I installed it and for some reason I still have the same Radio and PRI. What version should I have?"

Answer: The same! Funny thing is a lot of people asking this question have flashed a few ROMS and should know the answer. But still, updating any of the 4 stick regardless of what ROM you are running. Once you flash them, those are the versions you have until you re-flash to update them. ROMS and any of the 4 updates are a separate entity. (ROMS CAN contain radio updates within them, but none that I have found that are not custom have radio updates built it. It is just possible to do, for arguments sake.)

WARNINGS: KNOW THE DANGERS INVOLVED WITH WHAT YOU ARE DOING

1. Flashing radios from another handset can make your Evo stop working correctly. Only use radios made for an Evo. Period.

2. Common knowledge is to always use the latest radios for the best performance, battery life, and signal. I see this in a lot of ROM threads. While true, radio updates and the like can be tricky at times. Make sure you do those updates separate from any other installation. I do not recommend doing a ROM and radio flash at the same time.

3. Did you know flashing your Radio can break 4G? It can. Each phone has a unique encryption key for the 4G. So let's say Grace buys an Evo and I want her radio update. So I take the update off her phone and add it to mine. Well, it will probably work, but there is a chance it will overwrite my keys and then what happens? Well, if Grace is using 4G, I cannot use it at the same time since we have the same keys now! Now you have two handsets with one set of keys. There is a way to fix it (will update with link soon) but still, did you know you can mess it up?

4. While it is always best to use the latest, I suggest EVERYONE (regardless of anything else) should have a copy of a rooted 2.2 ROM. This way you can at least restore your radios to a working state in almost every case.

5. While there might be fixes out there listed (if you do screw it up), do you have the ability to use them? What if that fix does not work on your phone?

6. Ivide Infra brought this up, "Doesn't a Nandroid back up everything, including radios?" No it does not! I read that there is a way to back radios up using Amon RA recovery but not sure if it is true or not. I cannot seem to find that post again and I looked (didn't look hard, but still). This is a good example of a situation where you think you have a safety net but may find out there is none if something goes wrong.

The moral of the story? Read up on something before you do it, especially if it is something you are trying for the first time.


What ROM works best for me? I see this a lot.

Answer: I don't know, nor does anyone else. This is like asking your buddy at the party which girl you should try and hook up with.

You have to try a few because we all have our preferences. (ROMS, not the women!) Some like Sense, some hate it. Some want a stock ROM with added features, others want a totally customized ROM that is radically different that stock (like CM6). You know you have the right ROM when it has everything you want and everything you use works. You have to try as many as you can until you find the right one for you.

A better thing to do is tell people what you want in a ROM and ask what ROM they suggest after they get an idea of what you are looking for. Try their suggestions but still try a few that seem to be what you are looking for. The first post in all of the ROM pages on here have detailed information about the ROM; read up and find out what the ROM has to offer. If you need your phone for important stuff (like work), I highly suggest you do not use a RC (release candidate) or especially a Beta ROM (unless the description claims everything works). It may decide not to work at the worst possible moment!

If you are happy with your phone at stock yet want to have the benefits of being rooted with super user ability, use a stock ROM that is already rooted.

You also have to be aware that some ROMS can have issues. Sometimes stuff will not work when you try and use them (for example, 4G, HDMI, Cameras, and FM Radio to name a few). You really have to read the known problems and if it sounds like something you use will not work or if you want a completely 100% working device, do not use a ROM that says something is not working. Double that if it is something you use often.

Lastly, if you really want a ROM that has everything you want, you will have to learn how to make your own. Please do, I have released the second version of my ROM, feel free to check it out! (Link is in my signature)


After rooting, how do I install a ROM?

Answer: Through your recovery. It is always highly suggested to wipe data, cache, Dalvik. Here is the steps (this is how I do it and have not had any problems yet.)

Before flashing, ALWAYS do a Nandroid backup in case anything goes wrong! Do this periodically to keep your phone able to be restored in case of problems. I also suggest doing a full backup with Titanium Backup before you proceed.

1. Copy the ROM and optionally the radio/WIMAX/PRI/NV updates, kernel, and theme you plan on using (if any) to the root of your SD card. Hook up your USB cable to your computer, then on your phone switch from charge only to disk drive mode. Your phone's SD card pops up and then you can copy/paste your files onto there.

2. Make sure the transfer is complete and then power down your phone.

3. Reboot into recovery. Do this by holding the volume down key on your phone as you turn it back on.

4. Your phone will enter Hboot, let it load up for a few seconds, then use volume down to go to recovery. Press power to enter recovery. (NOTE: if you select recovery and your phone shows a disk icon with an exclamation mark your recovery is either missing or damaged and needs to be reflashed. That or you may not be fully rooted.)

5. Once in recovery (using Amon RA as my example) you go down to the wipe menu and hit your power button.

6. Once in the wipe menu, I usually do them in the order they are listed. First do a data wipe, then cache, then Davlik. I then tend to do a SD: EXT wipe, battery stats, and rotate settings as well just for good measure. Some recommend doing this twice, but I have never had to and think that is unnecessary.

7. Now you are ready to flash away (reminder, did you do a backup first? If not get to it before doing step 6!). Now you have a choice but I prefer to do it my way. You can flash everything at once, or reboot after each item. I do the reboot after each personally. Flash them in this order: ROM, kernel, theme, Radio/WIMAX/NV/PRI. You can try to flash the ROM and custom kernel afterwards only, then do the rest after rebooting.

8. If everything went well, your phone should take a long time to boot up the first time. Be patient. If it went well, within about 5-7 minutes or less the ROM should load up.

9. If your phone gets stuck on the EVO Screen or the boot animation repeats itself, that means the ROM did not take correctly. Do a full reset by taking out the battery for about 10 second and then reboot and see if it fixes the problem. If it happens again try and start over from step 6. Redo the wiping and flashing process. Also, if flashing more than one at a time, try doing each one, then rebooting before you flash the other.

10. If you do it again and still experience problems, check to see if you are fully rooted. If you determine you are indeed fully rooted, try and reinstall the rooted version of the stock HTC ROM and then try flashing your custom ROM again.

11. If no problems, congratulations and enjoy your new ROM!


What kernel works best for my EVO? This is another question you will often see. A variation is, "What kernel/ROM combo works best?"

Answer: Well, a stock HTC kernel is the short answer. It will work with everyone's phone (well) and likely have some of the best battery life. Now that the newest kernel was just released and has already been rooted, it will work better than the custom kernels overall (as far as being universally compatible). Now that they removed the 30 frame per second limit on the Evo with the 3.29.651.5 kernel, there is less reasons to use a custom one. There are exceptions, of course. But if you want your phone to behave like stock and work well with your phone, a HTC kernel is the only one you need (unless you want stuff like audio tweaks, multi-touch, overclocking ability, or the ability to customize more. In that case, a custom kernel is better). Use the new one with the FPS fix though!

For a custom kernel, again we do not know. A kernel is just above the hardware (speaking of the layers). It is more important than finding the correct ROM. A ROM is more like preference. With a kernel, it is very important to find the correct one for your phone. It has a lot to do with how smooth or fast your phone acts. A kernel that works good for my Evo can run like **** on your Evo. Some phones will work better with Netarchy kernels, others will be better with a Kingklick. Some phone will work well with HAVS, other may hate it. That is how this stuff works!

Sometimes you will know immediately that you have the wrong kernel for your phone. Your phone will act up, restart, connection problems, graphical glitches, and all kinds of funkiness! Other times it may take a day or so of using your phone to spot potential problems. You know it is definitely the wrong kernel if your phone refuses to bootup, even after a battery pull!

Kingklick and Netarchy are the two who make the best for Sense based ROMS, which is most of them. The only exception is Cyanogen. You need to run a kernel made for his ROMS (which are AOSP based, not Sense.) His is the only exception unless they are made from Cyanogen's ROMS (use it as a base).

If running Sense, I would try a few of King's and Netarchy's kernels. I suggest using their latest and working your way down until you find the right one for your Evo. You will know when you have the right one when your phone runs smooth (you have to run them for a day and use them, see what happens.) and you do not encounter any problems that were not present before you switched kernels.

If using CM6 or any Cyanogen ROM build (older, nightlies, etc.) you have to use a kernel made for that ROM. Snap is a popular one. Again, you have to experiment to find the right one.

So the answer is find one that works good for you, stick with it. Or just use a HTC kernel if using Sense and call it a night!


With kernels, what is BFS and CFS? Which would work better for my phone?

Answer: CFS stands for Completely Fair Scheduler. BFS stands for Brain **** Scheduler (sounds fun, right?). These are two different ways that the phone's CPU uses to schedule events. Without getting into the technicalities, here is what I have found for my Evo. Your mileage may vary and again, you have to experiment to find which works better for your particular phone.

CFS: Generally more consistent, use when you want consistent performance and/or if BFS kernels do not work well with your phone. Sometimes will appear to be smoother than a BFS kernel in overall use. The stock HTC kernel uses CFS and it is more standard than BFS.

BFS: Generally a bit faster but a bit more inconsistent (might appear to slow down more and such). Usually faster overall performance but will not look as smooth as a CFS kernel (in general).

Another way to put it, CFS is closer to a flat line, if you drew a performance map it would have less peaks and more consistency. With BFS, there would be more peaks and higher peaks with the faster readings and lower peaks with the slower.

You will find that one or the other may work better for you, or fit your needs better. It is a good idea to try both and see your results. My phone seems to heavily favor CFS kernels and I like the overall smoothness and consistency better. To me, BFS often appears to be more laggy than a CFS kernel. Again, each phone is different though and my results may not match yours.



I want to unroot my phone, what is the best way to do this? If you want to root using a different method, or need to return your phone to where you got it from for any reason, read on.

Answer: You need to download a RUU and install it. You can download an older RUU or get a newer one. This will unroot your phone and make it look like you never rooted it in the first place. You can even do a RUU if your screen is busted, just always keep USB debugging on. To use it, follow the instructions in the RUU executable and do what it says.


Is a full wipe needed when changing kernels? (Thanks to m4rk0358 for this!)

Answer: No, a full wipe is not needed to install a different kernel. I do suggest you go into your recovery and wipe the Cache and Dalvik before installing the new kernel though. In most cases, you can just flash the new kernel over the last kernel. But a full wipe is completely unnecessary (unless you are coming off a kernel made for CM6, in that case a full wipe and flashing a stock HTC kernel is recommended before switching back to a custom kernel).


Overclocking: "How much should I overclock, what should my SetCPU settings be set at?"

Answer: In this new age of phones, we are seeing them become faster and faster. Now with SetCPU readily available and overclock-ready custom kernels, a lot of people are overclocking their phones. These same people also wonder why they are having poor battery life. You see a few posts a day with something like, "Well, I tried the new (insert kernel here) and I overclocked but I noticed I am getting poor battery life!"

The HTC Evo has some really nice components, including the 1 GHZ Snapdragon CPU and the graphics chipset is plenty powerful. Do you really need to make it faster? Considering now that the FPS is unlocked, the phone is as smooth as butter as it is. Most apps work smooth on less capable and older handsets.

Again, all phones have the same components but results will not be the same at all (well, some can have slight differences..for example: the touch screen can be different). Mine may overclock to 1288 MHz without a problem, yours may lock up before you reach 1200 MHz. This is how it works

Most are only overclocking 10-12% or less. While benchmarking scores will increase, you will not see a major difference in overall use of your phone. In fact, you might not see a difference at all.

So yeah, if you want to impress people you never met, overclock and post your screenies! For me, my phone is more than fast enough and eating up battery for little to no perceivable gain is not worth it. This is not a computer with fans and a cooling system that can be upgraded!

But hey, if you really feel you need to run your phone 5-10C hotter just to make it a tad bit faster, knock yourself out! You can either have better battery life, or make your phone faster. Generally you cannot have both.

If using a kernel with HAVS, you do not need SetCPU to under clock. That is exactly what HAVS does, lowers voltages when your phone is idling. You are defeating the purpose by using SetCPU. This is why Kingklick himself tells everyone not to use SetCPU with his kernels.


Is a Task Killer needed for Froyo? (Thank to beatblaster for this!)

Answer: Believe it or not, Android 2.2 does a fantastic job managing apps all by itself. The Android OS is designed to kill apps/tasks as resources are needed and usually only does so when it's absolutely necessary. Using a task killer app can be handy when you encounter an app that freezes or is otherwise stuck but to use it as the primary task killer (instead of letting the OS do its thing) is contrary to the built in efficiency of Froyo itself. Try to trust the OS. Though a task killer is still recommended for the odd lot who are still using Android 2.1 or lower!


Which recovery should I use: Amon Ra or Clockwork? What are the pros and cons of each? Does Clockwork really wipe the Dalvik?:

Answer: Amon RA. Amon RA works, does everything you need it to do, and does it well! I highly recommend using Amon RA, it is generally considered the superior of the two and does a better job of wiping. Everything is right there and it is extremely easy to use.

Clockwork is pretty good too, but here are some pros and cons of each. (I will list a few, there are more differences but I will cover what I can think of offhand).

Clockwork Download here
PROS:
Able to use Rom Manager to flash ROMS and perform other functions (This is by no means necessary though, that is what a Recovery is for and it is generally safer)

Able to read ROMS stored in any folder.

CONS:
Does not seem to work as well as Amon RA in doing it's job.

Rumor that it does not properly clean the Dalvik cache when wiping. You hit it and it does not seem to do anything. Some claim that they checked the Davlik after using it and it is indeed wiped.

Some (including myself) find it a little more clunky to use.

Amon RA Download here
PROS:
Generally considered to be a superior recovery as it is based on Cyanogen code (who is really good, let us just put it that way!) and there are lots of posts where people switched to Amon RA because they were having issues with Clockwork.

Easy access to all functions, no need to scroll through 5 no selections to reach to a yes!

I find it better laid out and functions are nicely categorized.

It works better than Clockwork. Fewer reports of problems.

CONS:
You can only read ROMS and files on the root of your SD card.

It does not play well with the program ROM Manager. Most functions on ROM Manager are only usable through Clockwork (considering the overall poor experience with ROM Manager trying to download ROMS that no longer exist, bad checksum ROMS that I downloaded through it, and other problems....IMO NOT a con. Plus, safer to flash through recovery anyhow.)


Do the signal bars indicate signal strength for the 3G? (Thank to LovethyEVO for this!)

Answer: No. It indicates the connection for just the phone connection. You can have good reception for calls and still get slow download speeds. Generally if you have good signal, you will have good download speeds though.


How do you wipe the battery stats, or how do you increase your battery life?

Answer: As you may or may not be aware, you cannot trickle charge the battery on these phones as they will blow up! To counter this, the last 10% of your battery is going to be a bit flakey. What the phone does is once the battery reaches 100%, the phone software will let the battery drop down to 90% before it allows more charging to take place. That is why you often can use your phone after a full day's charge and immediately be at around 90% for no apparent reason. When you reset battery stats, you are effectively resetting the phone's software. it will take a couple of days for it to relearn your battery and give you a more accurate result and more efficient recharge.

Battery recalibration (Thanks to Cyanogen for this and to fachadick for bringing it to my attention).

If you're experiencing higher than normal battery drain, try the following:

1. Charge the phone to full battery; let it keep charging until the battery says it is fully charged. Do not just wait until the light is green, it isn't always fully charged, causing a lot of inaccuracies. (You can check by going to: Settings -> About Phone -> Status -> Battery Level = Full.)

2. Boot to recovery and wipe battery stats.

(To have the most accurate of battery stats, reboot the phone immediately after wiping the battery stats and wait for your ROM to boot completely to the desktop. Once your entire boot is done and you have full access to the phone, go ahead and pull the charger and continue.)

3. Do not charge the phone until after draining the battery completely, resulting in it automatically shutting off. Take out the battery, and keep trying to turn on your phone until it will not turn back on at all.

4. Recharge the phone completely and then use as you normally would.

This is a method that has been proven to work, I am sure there are other ways. My battery lasts longer after doing this and the reading is much more accurate. It might be advisable to do this after every ROM install if you want the most battery life and most accurate battery reading by the phone's software.


I will add more and reserve a couple more slots, but I think this is a good start. Please feel free to offer suggestions or your own misconceptions and answer.

HOW ABSOLUTELY AMAZING, WELL SPOKEN, LAYMANS TERMS, DETAILED REPORT. A LOT OF ANSWERS I NEEDED WERE RIGHT HERE. THANKS HUN!!
:thumbup::thumbup::thumbup::co ol:

~First Lady of Android~

Originally Posted by vide infra

then why do most (if not all) of the devs put links to the newest radio/wimax with their roms? Do they strip out the keys so they don't overwrite yours? I don't see why so many developers would stress updating radios if it was potentially hazardous.

I've seen its because they want you to use their stuff, & their stuff only.

~First Lady of Android~

I followed this tutorial here:
http://htcevohacks.com/htc-evo-hacks...18-with-s-off/

I got through the whole recovery thing except when I got to the steps for S-OFF. The very first command just returns a "device not found" error.

got stuck in a boot loop when I put cyanogenmod 7 on it. I redid some steps then just started panicking and flashing ****. Finally it booted into cm7.

When I boot into recovery it still says S-OFF but I can use things that require root. I am able to grant apps access to root using the SuperSU app. I want to be able to install ROMs via the SD card but I can't seem to do that with S-OFF. I'm confused though, because I followed that tutorial to the letter. I've never rooted before so I was very cautious. Then I thought I bricked my phone and was screwed when it wouldn't boot.

I don't understand this **** well enough.... -_- does anyone else have any suggestions for getting S-OFF? Nothing I've tried works and I don't understand why I keep getting "device not found" when I've enabled debugging and typed the command properly.

Originally Posted by Risket

I followed this tutorial here:
http://htcevohacks.com/htc-evo-hacks...18-with-s-off/

I got through the whole recovery thing except when I got to the steps for S-OFF. The very first command just returns a "device not found" error.

got stuck in a boot loop when I put cyanogenmod 7 on it. I redid some steps then just started panicking and flashing ****. Finally it booted into cm7.

When I boot into recovery it still says S-OFF but I can use things that require root. I am able to grant apps access to root using the SuperSU app. I want to be able to install ROMs via the SD card but I can't seem to do that with S-OFF. I'm confused though, because I followed that tutorial to the letter. I've never rooted before so I was very cautious. Then I thought I bricked my phone and was screwed when it wouldn't boot.

I don't understand this **** well enough.... -_- does anyone else have any suggestions for getting S-OFF? Nothing I've tried works and I don't understand why I keep getting "device not found" when I've enabled debugging and typed the command properly.

Calm down, you're already rooted so you dont need to do any of that crap. All you need is a good recovery. Smelkus can do that for you. Look it up and flash it, then you can. Begin downloading ROMs and flashing them through recovery.

Sent from my SPH-L710 using xda premium

Originally Posted by death-by-soap

Calm down, you're already rooted so you dont need to do any of that crap. All you need is a good recovery. Smelkus can do that for you. Look it up and flash it, then you can. Begin downloading ROMs and flashing them through recovery.

Sent from my SPH-L710 using xda premium

My phone won't even load the recovery. When I go to the bootloader and choose "recovery" it just goes to "fastboot" anyway. I have to use the command line on my computer every time and run "fastboot flash recovery recovery-RA-supersonic-v2.3.img" to get my phone to load recovery so I can flash anything.

I found Smelkus at goo.im They have aokp, cm9, ics, mason, reloaded2, tmdirt2. I tried them all and they all say installation is aborted.

I'm currently using CM7. I tried CM9 this morning (with Android 4.1.1) and everything was crashing constantly. I couldn't even use the Play Store, Music, YouTube, Drive. TeamDirt got stuck in a boot loop. Finally I just formatted everything and put CM7 back on it. I thought it would be awesome to have ICS or JB but I really just needed something that worked.

recoveries

---

i've read alot about cwm not being as good as amon_ra because it leaves traces of previous roms and you cannot flash radios, is there any truth to that?

Originally Posted by evathaevo

i've read alot about cwm not being as good as amon_ra because it leaves traces of previous roms and you cannot flash radios, is there any truth to that?

2.5 years ago when the evo came out Amon_Ra was definitely more reliable and would flash anything you told it to. After a bad experience with CWM when I first rooted my EVO I wouldn't use it. Around version 2.0.5.X CWM was having problems properly wiping dalvik cache, which would ultimately leave remnant data behind when changing ROMs which creates a lot of problems when flashing incompatible ROM versions, i.e. from a Sense ROM to an AOSP ROM. Any more CWM is and has been reliable for quite some time, I personally don't use it unless I absolutely have to, I much prefer TWRP on my current devices.


Sent from my SPH-L710 using Tapatalk 2