Develop Bugs

[Q] Root Question: No OTA updates done; Best ROM and method?

Hi--I am a generally technically adept Evo owner who would like to root to a Froyo custom ROM, but I've never had to root anything before. I've read threads meant to act as guides (like those linked in the sticky thread), but there seems like so much I don't understand. I know these are simple questions, but my searching didn't really help. I'd be really grateful if anyone had any helpful answers.
Question 1: Does anyone have any recommendations for the best custom ROM that will have these features?:
Froyo (of course)
SenseUI (I prefer it, but have nothing against stock Android)
Ability to restore my apps (via Titanium Backup, I assume)
Unlocked wifi tethering (via app or Froyo's in-built capability)
Unlocked FPS (I have a Novatec panel)
Same or better camera/video capabilities as stock SenseUI (i.e., nothing broken at least)
My current software: Stock Evo, no OTA updates applied, with Superuser Unrevoked permissions.
(That is, I have not applied any OTA updates since I bought it, June 11th. I'm running 2.1-update1, version 1.32.651.6. I did the Unrevoked 1-click "root" that in fact only gave me Superuser permissions (the Unrevoked that was first released, not the Unrevoked2 or 3 updates). I.e., I can use the wifi tether and Titanium Backup, and I've backed up my apps/settings with it.)
Question 2: Can anyone tell me in a simplest method to safely root and install the custom ROM, considering I have no OTA updates and unrevoked superuser permissions?
Specifically, I've read guides that list 3 steps (gaining root permissions, unlocking NAND, gaining "full" root), but I still have a lot of questions:
What does it mean to "flash a recovery"?
[*]When do I have to manually install radio updates, and how do I know which ones I need?
[*]If I decide I'd rather go back to stock, ever, can I do that?
[*]What is the likelihood of a brick, and can I repair a brick?
[*]Can Titanium Backup really restore all my apps after I do a full wipe and root? (just to calm my anxiety, please...)
The best guide I've seen is the "IDIOT-PROOF" root guide, at thread 701004 (sorry, new user restriction, can't post links), but I don't know if it's still current. That also seems more complex than SimpleRoot (also don't know if it's current).
I think I'm looking for the simplest root method with the least possibility of screwing everything up. (It pains me to say it, but a brainless iPhone-like "slide-to-jailbreak" method would be great.)
Sorry for the newbie questions. If anyone has any advice/answers, I'd be glad to hear them!

Well best bet for you is probably going to be either the one click simpleroot, you can go to simpleroot.com its there for download. Of course it depends on exactly what software version you are on. As far as your rom choice there is no rom that offers all of those things, probably closest will be stock rooted 2.2, then you can either live with the 30fps restriction or flash a custome kernel and live with 3mp camera .... you're choice. the recovery is a program that the phone boots into that has nothing to do with the rom at all, with this you can select several operation to make on the rom. You need recovery because you cant modify the rom when you are booted in the rom. Anyway this is all a very basic explanation. My recommendation would be to follow toasts part 1 then part 2 to root and unlock nand. (unlocking nand allows writing and writing to the system area of the rom while booted into the rom) then you will be all set to flash any rom you like. feel free to pm if you need more info As far as knowing what you need I would recommend starting with netarchy's stock rooted 2.2 odexed version. In his post he will tell you flash rom then radio then wimax, all of these files are included there in the post. Then as you learn you can switch between roms to explore what each one can do for you and decide which you like best. Yes Titanium backuop will work with this.

For me and I have flashed every rom lol. Daily driver would have to be the fastest and stabliest rom which is in my opinion Caulkins v1.02 froyo. Use simple root for 1.32. Then use the flash recovery and pick ra recovery.

ifly4vamerica said:
As far as your rom choice there is no rom that offers all of those things, probably closest will be stock rooted 2.2, then you can either live with the 30fps restriction or flash a custome kernel and live with 3mp camera .... you're choice.
Click to expand...
Click to collapse
Really? How about a ROM with, say, just 2.2 + SenseUI, with all the standard features, and wifi tether enabled?
Thanks for the advice, by the way, both of you.

ScaryBugThing said:
Hi--I am a generally technically adept Evo owner who would like to root to a Froyo custom ROM, but I've never had to root anything before. I've read threads meant to act as guides (like those linked in the sticky thread), but there seems like so much I don't understand. I know these are simple questions, but my searching didn't really help. I'd be really grateful if anyone had any helpful answers.
Question 1: Does anyone have any recommendations for the best custom ROM that will have these features?:
Froyo (of course)
SenseUI (I prefer it, but have nothing against stock Android)
Ability to restore my apps (via Titanium Backup, I assume)
Unlocked wifi tethering (via app or Froyo's in-built capability)
Unlocked FPS (I have a Novatec panel)
Same or better camera/video capabilities as stock SenseUI (i.e., nothing broken at least)
My current software: Stock Evo, no OTA updates applied, with Superuser Unrevoked permissions.
(That is, I have not applied any OTA updates since I bought it, June 11th. I'm running 2.1-update1, version 1.32.651.6. I did the Unrevoked 1-click "root" that in fact only gave me Superuser permissions (the Unrevoked that was first released, not the Unrevoked2 or 3 updates). I.e., I can use the wifi tether and Titanium Backup, and I've backed up my apps/settings with it.)
Question 2: Can anyone tell me in a simplest method to safely root and install the custom ROM, considering I have no OTA updates and unrevoked superuser permissions?
Specifically, I've read guides that list 3 steps (gaining root permissions, unlocking NAND, gaining "full" root), but I still have a lot of questions:
What does it mean to "flash a recovery"?
[*]When do I have to manually install radio updates, and how do I know which ones I need?
[*]If I decide I'd rather go back to stock, ever, can I do that?
[*]What is the likelihood of a brick, and can I repair a brick?
[*]Can Titanium Backup really restore all my apps after I do a full wipe and root? (just to calm my anxiety, please...)
The best guide I've seen is the "IDIOT-PROOF" root guide, at thread 701004 (sorry, new user restriction, can't post links), but I don't know if it's still current. That also seems more complex than SimpleRoot (also don't know if it's current).
I think I'm looking for the simplest root method with the least possibility of screwing everything up. (It pains me to say it, but a brainless iPhone-like "slide-to-jailbreak" method would be great.)
Sorry for the newbie questions. If anyone has any advice/answers, I'd be glad to hear them!
Click to expand...
Click to collapse
I'd like to suggest something before you actually move forward. I usually back up with MyBackup and with Titanium backup. I am completely rooted and nand unlocked but something i've seen Titanium for some reason after i grant it superuser tell me my phone isn't rooted on different roms, also i have seen Mybackup crash the sense and try to reboot it over and over in a loop. Luckily I did a Nandroid restore to a more stable setup. Some of the other forum members here are more likely than not less new to the process than myself, but I thought i had covered everything and when i did simple root, I was on 1.47, with the factory reset and everything lost my data... luckily it wasn't a lot or important. I just thought i'd let you know that it is not a bad thing to have a zipped backup of all of your apks+data, and your contacts with both programs before you go ahead. Hope that possibly can steer you out of trouble if one of them fails to perform as it should. Best of luck.

Exohart said:
I'd like to suggest something before you actually move forward. I usually back up with MyBackup and with Titanium backup. ... Hope that possibly can steer you out of trouble if one of them fails to perform as it should. Best of luck.
Click to expand...
Click to collapse
Cool, thanks for the tip.

You can get a rooted stock 2.2 ROM, odexed or deodexed. Then you can install a wifi tether app. Personally, I use Fresh 3.1.0.1, I don't notice any differences in general to stock, but you should probably just try different ROMs out and see which one you like. It's easy to switch around.
See this for ROMs.
As for rooting, You can use Simple Root, but I highly suggest doing it yourself using toast's or TheBiles' guides. You learn a lot and it's the same thing as using Simple Root, but you can deal with problems better (although I didn't have any issues when I did mine).
See here for guides.
There is a lot of info on how to get around any issues you have, so be sure to search if you do run into trouble.
And if you need the files for rooting, check here.

Awesome response, SilverZero, thanks! I'm starting to feel comfortable with the rooting procedure.
I think the difficulty I have in choosing a ROM is that many ROM threads don't list conclusively whether a feature works or not. So, for instance, I presume that the Fresh ROM has a fully working camera (8MP/720P with all settings), but I've read other ROM threads that talk about downgraded camera bugs, so I am not sure if I should assume things work fine. Conversely, I think wifi tethering doesn't work, since it *seems* to suggest it isn't working, but doesn't flat-out say so...
I don't suppose some source exists somewhere that lists/compares all of these ROMs' features in a table format, listing whether they work or not, or are downgraded? Having something like that in a central, often-updated location would be incredibly useful...

I used toast's method for rooting, and havent had any problems whatsoever. All I had to do after that, was install the new RA recovery image ( was more current ).
Is this the simplest way? probably not. But, i perfer doing the method with the most manual work. Automated processes tend to scare me, 'oh, our mod does steps 1 through 19 all at once'... well, thats fine, but what happens when it fails half way through? Toast's method, while a bit involved, is pretty simple, and if something happens, you can go "hey, when i do this command <whatever>, it does this, helps?!".
as for your 'questions 2s'
1: Are you sure you dont mean, flash from recovery? recovery is where you do all of your flashing, do your nandroid backups, and wiping. theres 3 ways to get there ( once your rooted/nand unlocked ).. volume -, and power while the phone is off, hold it til you get the menu. use quickboot ( a feature of damagecontrol mod ), or use adb using a command prompt on windows ( adb reboot recovery ).
2: Most people install radio updates when they go to change to new roms. The reason being, 2.2 'code' is based around having a certain radio version, and for things like 4g, and good 3g signal, you need to match.
personally, every time i go to install a new rom, i verify what the most recent radio version is out there, and install it ( same with wimax )
3: Once you are fully rooted, there are walktrhoughs for 'starting over / going back to stock'.. but I would just use one of the rooted stock images, as it gives you the ability to change your mind. for instance, right now 2.2 isnt rootable, so if you changed your mind after switching back to it, your kind of screwed. I'm not sure if the engineering image you install for root would go away if you reverted to stock/root though, as have never tried.
4: as long as you have the phone rooted, any 'bricking' that i have caused ( boot loops, power turning off on boot, etc ), were easily recoverable by just booting into recovery and reflashing. the only way I could see bricking in a totally bad way, would be if you somehow messed up the rooting process and corrupted the bootloader in such a way it couldnt recover. Otherwise, i have yet to see a rom that will flash / change your bootloader or recovery image, so it shouldnt be an issue.
5: It can, but i've seen issues where backing up stuff from a 2.1 rom, and installing a 2.2, causes weird issues. its safer to just redownload them if you are using a 2.2 rom. Another benefit of 2.2, is now google backs up your app selection you had installed, so when you wipe / flash a new rom, it auto-reinstalls all your apps you had from before ( it doesnt backup your settings though, just the applications themselves ).

ScaryBugThing said:
Awesome response, SilverZero, thanks! I'm starting to feel comfortable with the rooting procedure.
I think the difficulty I have in choosing a ROM is that many ROM threads don't list conclusively whether a feature works or not. So, for instance, I presume that the Fresh ROM has a fully working camera (8MP/720P with all settings), but I've read other ROM threads that talk about downgraded camera bugs, so I am not sure if I should assume things work fine. Conversely, I think wifi tethering doesn't work, since it *seems* to suggest it isn't working, but doesn't flat-out say so...
I don't suppose some source exists somewhere that lists/compares all of these ROMs' features in a table format, listing whether they work or not, or are downgraded? Having something like that in a central, often-updated location would be incredibly useful...
Click to expand...
Click to collapse
Here's a project that one user is putting together comparing different ROMs.
https://spreadsheets.google.com/ccc?key=0Aguc0npJCrWxdEFyU2NRNG1jNnRkY2trdXBsYlJLdWc&hl=en#gid=0

imiddlet said:
I used toast's method for rooting, ...
Click to expand...
Click to collapse
Wow, thank you for taking the time--you really answered all of my questions.
SilverZero said:
Here's a project that one user is putting together comparing different ROMs.
Click to expand...
Click to collapse
Greeeeat. Exactly what I was looking for.
You guys are awesome--I think I know what I need to know now, and in the next few days I will probably try rooting and installing Fresh Evo or BakedSnack. I'll update once I know how it went!

Urg...Well, I did the manual root method. Everything went fine through the initial root (using the classic method by toastcfh), and through the manual recovery mode where I made a nandroid backup.
Then, in recovery mode, I attempted to flash the latest Fresh Evo 3.1.0.1. It gave me no error messages, and I rebooted.
Now, it is stuck on an infinite reboot at the Fresh Evo ("FRESH!!!") bootup animation. It just keeps running that animation, never loading up. I've let that animation run about 15 times before I had to pull the battery to make it stop. Any time I try to boot the phone, I am stuck at that infinite reboot/load sequence.
The only thing I could do was hold Vol- while powering up to get into the bootloader and redo my stock root. I redid the Fresh Evo install, and it still just keeps rebooting for 10 minutes, before I pull the battery. I'll try Baked Snack next, but I don't want to press my luck with too many flashes... Any ideas anyone?

ScaryBugThing said:
Urg...Well, I did the manual root method. Everything went fine through the initial root (using the classic method by toastcfh), and through the manual recovery mode where I made a nandroid backup.
Then, in recovery mode, I attempted to flash the latest Fresh Evo 3.1.0.1. It gave me no error messages, and I rebooted.
Now, it is stuck on an infinite reboot at the Fresh Evo ("FRESH!!!") bootup animation. It just keeps running that animation, never loading up. I've let that animation run about 15 times before I had to pull the battery to make it stop. Any time I try to boot the phone, I am stuck at that infinite reboot/load sequence.
Anyone have any advice? Am I screwed?
The only thing I think I can do is hold Vol- while powering up to get into the bootloader and have it check PC36IMG, after which it gives me the same normal root Step 1 option to "Start Update" (Vol+ for yes, Vol- for no). Will this just restore to "stock" root? I'd like to get FreshEvo working somehow...
Click to expand...
Click to collapse
Try doing a full wipe, Data, Dalvik Cache, everything except the SD card. Then try reflashing the ROM. That was how I had to fix mine when it did the same thing.
Also don't forget to update your Radio, WiMax and Recovery if you havent already.
http://forum.xda-developers.com/showthread.php?t=715485
http://forum.xda-developers.com/showpost.php?p=6877247&postcount=98
As far as the best ROM is concerned I've been using SteelH's deodexed stock ROM with the netarchy-toastmod kernel and it's been running great. FPS are unlocked, its quick as hell and my battery life is excellent.
http://forum.xda-developers.com/showthread.php?t=743781
http://forum.xda-developers.com/showthread.php?t=719763

xHausx said:
Try doing a full wipe, Data, Dalvik Cache, everything except the SD card. Then try reflashing the ROM. That was how I had to fix mine when it did the same thing.
Click to expand...
Click to collapse
Thanks for the suggestions. Unfortunately, I did a double-wipe (cache, dalvik cache, and data/factory reset x2) before each of the 3 times I tried to install Fresh Evo. Same infinite reboot loop always.
Then I installed Baked Snack just now. I was able to actually boot (54 fps looks great!) but ROM Manager was giving me an error message about flashing the Recovery replacement, Wifi Tether force closed every time I opened it, and every time I plugged in the USB cable, it would disconnect about 2 seconds later, rendering the phone essentially useless since it wouldn't recharge or accept files in that two seconds.
So now I'm flashing back the stock root image, PC36IMG.zip.
I guess this isn't going very well. If anyone has any advice about these problems I'm having, I'm still in the depths of rooting hell. I appreciate the SteelH suggestions. Maybe I'll try that next. But it's definitely worrying me that every ROM I try has some major problems.

ScaryBugThing said:
Thanks for the suggestions. Unfortunately, I did a double-wipe (cache, dalvik cache, and data/factory reset x2) before each of the 3 times I tried to install Fresh Evo. Same infinite reboot loop always.
Then I installed Baked Snack just now. I was able to actually boot (54 fps looks great!) but ROM Manager was giving me an error message about flashing the Recovery replacement, Wifi Tether forced close every time I opened it, and every time I plugged in the USB cable, it would disconnect about 2 seconds later, rendering the phone essentially useless since it wouldn't recharge or accept files in that two seconds.
So now I'm flashing back the stock root image, PC36IMG.zip.
I guess this isn't going very well. If anyone has any advice about these problems I'm having, I'm still in the depths of rooting hell. I appreciate the SteelH suggestions. Maybe I'll try that next. But it's definitely worrying me that every ROM I try has some major problems.
Click to expand...
Click to collapse
if you're using clockwork try switching to Amon-RA. That may be whats doing it

xHausx said:
if you're using clockwork try switching to Amon-RA. That may be whats doing it
Click to expand...
Click to collapse
Thanks for the suggestion and the very fast responses. I'll give Amon-RA a shot, if I can install it. (note: I didn't use Rom Manager to install any actual ROMs here--it was just what I was about to begin using.)
Sorry if I have so many questions, but: What is the best method to flash Amon-RA recovery? Rom Manager seemed easy because you could simply download the program, run it, and choose an option in the settings menu to replace the stock Recovery.
For Amon-RA, there are two options--fastboot, and adb. I only have a vague idea of what these are and how to make them work.
As an UPDATE: I installed SteelH's ROM, and it booted, but it definitely didn't have 54 fps on mine (clearly 30 fps, Novatec panel FWIW), and I had the same problem with the USB cable disconnecting 2 seconds after plugging it in. I of course wiped everything before installing.
So I'm trying to figure out if I did something wrong in my original root--though it seemed to work fine. Could a locked NAND be causing these problems?

ScaryBugThing said:
Thanks for the suggestion and the very fast responses. I'll give Amon-RA a shot, if I can install it. (note: I didn't use Rom Manager to install any actual ROMs here--it was just what I was about to begin using.)
Sorry if I have so many questions, but: What is the best method to flash Amon-RA recovery? Rom Manager seemed easy because you could simply download the program, run it, and choose an option in the settings menu to replace the stock Recovery.
For Amon-RA, there are two options--fastboot, and adb. I only have a vague idea of what these are and how to make them work.
As an UPDATE: I installed SteelH's ROM, and it booted, but it definitely didn't have 54 fps on mine (clearly 30 fps, Novatec panel FWIW), and I had the same problem with the USB cable disconnecting 2 seconds after plugging it in. I of course wiped everything before installing.
So I'm trying to figure out if I did something wrong in my original root--though it seemed to work fine. Could a locked NAND be causing these problems?
Click to expand...
Click to collapse
I used the fastboot method earlier and it was a piece of cake. Just move the recovery to the Tools folder for the SDK, put your phone in fastboot mode and copy paste the two lines in a cmd prompt to install it. I was bored reading through the recovery thread I linked to earlier and apparently clockwork is not wiping properly, others were also having problems with Fresh because of it.
For the FPS fix that is done in the kernel so you would need to flash a custom one.

xHausx said:
I used the fastboot method earlier and it was a piece of cake. Just move the recovery to the Tools folder for the SDK, put your phone in fastboot mode and copy paste the two lines in a cmd prompt to install it. I was bored reading through the recovery thread I linked to earlier and apparently clockwork is not wiping properly, others were also having problems with Fresh because of it.
For the FPS fix that is done in the kernel so you would need to flash a custom one.
Click to expand...
Click to collapse
I tried to do as instructed. I rebooted into Fastboot mode on my phone, verified the device was seen by fastboot on my PC, then entered:
C:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-evo-v1.7.0.1.img
sending 'recovery' (5032 KB)... OKAY [ 1.406s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.094s
I tried to redownload the file, but the same result occurred.
EDIT: I was able to flash the Amon-RA recovery, going back to toast's instructions. I don't know why it wasn't flashed before...
I'm also not sure that my wiping the data is the problem--I wiped factory settings/cache/dalvik cache each time using only the stock recovery. I think my mentioning Rom Manager might have suggested I used that program to wipe my data, but I haven't done so...
Anyway, I appreciate the help. This is tough for me--I can't seem to get anything to work.
EDIT2: Problems solved! Indeed, I had not properly unlocked NAND. I redid the toast NAND unlock steps, and Fresh Evo installed on the first try!
My only remaining question: how do I flash a kernel? I simply flash a ROM and then the kernel? I think Fresh Evo is great, but fps2d is still showing me locked at 30 fps.
EDIT3: I think I found the answer. Flash it like any other ROM from zip. (Doing it with Netarchy's Kernel 4.0.3: http://forum.xda-developers.com/showthread.php?t=719763 )
(Probably looks silly reading me answer my own questions, but I thought it was better to look stupid if it might help a future beginner like me.)

Just my oppinion simpleroot never really worked for me and ive read bad things about unrevoked so just follow toasts method to rooting it is very simple and straight forward, as for rom i prefer baked snack themed version it is by far the most sexy rom i have seen it uses manups theme and u can enhance it even more, its very stable and has no fps cap on it, as well as both cameras work and video recording works, im not sure if blue tooth has been fixed yet and am not sure if 4g works because i dont have it where i live try it out and tell me what u think.

So...Everything works! A couple of final notes in case it ever helps anyone in the future:
Note 1: The call part of the phone was not working well at all. I could send and receive calls, and hear the other party, but the audio was very noisy and the other party didn't hear my voice when I talk.
I tried to update PRL and Profile, but I got an error code 1012: "The profile update could not be completed. Please try again later. If the problem persists, you may need to contact customer service. Error code:1012"
I thought the problem might be me overwriting some system files with Titanium Backup (though I was careful). But when I tried wiping factory settings/cache/dalvik cache, and rebooted, still the same problems. Ultimately, it turned out simply that Sprint's servers were down, so I couldn't update my profile/PRL. I finally was able to update the Profile and PRL (now 60669) when they came back up, and everything seems to be working.
Note 2: I realized too late that I lost all of my visual voicemails. I don't think there's a way to restore them, and I don't know if there's any way to back them up. But something to think about if you've racked up a fair amount of downloaded visual voicemails.
Thanks everyone for your help.

READ FIRST! - Rooting, Solutions to Problems, the Answer to Life (Updated:11/29/11)

ROOTING + UNROOTING INFORMATION + COMMON QUESTIONS + PROBLEMS w/ LINKS​
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND TO BE USEFUL. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
Preface:
I made this guide to be a collection of information for the latest rooting methods as well as common questions and problems that arise from rooting/flashing/etc. Please read the entire guide if you are new to rooting. Also the common questions and problems are found in posts 2 and 3 of this thread. I hope you find this to be helpful. Happy and safe rooting.
----------------------------------------------------------------------------------------------------
Rooting Information
What is rooting and why should/shouldn't I do it?
Rooting is a way of gaining access to the root directory of your phone enabling you to change every aspect of your phones software that the manufacturer has locked. This enables you to do many things with your device that the manufacturer did not intend. Here are some reasons why people root and why people don't.
Reasons to root:
Get the latest versions of Android on your phone before anyone else.
Try faster and more optimized versions of your phone's software.
Overclocking and underclocking your phone.
Longer battery life.
Theme your phone a lot more.
FREE Wireless Tethering.
Remove unwanted Sprint software.
Reasons to NOT Root:
Not comfortable with troubleshooting your phone and phone problems.
Do not have the time to spend going through countless forums to find solutions to problems.
Possibility to break your phone permanently causing you to go back to Sprint (IF YOU HAVE INSURANCE) to get another one or buy another if you don't have insurance.
VOIDS YOUR WARRANTY WITH SPRINT. (Can be undone)
Very time consuming and addicting.
Do not know what a "driver" is for a computer.
Have no knowledge of DOS.
So how do I root?
-Don't use any method just because the guide says "ROOT METHOD". Make sure its the latest root method used for your situation. Even this guide will get outdated one day (I'll try my best to keep it up to date).
-Rooting will cause all your information to be lost if you did not properly back them up. You will lose anything saved on the phone, such as contacts (not synced to Google) and applications and settings. Anything on your SD card will still be there such as music and pictures and video.
Basic terminology:
ROM - The phone's software
Flashing - Installing. Pertains to ROMs, kernels, radios, themes, etc.
0) Make sure you have at least 30% battery. You do NOT want to have your phone die when flashing. Your phone will turn into a very pretty and expensive paperweight.
1) Turn on your phone and hit Menu > Settings > About Phone > Software information. Make a note of your Baseband Version, Kernel version, Software Number, and PRI Version. Now press your BACK button and go to Hardware information. Look for your 4 digit Hardware Version. Write this down too. This information is helpful when troubleshooting issues you may have.
2) Power your phone off. Hold VOLUME DOWN and your POWER button till you see the following screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is called the Bootloader Screen. Remember it. You will see it very often. There are two pieces of crucial information on this screen that you will be concerned with. On the first line, you will see S-ON. This stands for Security-ON. It means you are not rooted more or less. On the second line you will see "HBOOT #.##.####" This is your HBOOT version number.
3) Now that you have this information, it is time to pick your root method. You only need to root once and only need to pick ONE of the following methods.
Revolutionary: - This will unlock the bootloader for the latest stock GB. Follow all instructions to the letter.
http://forum.xda-developers.com/showthread.php?t=1218386
IF YOUR VERSION IS BEFORE 4.22.651.2, UPDATE YOUR PHONE USING OTA THEN ROOT USING REVOLUTIONARY!!!!!!
PLEASE NOTE THAT WHEN YOU GO TO THESE RESPECTIVE LINKS, MAKE SURE THAT THEY ARE STILL UPDATED! CHECK THE LAST PAGE OR 3 TO SEE IF IT IS STILL UPDATED. IF NOT SOMEONE WILL GENERALLY SAY IT IS OUTDATED. SUPPORT FOR THE ROOT METHODS SHOULD BE DONE ON THEIR RESPECTIVE PAGES OR IN THE Q+A PAGE. ALSO MOST ISSUES YOU WILL RUN INTO, SOMEONE ELSE PROBABLY ALREADY HAS SO PLEASE USE THE SEARCH FUNCTION.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How do I know if I am rooted?
Go into Bootloader. If you see S-OFF at the top, you are fully rooted.
I am rooted now. What can I do?
FIRST MAKE A NANDROID BACKUP! ALWAYS DO THIS BEFORE YOU FLASH SOMETHING. THESE ARE BIG FILES SO TRANSFER THEM TO YOUR COMPUTER TO SAVE SPACE ON YOUR SD!
A nandroid backup basically takes a snapshot of your phone which you can restore. While it will fix most problems, it is not a cure all. It will fix most if not all ROM flashing blunders.
How do I make a Nandroid Backup?
1) Power off your phone.
2) Hold VOLUME DOWN and POWER to till you see the Bootloader screen.
3) Use VOLUME UP and VOLUME DOWN to navigate to RECOVERY and push the POWER button to select.
4) Once in Recovery, Look for an option that says NANDROID or NANDROID BACKUP.
5) Select that and hit power.
6) Wait till your NANDROID BACKUP is finished and then proceed to flashing anything you want.
7) ALWAYS DO THIS BEFORE FLASHING ANYTHING.
8) If you run out of space on your SD card, your backups are saved to your SD card under the Nandroid Folder. Back up this folder to your PC.
OK. I made my Nandroid Backup. What can I do now?
You can now flash custom ROMs, kernels, radios, themes, etc.
If you aren't sure what a ROM/Radio/Recovery is check out ricsim78's post here:
http://forum.xda-developers.com/showthread.php?t=790427
Here is a great guide on kernels. Kernels are what you want to flash if you want to improve battery life.
http://forum.xda-developers.com/showthread.php?t=894880 - Kernel information. What each does and what each stands for?
Here is where you can find most of the goodies here on XDA for the Evo:
Head on over to the Android Development forums for Custom ROMs/Kernels/Radios/Recoveries.
If you want themes, clocks, widgets, UI, etc, head on over to the Themes + Apps forum. Make sure you flashed a "Deodex" ROM for theming.
How do I flash a ROM/Kernel/Theme/etc
99% of all ROM's, kernels and radios come flashable (will be a .zip file).
0) MAKE SURE YOU HAVE 30% BATTERY AT LEAST!
1) Plug your phone into your computer and connect it as Disk Drive.
2) Place your ROM/Kernel/Radio/Theme/ETC into your SD card. (If you have the 4 in 1 option skip to step 5)
3) Power your phone off. Hold VOLUME DOWN and POWER at the same time till you load into Bootloader.
4) Select recovery by using the volume buttons to move and hit the power button to load into Recovery.
5) Once in recovery, make a NANDROID BACKUP and wipe your data/cache/dalvik! If you are flashing an update to your ROM and want to keep your apps, don't wipe your data. If you run into errors or FC (Force closes), wipe your data/cache/dalvik and flash again.
6) Flash your file by going to Install/Flash zip from sdcard.
7) Select your file and hit the power button. Press power again to confirm if needed.
8) Wait till the flash is complete and reboot.
How do I return to stock (unroot)?
http://forum.xda-developers.com/showthread.php?t=1218386 Go down to the FAQ. Your answer lies there.
How do I backup my apps?
Use MyBackup. You can use this to backup and restore your apps without the need for rooting. (Thanks teh roxxorz)
Appbrain is good if you are using market only apps. However app data won't be saved.
Titanium Backup is also good if you are rooted.
Credits:
teh roxxorz aka time traveler, xHausx, ricsim78, zikronix, djR3Z, mroneeyedboh for their work on the guides I linked and to all the devs out there cooking up ROMs/Recoveries/Themes/Kernels/ETC to bring everyone rooting joy.

Common Questions
I am getting an Over the Air (OTA) update from Sprint. Should I accept it if I am rooted?
This is what a Sprint OTA update looks like.
IF YOU ARE ROOTED, DO NOT ACCEPT THIS OTA.
This means that your phone's software is not up to date and it is telling you to update. You must download a ROOTED version of the update and manually flash it. Accepting this will cause you to lose root and worst case, brick your phone. SO DON'T DO IT! lol
This is the link to the latest OFFICIAL ROOTED Sprint ROMs. This will flash a ROOTED 100% stock phone. Meaning it will be rooted but it will be just like your how your phone was before you rooted it. You can NOT remove the Sprint bloatware on the phone. You can also flash a custom ROM with the newest update as its base.
Newest Stock ROOTED RUU - 4.22.651.2
http://forum.xda-developers.com/show....php?t=1110733
3.70.651.1 + Radios
http://forum.xda-developers.com/showthread.php?t=874251 NEWEST ROOTED OTA. Use the First link for the Radios.
3.30.651.3 + Kernels
http://forum.xda-developers.com/showthread.php?t=836728
3.30.651.2 + Kernels
http://forum.xda-developers.com/showthread.php?t=819838
3.29.651.5
http://forum.xda-developers.com/showthread.php?t=789913
I rooted using ABC's method. Do I need to root again using XYZ's?
No. Once you are rooted, you are good to go.
I turned my phone into a paperweight/bricked it/"borked" it/its just not working no matter what I do. What can I do?:
If you can still get into your bootloader then you are not bricked! But if you can't get into bootloader and if you have Sprint's Total Equipment Protection Program, you are in luck. They changed their policy on October 23rd. Here are the details of what it covers.
http://www.phonenews.com/sprint-tepsr-changes-next-week-13303/
If the phone is beyond repair, you will have to go through Asurion and pay the $100 deductible. TEP does not cover rooted phones. You have to go through Asurion.
If you don't have TEP, everything except water/fire damage and lost phone replacements cost $35 per incident as long as the phone is not beyond repair. If it is beyond repair, you will have to buy a new phone.
What is PRL?
PRL stands for Preferred Roaming List. Its a list of roaming towers in your area. Its best to keep this updated in crappy coverage areas.
What is PRI?
http://forum.xda-developers.com/showthread.php?t=751935&page=7 <- Debate on what it stands for. (REALLY?!)
In actuality it is called "Product Release Instructions" and is essentially a list of settings for the radio. It's the PRI which uses the PRL to enable data roaming by connecting it to towers/cell sites listed in the PRL and for other things such as to allow calls to interrupt an active data session (ring-through).
How do I update my PRL/PRI?
Go to Menu > Settings > System Updates > Update PRL + Update Profile.
If that doesn't work (and for most, it doesn't), you can always download it from here. Mind you the above steps only work for Sense based ROMs. If you are on AOSP you have to download it from below.
http://forum.xda-developers.com/showthread.php?t=715485
To update your PRL Manually, go to this link (thanks to Noncorp)
http://forum.xda-developers.com/showthread.php?p=10004743#post10004743
Latest Information:
Radio: 2.15.00.04.08
WIMAX: 27925
PRI: 1.90.003
PRL: 60677
I see "deodex" and "odex" ROMs. What are those?
Basically if you want to theme your ROM you want to use deodexed ROMs. Odexed ROM's are made to be streamlined. There is a performance difference. Deodexed ROM's will take longer to boot up because everything or almost everything is unpacked. Odexed ROM's will boot faster and be more responsive.
http://lmgtfy.com/?q=What+is+deodex
Google is your friend =P
FREE Wireless Tether:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Evo
***Some builds don't work with certain ROM's. Trial and error or searching within your ROM's thread will let you know which build numbers will work for you. Also note if you enable WIFI Encryption, the password is CASE SENSITIVE! Make sure you know that as you are typing the password in due to certain keyboards auto capitalizing. ***
Launchers:
ADW - Landscape on Home Screen, Customize Dock Bar, Customize Icons, Customize App Drawer, Free and Pro Versions.
LauncherPro - Landscape on Home Screen, Customize Dock Bar, Customize Icons, Customize App Drawer, Free and Pro Versions, Widgets (Pro Only)
Widgets
Beautiful Widgets - Sense like clocks and weather. Make sure to download the animation package if you want animated weather.
OneSeven - A text based date widget
Tajm - A text based clock
----------------------------------------------------------------------------------------------------
Battery - Common Questions and Problems
What is the best ROM + Kernel combination for battery life?
There is no right answer for this. Battery life is affected by so many factors, the only thing you can do is trial and error. Here are most of the factors that can affect battery life:
-Phone Settings (Haptic feedback, screen on duration, auto sync, radios, etc)
-ROMs
-Kernels
-Overclocking + underclocking
-Apps
-Signal strength
-Roaming
-Battery type
-Battery stats
-Calibrating the battery
-PRI
-PRL
-The water you drank the other day
-The **** you took just before
So how do I improve battery life?
#1 Go to the bottom: http://forum.xda-developers.com/showthread.php?t=790427
#2 Adjust your brightness settings, turn off anything you aren't using, use Wifi if it is available (noticeable), set sync frequencies longer, and turn off haptic feedback.
#3 Get some Ebay batteries. They work decently for the price but you may not enjoy carrying multiple batteries around and doing the battery shuffle with your phone.
#4 http://forum.xda-developers.com/showthread.php?t=778466
#5 Seriously go out and buy an extended battery. It is well worth it if you don't care about the increase in size. If you are like me and use the car dock you will get a bit ticked off that you have to switch back to the stock battery and stock cover when you get into your car but its worth it.
#6 You do the hokey pokey and you turn yourself around, that's what it's all about!
I bought #3 when I got my Evo at launch. The damn aftermarket batteries lasted longer than my OEM.
----------------------------------------------------------------------------------------------------
ROM Information and Tips Poll of ROM usage: http://forum.xda-developers.com/showthread.php?t=951057
Sense ROMs
There are a few flavors of Sense nowadays and you may be confused as to what it all means. If your Evo was fully up to date, it should be on Android 2.2 Froyo using Sense 1.0.
Lately there have been ROM leaks that have pushed it all the way up to Gingerbread 2.3.3/2.3.4 with Sense 3.0. The problem is these are unofficial updates of Sense.
Any leaked ROM will have bugs that must first be ironed out.
Sense 1.0 - Will have everything working. Most of these ROMs optimize performance and are themed with certain mods and tweaks.
Sense 2.0 - Will almost certainly not have 4G working along with other bugs because Sense 2.0 are ported over from other devices who don't use WIMAX. If you need 4G, don't bother flashing a Sense 2.0 based ROM.
Sense 3.0 - Currently there are two leaks that feature Sense 3.0, Kingdom (Evo 3D) and the Sensation leak. The Kingdom leak is the best bet as of now because it has both Android 2.3.3 and Sense 3.0 WITH WORKING 4G! The problem is that it was made for a 3D device so there are bugs that need to be ironed out.
Here are some general guidelines to follow:
If you want stability, stick with a Sense 1.0 ROMs.
If you want to experiment and can do without 4G or don't have 4G in your area, try a Sense 2.0 ROM.
Sense 3.0 is in no way ready for daily use without major bugs.
When picking your Sense ROM from the Android Developer section, make sure you read the titles and the Original Post (OP) by the author of the thread.
They will tell you what the ROM is based off of.
AOSP ROMs (Vanilla ROMs)
AOSP/Vanilla ROMs do not have Sense and is based off the original Android UI. Sense can limit performance and use certain resources. The following two ROMs should be your starting points for AOSP based ROMs as most of them for the Evo are based off Cyanogen Mod (CM). While these have come a long way for the Evo, some functions aren't working such as 720p video recording.
http://forum.xda-developers.com/showthread.php?t=956187 CM7 + 4G + HDMI Mirroring
http://forum.xda-developers.com/showthread.php?t=915527 MIUI NO 4G
** These have been found to be stable for daily use. Read through each thread to know what is and is not working. There are many other ROMs out there that are in beta that are not listed here. **
----------------------------------------------------------------------------------------------------
ADB - Android Debug Bridge
A great guide to ADB.
http://forum.xda-developers.com/showthread.php?t=879701

Common Problems:
Standard Troubleshooting For Many Flashing Problems:
-Try Rebooting. Most problem will be solved this way.
-Was it fine before your Nandroid Backup? If so, restore your backup.
-If you flashed something and are having issues, did you wipe your data/cache/dalvik? If not then do it and reflash.
-If you are still getting problems, the file is most likely corrupt or outdated. Try redownloading and making sure the file is updated for your ROM + Version #
-If the file is updated and NOT corrupt, SEARCH FIRST IN THE FORUMS OR GOOGLE! You will be surprised on the answers you can find in 15 seconds of searching.
-Can't find any solution or workaround? Then make a post in that thread with details of your problems, as well as ROM, Hardware version, Hboot #, error messages, etc.
I am getting a picture of an Evo with a Red ! inside of a triangle HALP!
You mean this?
This means your recovery is not flashed to a custom one such as Amon RA or Clockworks. If you do have one flashed, try hitting VOLUME UP and the POWER button. See if your screen pushes into recovery. If not then you will have to reflash your recovery again.
I am getting a picture of an Evo with a Green arrow with a circle HALP!
You mean this?
This means whatever you just flashed is being updated and you should let it run its course. It will go away after a few minutes and by the time you finish reading this it might be done! If its running for a LONG TIME. Pull your battery and load back into recovery. Wipe your data/cache/dalvik and then reboot again. You might see this screen again but it should run through this time.
I am getting a red ? image what does that mean?
You mean this?
The "WTF" (courtesy of xHausx) icon, it will show that if it gets a bad auto update command or a bad update package. Try to go back into recovery, wipe your data/cache/dalvik and try again.
I am getting a red triangle with an !
You mean this?
The Last one I'm guessing you'll see if there is an error within the recovery itself, I've never seen it be used before. - xHausx
I am getting random Force Closes (FCs) after flashing ****.
Did you wipe your data/cache/dalvik? If not do a Nandroid Restore to the backup you should have done before flashing and then wipe data/cache/dalvik and then reflash. See if you still get a FC. If you do, there might be a problem with whatever it is you flashed with the ROM you are using. Check on the thread you downloaded it from for support.
I am stuck in a boot loop.
If you flashed a new ROM and you are stuck in a bootloop, you probably didn't erase your data/cache/dalvik. Try that and reflash your ROM. This will fix most boot loop issues. If it was from something else, make a post in your respective threads or in Q+A.
I am stuck in a NAND Backup! Lots of "..............."
Pull your battery and restart the backup. You might also want to erase the NAND backup that failed by going to your respective NANDROID backup folder on your SD card.
My 4G isn't connecting and I'm in a 4G city.
Enable your 4G radio. Go to Menu > Settings > Wireless & Networks and look under 4G. If you see Scanning... > Connecting to Sprint > Authorizing > Scanning and it keeps repeating, you might have lost your RSA keys. Go back to your home screen, hit Menu > Settings > About phone > Hardware Information > 4G MAC Address. Does it say 00:16:08:00:24:05? If not you are fine and probably don't have a strong enough signal. 4G doesn't penetrate as well as 3G because there isn't that much signal saturation. Also because 4G runs on a higher frequency than 3G and therefore doesn't penetrate as well. (kudos to for reminding me nuformzdesign) If so, you lost your MAC address. Now you need to check if you have your RSA keys.
Go to the Market and download RSA Key Checker by joeykrim. Use this to see if you still have your RSA keys.
If you still have your RSA keys and only need to fix your MAC address IF it is 00:16:08:00:24:05. Go here:
http://forum.xda-developers.com/showthread.php?t=715525
If you lost your RSA keys, there is a restore method but I am not sure if it works. At this point it is your only choice beside returning it to Sprint.
http://forum.xda-developers.com/showthread.php?t=936945&highlight=RSA
OK. That didn't work. What do I need to do before I return this to Sprint?
Unroot your phone using the method above. Return it to Sprint, and tell them you can't connect to 4G and continue playing dumb. Say that you turned it off and turned it back on and no 4G. Also make sure you remove your SD card. If their tech is smart, he will look for signs of root like busybox or SU. So just keep it simple and take your SD card out and give them your phone.
I still have my RSA keys and my MAC address but I still can't connect to 4G.
Go to Menu > Settings > Update Phone > Update Profile. Also do Update PRL. Reboot your phone and try to connect again. If you can't go to Menu > Settings > Wireless & Networks. Look under 4G and see if it just gets stuck on Scanning and does NOTHING else. If it does, are you underclocking/undervolting? If so you might have been too aggressive. Revert back to a stock kernel. Check to see if you get your 4G back.
My 4G takes forever to connect. What can I do?
Take a look through this. What this does is basically make your phone check every 15 seconds instead of 300 seconds. Which is why your 4G takes forever to connect when you know you have a strong signal. Be warned however as this will cause your phone to die faster when 4G is on. Or you can update to 3.70.651.1. It has a "widget" that allows you to manually reconnect.
http://forum.xda-developers.com/showthread.php?t=726877
My USB port/SD Card is not found or not working. What can I do?
Go through this post.
http://forum.xda-developers.com/showthread.php?t=695243
Also this happened to me once because I unplugged in disk drive mode and I couldn't access anything on my SD card. I reconnected it to my PC in disk drive mode and then ejected the drive from Windows. This restored functionality.
I am a MAC user and I downloaded ____'s ROM and it doesn't work.
Macs will recompress the file. Use Firefox to download and make sure it doesn't recompress the file. It should work then. Either that or use a Windows based PC.
I tried to NANDROID BACKUP and I got an error message saying "Run 'nandroid-moble.sh' via adb!"
Your SD card is full. Mount your phone in recovery using the USB-MS option (Amon-RA) and clear off your SD card. Your Nandroid Backup folder is called nandroid (Amon-RA). Move that to your PC.
I see these weird multi-colored lines that look like static. Is something wrong?
This is a very common issue that happens to a lot of people. You don't need to worry. Nothing is wrong. Sometimes it will persist after you flash a ROM. Restarting your phone will fix the issue. It will always come up when flashing a ROM or restarting. However it won't impede you from using your phone. So the bottom line, don't worry about it.

Very Helpful SHould Be Stickied!

Thanks. Did this in one sitting. Going to add more as time goes on with what I see a lot of being asked here.

stickied stay on topic. @OP ball is in your court. good job

Thank you for this! There have been a few tweaks to some of the root and unroot methods/guides...nice to have them in one place

I have a question. I rooted my phone using these 2 web pages http://forum.xda-developers.com/showthread.php?t=765496, http://www.thedroiddemos.com/forum/viewtopic.php?f=18&t=7, which are pretty much the same while i watched the videos djrez has on how to root the evo. I just noticed those 2 threads were posted a while back. Does that mean i should root my evo again using your method?

LuvThyMetal said:
I have a question. I rooted my phone using these 2 web pages http://forum.xda-developers.com/showthread.php?t=765496, http://www.thedroiddemos.com/forum/viewtopic.php?f=18&t=7, which are pretty much the same while i watched the videos djrez has on how to root the evo. I just noticed those 2 threads were posted a while back. Does that mean i should root my evo again using your method?
Click to expand...
Click to collapse
If you are rooted already, you do not need to update your Root method. You only need to update your ROM.

sekigah84 said:
If you are rooted already, you do not need to update your Root method. You only need to update your ROM.
Click to expand...
Click to collapse
Thank you. Are you talking about the recovery Rom? Sorry I'm new to this stuff
Sent from my PC36100 using XDA App

LuvThyMetal said:
Thank you. Are you talking about the recovery Rom? Sorry I'm new to this stuff
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No. Recovery is different from a ROM. A ROM would be the equivalent to the flavor of OS you are using. Whether it be CM6, Ava v10, Myn's ROM. Look under the Android Development section and go through some of the posts labeled as [ROM]. They have screen shots of the ROM's appearance and some have videos of their use and features.
Some just change the appearance, others increase performance, include apps such as Swype and Hulu, and some change it back to vanilla/ASOP which is a non-Sense ROM that goes back to the traditional Android OS.

sekigah84 said:
No. Recovery is different from a ROM. A ROM would be the equivalent to the flavor of OS you are using. Whether it be CM6, Ava v10, Myn's ROM. Look under the Android Development section and go through some of the posts labeled as [ROM]. They have screen shots of the ROM's appearance and some have videos of their use and features.
Some just change the appearance, others increase performance, include apps such as Swype and Hulu, and some change it back to vanilla/ASOP which is a non-Sense ROM that goes back to the traditional Android OS.
Click to expand...
Click to collapse
Oh Haha I feel dumb now. Thanks a lot this clears my confusion. Is there any roms you would recommend. I'm using standard android OS, at least I think so :S
Sent from my PC36100 using XDA App

LuvThyMetal said:
Oh Haha I feel dumb now. Thanks a lot this clears my confusion. Is there any roms you would recommend. I'm using standard android OS, at least I think so :S
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What your phone originally came with is called Sense. If it looks anything like it, its a Sense ROM. Original OS looks like the Nexus. As for recommended apps, its hard to say. Everyone has their own preferences so many people flash a ton of different ROM's to find one they like. I personally like Sense so I flash a deodex stock rooted ROM and then proceed to flash themes and remove bloatware with custom kernels.
Just remember to make a Nandroid backup. And then try different ROM's out. Be careful when flashing WIMAX radios. You might lose 4G permanently.

sekigah84 said:
What your phone originally came with is called Sense. If it looks anything like it, its a Sense ROM. Original OS looks like the Nexus. As for recommended apps, its hard to say. Everyone has their own preferences so many people flash a ton of different ROM's to find one they like. I personally like Sense so I flash a deodex stock rooted ROM and then proceed to flash themes and remove bloatware with custom kernels.
Just remember to make a Nandroid backup. And then try different ROM's out. Be careful when flashing WIMAX radios. You might lose 4G permanently.
Click to expand...
Click to collapse
Oh okay yea then I'm using sense Rom not the originally Android OS. To do a nandroid back up isn't that when you hold volume down and power button? I have no idea what kernel is. I'm kinda scared trying new roms cuz I've never tried it before, I definitely don't want to lose 4G that would suck
Sent from my PC36100 using XDA App

Good job thanks for this will be really helpful for me and everyone

LuvThyMetal said:
Oh okay yea then I'm using sense Rom not the originally Android OS. To do a nandroid back up isn't that when you hold volume down and power button? I have no idea what kernel is. I'm kinda scared trying new roms cuz I've never tried it before, I definitely don't want to lose 4G that would suck
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes and no. You hold VOLUME DOWN and POWER to get to bootloader. From there you go to Recovery. Then in Recovery, you will see an option for Nandroid/Nandroid Backup. You make it there.
Losing 4G is thought to be caused by flashing WIMAX radio updates. Kernels should be fine. I lost 4G connectivity because I underclocked too much. ROM's like CM6 just don't support 4G, not that you will lose 4G. AVA's ROM is fine, same with a few others. If you NANDROID back up you should be fine against 99% of the problems out there.

sekigah84 said:
Yes and no. You hold VOLUME DOWN and POWER to get to bootloader. From there you go to Recovery. Then in Recovery, you will see an option for Nandroid/Nandroid Backup. You make it there.
Losing 4G is thought to be caused by flashing WIMAX radio updates. Kernels should be fine. I lost 4G connectivity because I underclocked too much. ROM's like CM6 just don't support 4G, not that you will lose 4G. AVA's ROM is fine, same with a few others. If you NANDROID back up you should be fine against 99% of the problems out there.
Click to expand...
Click to collapse
Thanks man, a Nandroid backup should be easy then. I was thinking it was when you save all the files in your SD card to your computer by selecting all and saving on desktop or something but nvm I understand now.
I guess I just have to be really careful when I flash a Rom.
Sent from my PC36100 using XDA App

LuvThyMetal said:
Thanks man, a Nandroid backup should be easy then. I was thinking it was when you save all the files in your SD card to your computer by selecting all and saving on desktop or something but nvm I understand now.
I guess I just have to be really careful when I flash a Rom.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Glad I could help. Like you said. Be careful when flashing and follow all instructions from the devs. You should be fine. I never bricked a phone but I did end up losing my RSA keys for 4G so I had to get a replacement.

Hi everyone. First of all I'm using hardware version 0003. My Baseband is 2.15.00.09.01. Software number 3.30.651.3. Is it possible for me to root this Evo? Please help!!!

Great job on the guide sekigah84! I have update the Universal root so it now works with the 2.02 hboot

[HOW-TO] CyanogenMOD on Telstra Defy

Hey everyone,
Just hope to make things a bit easier for all fellow aussies trying to install Cyanogen 7 on there Telstra Defy. Links and attachments at the bottom.
First thing is, so far as i can tell, 2nd-init does not run Clockwork recovery properly from the telstra stock SBF. On this ROM you will probably get the "unable to mount SDcard" error.
Also do NOT install clockwork recovery during any part of this, it comes with
2nd-init and does not need to be installed seperately (can cause problems if you do)
This is the series of steps I took to get it working.
1. Copy Defy-Cyanomod 7 Beta and Google Apps onto SDcard
2. Root phone with SuperOneClick 1.7 (1.8 doesnt seem to work)
3. Install 2nd-init (App is on market or below)
4. Reboot phone twice
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
7. Let the phone cycle through 2 complete loops.
(CM7 seems more stable once I did this)
8. On the third cycle enter 2nd-init (Volume Down when blue light is on)
9. Enter custom recovery from 2nd-init
10. WIPE Data/Cache
11. Install Defy-Cyanogen 7 from SDcard
12. Reboot phone and let CM7 load up
13. Reboot again and enter 2nd-init+custom recovery and install Google
Apps from SDcard
14. Enjoy some CM7 goodness
Thanks to everyone that made these things possible.
Links
Defy-Cyanogen 7
Latest Google Apps
http://forum.xda-developers.com/showthread.php?t=1033654
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/

I'm running cm7 on my telstra,defy. At this stage no problems, only thing was i had already flashed a non-downgradable sbf. But for warranty purposes i can still go back to telstra by flashing a fixed telegraph Sgt and restoring with stock telegraph nandroid backup.
Sent from my MB525 using XDA App

Can you post a picture of the "About Phone" screen after restoring stock from non-downgradeable??
This is my second defy and Telstra wouldnt replace my first one because i didnt have the stock ROM. They can tell if its correct or not.

That's what I was thinking, my about screen after going back to the fixed sbf is not the telstra one.
Sent from my MB525 using XDA App

I will when I get a chance, don't suppose anyone could post an about screenshot of the stock telstra one.
Sent from my MB525 using XDA App

I suppose it depends on which tech you get at telstra, some will report it, others will just fix it.
I bricked mine while trying to produce a bufer overflow and divide by zero in the locked bootloader. Was getting some results until it bricked

This is what my about screen has after restoring nandroid and flashing fixed Telstra sbf.
System version: Blur_Version.2.26.0.MB525.Telstra.en.AU
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.03.00
Kernel version: 2.6.29
[email protected] #1
BPFlex version: USAJRDNEMARAB1BTEL02A.OR
APFlex version: GAS_ASIA_USAJORDANTELSTRA_P033
Build number: JRNEM_U3_2.26.0
I would be intetested so see what a stock Telstra one says.
For now I've returned to Beta3 CM7. I had basically done the same as you to install, only difference is I used this fixed sbf, 3.4.2_155-002_DEBLUR
Cheers

I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen

Thanks, I think the main one that will be different is the kernel version.
Sent from my MB525 using XDA App

Help...
The rom is perfect, very fast, so far so stable. Only
I noticed 2 bugs so far. 1. The camera's zoom, but that nothing
affects. 2. Skype does not connect here, / does anyone know how to solve
this? Put username and password, starts to connect, it restarts.
Someone managed to solve this problem?
CM7 Beta 4.1
Congratulations Quarx
Thanks

Hey, first of all thanks heaps for making this guide, thanks to you CM7 is finally running on my Defy. I have one problem though and just wanted to see if anyone else did: I can't play youtube on my Defy at all (through the app or m.youtube.com).
Is everyone else having this issue?
*Edit* I've seen a lot of forum posts from mid-last year relating to this, is this issue still unresolved or could this be a bug in the Defy CM7 port?
I've discovered that it will play youtube (both wifi and 3G) but it will only play HQ videos... While inconvenient, I can work with that

Thanks for the how-to+

Dazmonic said:
3. Install 2nd-init (App is on market or below)
Click to expand...
Click to collapse
For the idiots like me out there installing 2nd-init from the market isnt enough you have to run the file aswell by installing it from inside the 2nd-init program itself, i needed to reset my phone after using super one click for 2nd-init to be granted "superuser status" so it would run properly.
Also once you've chosen the cryogen mod file from the bootloader you can then go back to install the google apps file.
After stuffing up the 2nd init program I needed to reflash the origional telstra files, then repeat the guide.
All seems good now, and thanks alot for the guide. I'm sure i would have really botched it up with out it.

Dazmonic said:
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Click to expand...
Click to collapse
Have you changed back yet?
Sent from my MB525 using XDA App

hj all !
can u give me link download room fix sbf of KOREA ? i can't download it on 4share,because it's emty..
thanks bro

Dazmonic said:
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
Click to expand...
Click to collapse
My Defy is in the post and I will try install Cyanogen when I get it, however I would also like to try a blur free Froyo Rom so I was planning on installing the Nordic fixed ROM in step 5. and having a play with it before continuing the process. Is this possible or will I get a bootloop like you mention in step 6? Is the Froyo ROM used in step 5. useable or not?

Dazmonic said:
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
Click to expand...
Click to collapse
Has anyone got a copy of this SFB they could upload somewhere? It looks like all 4shared data has been pulled... see the updated 1st post here: http://forum.xda-developers.com/showthread.php?t=966537
I'd love to get a copy of this SFB so I can do these instructions by the book...
Thanks

Is there another SBF we could use besides the korean one? Does it mean if we use another SBF then we won't be able to flash back to the default telstra one?

****, Telstra are actually checking firmware versions before repairing known issues like the earpiece?
I flashed the China Froyo ROM from ages ago. Probably not downgrade-able huh. Does the upgrade to CM7 process change if you're already on Froyo?

Official 2.2, looking for some CM7 goodness
Hi guys,
I found this page to be a godsend, detailing exactly what i want for my device.
problem is now that Tesltra have updated to 2.2 and the links to the Korean fixed file seem to have all been nuked, im not sure what to do, im a super noob (yes i watched the intro video
I have rooted and flashed CM7 on my desire and want it on my Defy!
so if someone could kindly explain what substitutions (if any) are needed or a link to the files required as from what i understand, if you flash to an official 2.2rom larger then 50MB then you cant downgrade to factory ?
TLR Have Telstra Defy with Telstra 2.2 want CM7 - Halp please

[Q] General rooting and ROM questions

Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks

http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!

Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?

K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.

did you debrand? http://forum.xda-developers.com/showthread.php?t=835777

Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!

Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!

Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.

deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.

makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.

redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?

G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF

i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.

[Q] [SOLVED] Is my radio bricked? device no longer sees ANY SIM

-I have true s-off, permaroot and superCID
-ENG hboot and CWM work fine
-can successfully load and run ROMs
Device no longer sees a SIM card, yet been testing various ROMs for over 6 months with this handset.
I've taken it apart , and SIM slot looks ok.
I've tried eft wipe, superwipe, all my working nandroids, updated radio (currently running cm9/aokp40) to no avail.
Can anyone point me to how I can determine whether this is a S/W or H/W issue?
I'm leaning towards downgrading to stock/s-on then repeating the unlock to re-set my unlocked status for lack of any other options.
While googling not finding much if anything on radio data, so thanks in advance.
IF this is S/W based and you can help to fix I've a working TP2 in box as a reward/incentive.

If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.

kbeezie said:
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
Click to expand...
Click to collapse
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.

igor45 said:
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
Click to expand...
Click to collapse
I noticed that it said "only for 2.7.13", though that seems to be specifically for a version of MUIU.
though when I unpack the fix :
Code:
assert(getprop("ro.product.device") == "vision" || getprop("ro.build.product") == "vision");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
unmount("/system");
Which basically only verifies that the phone is a HTC Vision (as per existing build.prop), mounts the /system partition, then extracts the package's content of /system to your rom
in this case a single file:
/system/framework/framework-res.apk
So from just that, I can't really see the fix having a prolong effect on all your other roms, unless you failed to do a full wipe (factory reset and wipe cache/dalvik cache in recovery before flashing a brand new rom).

This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>

v1r0x said:
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
Click to expand...
Click to collapse
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.

kbeezie said:
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
Click to expand...
Click to collapse
Yes. Maybe it's just coincidence..
But I hope there is a fix for that problem.

Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app

igor45 said:
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.

igor45 said:
I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Click to expand...
Click to collapse
which file do you mean with that?

igor45 said:
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
Click to expand...
Click to collapse
Can you be more specific on the EliteMod part, are you simply talking bout the EliteMod ICS rom, or putting EliteKernel on top of a CM9 or AOKP port? (if just the rom, I'm not aware of a 'fix' that was meant for EliteMod).

v1r0x said:
which file do you mean with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
... maybe something in yozgats file?

igor45 said:
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
though I see it doesn't include the fix... maybe something in yozgats file?
Click to expand...
Click to collapse
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.

to clarify
kbeezie said:
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
Click to expand...
Click to collapse
LOL - bit of a noob here though not that bad, so no I didn't mix fixes/ROMs :highfive:
I was on latest Elitemod/CM9/AOKP
To be clear,
1 - I first flashed the file from post 74 in the thread that included the bugfixes and few enhancements to the original.
(So wondering whether there's something in that file, and yes it does include the fix)
----this is where "no sim inserted" occurs---
2 - when ROM came up good but no SIM, i reverted to my nandroids, trying each one of them.
3 - then tried full wipes with fresh ROM flashes
4 - then tried superwipe/efs wipe AND updated radio and tried each nandroid/fresh installs again
5 - now downgraded radio to what I had (minus the rils) and living with WIFI only connection til I can fix the SIM issue

btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.

kbeezie said:
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
Click to expand...
Click to collapse
Yes understood that the "fix" was a trivial patch and that it pplies only to the MIUI multilang version in question - trust me I would not have mixed those two up. I opted to first flash the version from the later post since it included app/framework enhancements WITH the "no service fix"
Yes I was on Elitemod ICS (AOKP base) with modified CM9 kernel. Sorry for that confusion.
I'd previously used Elitemod AND AOKPs with my old radio with no issues whatsoever. never had to tweak a thing.
FWIW I'm on hboot .84.2000 ENG s-off and yes using clockworkmod recovery
I'd like to try 4ext - looking into it now.
Appreciate the help.
Maybe I'll put this on hold til I get a new sim from FIDO...

igor45 said:
Maybe I'll put this on hold til I get a new sim from FIDO...
Click to expand...
Click to collapse
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.

kbeezie said:
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
Click to expand...
Click to collapse
Indeed - still hoping that there's someone that can offer a method of testing to see whether its a H/W issue. Must be somethng in adb and/or bootlogs? Perhaps in the bootloader for Radio.

well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium

demkantor said:
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thx for the suggestions
Have my sim working in my backup phone and works in every other phone I've tried. Yes have also tried airplane mode on/off data on/off - etc...
Did try to unroot yesterday but ran out of time, had to run off to work.
Want to do it right so will try again today as I've a bit more time.
playing with diagnostics menu now thanks.