Develop Bugs

[Q] Several Noobish questions

i have a couple of questions that are burning a hole in my head so i need to let loose with them.
1)
how can i tell what rom i flashed? i know dumb a$$ question but i forgot which rom i flashed since it was one that came out the night 2.2 official was dumped and it was the first stock 2.2 deodexed released.
i have several (ok a crap load) downloaded and a few on my sdcard. how can i tell which stock deodexed 2.2 rom i flashed? is there an app that will tell me. Phone's software info doesnt have the authors name in the version name, so i cant tell which.
2)
i want to try a few other rom's but dont want to lose the rom i have because everyting works 100% and i like that, regardless of who makes the rom.
what can i use to backup my current phone memory so that if i dont like the other roms i can just revert back.
nand backup doesnt do this right? (even though the size of the backup to me denotes it just might be the ticket)
3)
is there an app, via market, here, or sdk tools/emulator where i can take and tweak the speed at which things open.
its my thought that many roms are faster because the opening speed is altered so things open faster. just like you can do in LauncherPro.
is there a way that i can do this within the phone or externally to a file or two and then adb it back to the phone?
4)
i will add more, i am forgetting some i know.

1) well i can tell you what kernel, by going to about phone> software info
2)use rom manager when installing new rom, and itll ask u to make a backup, so when ever u want to go back to the old rom, restoe u last backup
3)i dont know about open close speed, but for phone speed itself, use setCPU and that controls how much of the CPU is being used when its (charging, screen off, etc.)

thanks Rocklee,
1)
kernel is easy, but i guess that doesnt really tell me which rom right? well not directly.
2.6.32.15-g746f4f0
[email protected] #58
2)
i thought rom manager wasnt recommended much anymore? this is just things i read, probably just certain roms i suppose. i really dont see amny people talking about it. and it does only support a few roms in terms of downloading.
3)
setcpu wont effect the opening/closing speed in the manor that i spoke of but good call. i guess because launcherpro can adjust the opening speed of certain things i assumed Sense had that ability hidden somewhere too.

v_lestat said:
thanks Rocklee,
1)
kernel is easy, but i guess that doesnt really tell me which rom right? well not directly.
2.6.32.15-g746f4f0
[email protected] #58
2)
i thought rom manager wasnt recommended much anymore? this is just things i read, probably just certain roms i suppose. i really dont see amny people talking about it. and it does only support a few roms in terms of downloading.
3)
setcpu wont effect the opening/closing speed in the manor that i spoke of but good call. i guess because launcherpro can adjust the opening speed of certain things i assumed Sense had that ability hidden somewhere too.
Click to expand...
Click to collapse
2) ROM Manager is just fine. If you buy into the rumors about ClockworkMod not wiping correctly, just flash Amon RA instead, you can use either one with RM. You can download ROMs over the normal Internet, too, you know. Just copy them to the root of your SD card.

v_lestat said:
thanks Rocklee,
1)
kernel is easy, but i guess that doesnt really tell me which rom right? well not directly.
2.6.32.15-g746f4f0
[email protected] #58
2)
i thought rom manager wasnt recommended much anymore? this is just things i read, probably just certain roms i suppose. i really dont see amny people talking about it. and it does only support a few roms in terms of downloading.
3)
setcpu wont effect the opening/closing speed in the manor that i spoke of but good call. i guess because launcherpro can adjust the opening speed of certain things i assumed Sense had that ability hidden somewhere too.
Click to expand...
Click to collapse
1 - check the software information screen under software number - some devs put their infor there - mine says "Baked Snack 1.2.5" telling me exactly what ROM I'm using.
2 - I don't use ROM Manager anymore because frankly, I just don't trust it. I don't know what it's wiping when it says clear cache, and there have been too many questions with how efective it wipes, even through recovery. Having said that, if you do want to back up, I would recommend not doing it through rom manager, but directly through recovery instead (hold volume down and power with the phone off). From here, you can nand a full backup, and also restore that backup to get your phone to the exact same state it was in if you screw up somewhere.
3 - nothing on this - pretty sure that's specific to launcherpro.

Thanks for the reply
Yup I am aware of everything you just mentioned.
I just didn't think a nand backup would restore if you flashed a new rom.
Sent from my Android for Telechips TCC8900 Evaluation Board (US) using XDA App

v_lestat said:
Thanks for the reply
Yup I am aware of everything you just mentioned.
I just didn't think a nand backup would restore if you flashed a new rom.
Sent from my Android for Telechips TCC8900 Evaluation Board (US) using XDA App
Click to expand...
Click to collapse
Just a quick tip using Nand....once you create a backup, plug your phone in to your computer, go on to your SD card in the folder named "nanadroid" open it and then open the folder with your device name on it and "rename" your backup to whatever you want. I created about 5 backups and then I wanted to flash a previous one and couldnt figure out which file was which lol. Oh and remember not to use spaces when renaming....use_underscores.

Launcherpro has setting that controls open and close speed. Stock is set at 4, but I set mine at 10, and everything is instant.
Edit: disregard, I didn't read your questions fully, sorry. Didn't see you mentioned Launcherpro.
Sent from my PC36100 using XDA App

[Q] What to do after rooting?

So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics

Become a flashaholic like the rest of us. BTW once start you can't stop.
Best advice I can give is to read, read, read and then read some more. Trust me the answers to your questions are in the 1000000s of pages.
Myn's ROM is very good. But I like Caulkins ROM the best with netarchy's 4.2.1 kernel. You don't want to use setCPU with 4.2.1 its not needed.
Just my 2 cents.
And then for some real fun start playing with the CM 6.1 RC1. That's were the fun really begins.
Sent from my PC36100 using XDA App

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
The first thing I did was to start flashing custom ROMS. In the early EVO days, there weren't many choices. Now, there are tons of good options out there, so get to flashin'! You'll also get lots of good ideas hanging out in the themes and mods forum. Stroll around in the "post your screens" thread and you'll be blown away by what some folks have accomplished.
Just my thoughts, of course, I suspect you'll get lots of other suggestions.

yea unfortunately lots of these terms are like a foreign langauge to me =\
after looking up the process of installing roms i see lots of people are saying do a nandroid back up and then copying the rom, radio/WIMAX/PRI/NV updates and kernel
the definitions/translations for that?

Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app

jacoballen22 said:
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
Using a custom ROM (or kernel) or boot animation is done through "flashing." Flashing is done via Recovery which can be accessed by the steps listed in a post above. I use the Amon Ra recovery and there are directions how to isntall this elsewhere on the site. I copy the ROM (or kernel or boot anim) to the root of my SD Card, boot into recovery, nandroid backup, wipe caches, wipe data, then I can specify an option to boot from zip on sdcard. (don't remember if it's high-level menu item or not) Anyway, find a Recovery you like (Clockwork or Amon Ra) and there will be specific directions on everything you can do on that Recovery's thread.
This is really a condensed version and there's way better and more thorough advice in Development and Q & A forums in stickies. I highly recommend reading those.

Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah

I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app

jacoballen22 said:
I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Hopefully you didn't "just" wipe battery stats - there's a process;
It should be done as follows (copied/summarized from the cyanogen wiki found here);
Battery recalibration
1. Charge the phone to full battery; let it keep charging until the battery says it is fully charged. Do not just wait until the light is green, it isn't always fully charged, causing a lot of inaccuracies. (You can check by going to: Settings -> About Phone -> Status -> Battery Level = Full.)
2. Wipe battery stats with Amon_Ra or ClockworkMod recoveries.
NOTE: To have the most accurate of battery stats, reboot the phone immediately after wiping the battery stats and wait for it to boot completely to the desktop. Once your entire boot is done and you have full access to the phone, go ahead and pull the charger and continue with this troubleshooter.
1. Do not charge the phone until after draining the battery completely, resulting in it automatically shutting off.
2. Recharge the phone completely and then use as you normally would.

I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector

6uPMAH said:
Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.
Click to expand...
Click to collapse
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?

Brutal-Force said:
I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector
Click to expand...
Click to collapse
good looks! the terms are IMO the most important thing to get a hold of

R1pTheJacka said:
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?
Click to expand...
Click to collapse
Is Nandroid back up the same that Titanium pro back up does?
fachadick said:
Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah
Click to expand...
Click to collapse
How do you do this?
fachadick said:
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Click to expand...
Click to collapse
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!

phillip623 said:
Is Nandroid back up the same that Titanium pro back up does?
How do you do this?
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!
Click to expand...
Click to collapse
Nandroid isn't the same thing as titanium, think of nandroid as an image, sort of like a disk image or a windows restore point. Once restored, it will take you back to exactly where you were at the time of the backup.
The numbers that you see in Rom Manager represent the recovery version. You currently have clockworkmod version 2.5.0.1 installed.
It's been spelled out above, and elsewhere through the forums, but I'm bored and I want to clean up this post anyway (I tried that new 8whatever keyboard again - still hate it. And before I cleaned it up, this post was three paragraphs of broken english), so here are some basic steps spelled out on what to do immediately after rooting, along with some terms.
The first thing you want to do once rooted is go into rom manager, and towards the bottom, hit the option that says "Flash Alternate Recovery". Once you do this, you'll notice at the top where it used to say Current Recovery: ClockworkMod 2.5.0.1 it will now say Current Recovery: Ra Recovery 1.8.0.
Now close out Rom Manager, and turn off the phone. Turn it back on while pressing down on the volume. The screen with the skateboarding Andy's will show up - this is the hboot screen. Among other things, this screen will tell you the version of hboot you're running, and whether you're S-ON or S-OFF. There may be a few different options listed here, but we're only interested in the one that says Recovery.
Select Recovery. The phone will reboot, and you should end up on a screen with green text. At the top it will say Android System Recovery, and all the way at the bottom, it will say Build : RA-evo-v1.8.0 From here select Backup/Restore. There are a few options, but note the two important ones - Nand backup, and Nand restore. Select Nand backup. It will ask if you're sure, so say yes. It will take awhile and the bottom of the screen will fill with dots. When it's done select Return then Reboot System Now. Congratulations, You just performed your first Nand Backup using Amon Ra recovery.
When you can, mount your phone as a drive, and go into folder inside the nandroid folder on your sdcard. You'll see a folder with today's date. Copy it somewhere safe on your computer. If you're interested, you can look in that folder and note the wimax.img file - this is where you're backing up the infamous RSA Keys (I'm not explaining what that is here, just know that you REALLY want to have this backed up, and kept somewhere safe). once the copying is done, unmount as a drive, and disconnect from your computer. Congratulations, now it's playtime.
Use either Titaniaum Backup or MyBackup Pro to back up all of your apps and data. Mybackup Pro will also backup call logs and text messages and things like that - I'm pretty sure Titanium does also, but I'm not sure. Your contacts should be backed up to google for easy restoration later.
Head over to the dev section and find a ROM that appeals to you. You can go with completely stock rooted if you want (which is essentially where you are now, but stock rooted would have the latest OTA updates when they come out), or stock with some tweaks to Sense, or non Sense at all (the most popular of these is CM, which rebuilds Froyo from the ground up.) Sense refers the stock launcher called Rosie, as well as some buried functionality in the phone - for example the mail, calendar, and dialer apps look and act different between Fresh and CM roms. Sense is a UI developed by HTC to go over what is commonly referred to as vanilla android/AOSP. AOSP stands for Android Open Source Project and is what google released on the n1, CM is an AOSP rom. Also, you're looking for a Deodexed rom (as opposed to odexed) so you can theme it later if you want.
Once you find a rom you like, download it to the root of your sd card (you may want to download it on your computer and move it to your sdcard). Refer to the above to get back into recovery, but this time instead of selecting Backup/Restore, select Wipe. Select Wipe data/factory Reset and let it do its things, then select Wipe cache, and let it do it's thing, then select Wipe Dalvic-cache, and let it do it's thing. What you've just done is erased all of the personal and superfluous data that was in the phone - you want to make sure that when you load the new rom, you're loading it on an empty slate, and that there's nothing of your old data left that could possibly corrupt something in the new rom. Some people say to wipe all of those options 2 or even 3 times each - I don't buy that though. Also, don't worry about the other wipe options you had there. Not needed now.
So once you've wiped, hit return, and select Flash zip from sdcard. It will pull up a list of .zip files found on the root of your sdcard. select the rom you just downloaded, and let it install. This may take a while. Don't freak. Once it's done, select Reboot system now. This will take a while too, maybe even a few minutes. Don't freak. Once it eventually boots up, restore all of your stuff with either Titanium or MyBackup Pro. Congratulations, You just flashed your first rom.
Now head over to the themes and apps section. Find a theme that interests you. Make sure its compatible with your rom (either sense or cm) and download it. Flash this the same way you flashed your rom, but you may or may not need to wipe first. Always refer to the op of those threads for specific instructions.
Finally and most importantly - head over to the thread in my sig and find a new font you like. All the cool kids are doing it. When you find one you like, copy it to your sdcard and flash it the same way you've been flashing everything else. You don't need to wipe anything for those though.
Tips;
1: never forget to wipe. As a rule, when flashing roms, you'll be wiping what people refer to as all three - that means wipe data/factory reset, wipe cache, and wipe dalvic cache. When flashing kernels or themes, you'll generally just be wiping cache and dalvic cache. Again though, always refer to the instructions in the op in which you found whatever it is your flashing.
2: if you'll be flashing both themes and roms, and possibly kernels, never flash in the same recovery session. So rom first, full reboot, then kernel, full reboot, then theme, full reboot. In that order, wiping and rewiping as needed.
3: give you're rom at least a few days before you give up on it, most need time to settle into your phone so to speak, and need a few battery cycles to get to peak performance, which brings up to
4: You should wipe your battery stats whenever you flash a new rom. Remember you saw that option under Wipe back in recovery? Well now you get to use it. I posed the link and process above in the thread.
5: At this point most people use Amon Ra instead of clockworkmod because there seems to be uncertainty as to weather or not clockworkmod correctly wipes. ONLY Amon Ra backs up the wimax.img, clockwork does not.
6: rom manager is a graphical front end for clockworkmod. A lot of people still use it to flash, becasue it's so easy to use, it can be used to download roms directly in the app, and doesn't require the zip file to be on the root of the sdcard - it van be anywhere on the card. Don't forget though, you can download the rom through the app if you want, but still switch to amon ra to flash it.
7: you cannot restore a nand backup you make with amon ra with clockwork, and you cannot restore a nand backup you make with clockwork with amonra.
8: on the off chance you need to change your hboot version for any reason, you can only restore nand backups with the same hboot version that they were backed up with. NOTE, were talking about hboot here, not recovery.
Damn, that was a lot of of text. Sorry about that.

i would recommend reading this thread: http://forum.xda-developers.com/showthread.php?t=790427
i have only been in the android world for about 3 months now, and was able to root and flash custom roms with ease within a few weeks of getting my evo. its really not hard at all once you understand the process.
as far as what rom to flash, that depends on the user. different rom have different features. if i were you, i would recommend reading the specs on each rom before flashing. some may have features missing, such as 4G, full camera support and such. And usually all that info is provided in the thread along with the rom. so, pay attention to that.
as for me, the goal for rooting was to do certain things that was only possible with root. such as, Nandroid backup, ShootMe, Wifi Tether and to disable some of the Sprint apps. so, i am using a stocked rooted rom. it is what it says. the same stock rom as the factory but rooted.
a lot of ppl use various custom roms to get better battery life. battery life on stock roms have improved quiet a bit lately. at least in the past 3 months, i have noticed a big improvement. hope this helps answer some questions.
and remember to always do a nandroid backup. i also use My Backup Pro to backup my Call Logs, SMS & MMS.

few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?

ok, so titanium pro will backup everything, even how your homescreen is set up.
the nandroid is for if there is a problem, or if you want to go back. ALWAYS HAVE AT LEAST ONE BACKUP MADE WITH AMON AT ALL TIMES OR YOU COULD PERMANENTLY LOSE 4G (FOREVER, NO FIX EVER)
rom manager can control clockwork recovery while booted up in a touch screen interface. it removes the need to use the annoying volume keys. doesnt work with amon.
i would highly reccomend amon to you. it is just that much better, but doesnt work with rom manager. volume keys arent that hard anyways. use amon.
ONCE AGAIN, ALWAYS HAVE AT LEAST ONE AMON BAKCUP AT ALL TIMES, AND ALWAYS BACKUP BEFORE DOING ANYTHING EVEN SLIGHTLY CONSIDERED MODDING. SERIOUSLY, TAKE 4 MINUTES OUT OF YOUR DAY TO WATCH DOTS APPEAR, AND SAVE YOURSELF 200 DOLLARS OR HOURS OF SETTING STUFF BACK UP. SERIOUSLY. DO IT.

Thanks for the detailed and informative post! This should be in the question and answer thread. I'm finally able to change my font and onto ROMS. I'll reply back once I'm on a normal keyboard.

R1pTheJacka said:
few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?
Click to expand...
Click to collapse
1. all your contacts are backup-ed on your google account. when you sign on to the google account after you flash a new rom, the contacts will be automatically downloaded to the phone. so, no further work needed to be done there. i use My Backup Pro to backup my SMS/MMS and Call logs. I think it is very similar to Titanium. Basically you use the program to backup the stuff you need onto your SD Card. Then, once you have flashed your new rom, you install Titanium or the My Backup Pro and use the Restore feature to restore what you need. As far as Apps go, I found that it was better to use App Brain, since that keeps a log of all the apps install on the phone, its usually a breeze to re-install all of them through that.
2. Amon RA & Clockwork perform the same function. you use either to flash custom roms, perform nandroid backups, etc. so, once you root your phone, you will need to install one of these.
3. ROM Manager.. does what the name says it does. you can change the rom on your phone using that utility app. But i think the Amon Ra/Clockwork Recovery method is the preferred way of changing out roms.

[Q] Titanium Backup Not Freezing?

OK, the preface:
1. Rooted the EVO 4G phone with Unrevoked3.
2. It worked, ClockworkMod Recovery is in place - phone says S-OFF on hboot. I did a nand backup successfully.
3. Installed Wireless Tether, works fine.
4. Purchased and installed Titanium Backup Pro - it said I needed Busybox, downloaded it. Everything works fine, did a full backup with it.
5. I like HTC's Sense UI.
Titanium Backup Pro starts fine, reports everything as "OK" - that I'm rooted, the super user app runs - all looks good. It's behaving as its rooted just fine. I went through the app list and started freezing apps like Amazon MP3, Sprint NFL, and all the other bloated crap that comes from Sprint with this phone.
The problem is - that when I reboot the phone, and go to Advanced Task Killer Free - things like FM Radio, Amazon MP3, News, etc - are showing as running. The Freeze didn't freeze these things - they are still launching.
I'm trying to keep it "just rooted" -- it's all new to me, and I'd rather not have to fart with special ROMs or radios, kernels, etc - I'm old, I'll brick the damn thing. Currently I'm armed with the bookmark to unroot with my RUU PC36IMG.ZIP and some unrevoked-s-on.zip, and that's about it.
So - any help here? How come when I freeze these things, the system still launches them on bootup?

I honestly haven't messed with the "freeze" part of Titanium, but I use an app called "Bloat Freezer" from the market that works perfect. If you dont mind spending a couple bucks, it is well worth the money in my opinion
Heres the link thru AppBrian, its on sale

First suggestion get rid of the advanced task killer - it isn't needed.
Secondly, one of the main reasons to root is to remove the sprint bloatware; you could do it through adb, but I am guessing you will think that is too hard. I thought you could uninstall the bloatware using titantium backup which would be easy.
If you can't uninstall them instead of freezing them, the easiest thing would probably be to flash a custom rom. If you want a stock feel that is very fast with no sprint bloatware - download and install MikFroYo 4.5.

Heaterz16 said:
First suggestion get rid of the advanced task killer - it isn't needed.
Secondly, one of the main reasons to root is to remove the sprint bloatware; you could do it through adb, but I am guessing you will think that is too hard. I thought you could uninstall the bloatware using titantium backup which would be easy.
If you can't uninstall them instead of freezing them, the easiest thing would probably be to flash a custom rom. If you want a stock feel that is very fast with no sprint bloatware - download and install MikFroYo 4.5.
Click to expand...
Click to collapse
I've been reading that if I remove the apps, I run some risk of OTA updates failing or some such. Is that not such a big deal, after all?
I feel confident about rooting and unrooting, reading over those steps a dozen times over. Not so much about custom ROMs and kernels. I read about radio keys possibly getting dorked, making sure you update radios and some other stuff - it starts to get a bit overwhelming - clearing cache, data, dalvik (wtf ever that is), certain features not working (fm radio, 4g, wimax, etc). As it is now, I've managed to root, do a nandroid backup with ClockworkMod Recovery, and a Titanium Backup backup - i feel confident with that.
I really do like the stock Evo 4G - just don't want any of that bloat running. There's no reason Amazon MP3 or Sprint TV should ever want to fire up at random times.
If it was easy to flip into some other ROM and still maintain my stock look, I'd be happy to start researching it. I read some other one was decent too - some Warm TwoPointTwo or something?
I'd like to keep Sense, the basic stock look - and get rid of the bloat.

Like here:
http://forum.xda-developers.com/showthread.php?t=883026
I started reading and my head started spinning with stuff about mods to the MikFroyo 4.5 ROM. NO CLUE how to add any of that or tweak it. Heck, not even a real clue on how to install MikFroyo safely. Is it just a matter of dropping some ZIP on the root of SD card, go to the ClockworkMod and update something or other? I guess I have much more reading ahead of me.
One question I do have -- when I do a backup with the ClockworkMod recovery -- is that everything? Is that my "safe checkpoint" - so if I screw something up, I can restore from that point?
I guess if I biff it entirely, I can always roll back to unrooted stock with that PC36IMG.ZIP and unrevoked-s-off.zip file.

It is a bit overwhelming, I would highly recommend running MikFroyo 4.5 - it is pretty stock feel with some extra eye candy and a whole bunch of mods that make it very speedy.
There are so many links in that thread so, here is the direct link to download MikFroyo 4.5: http://www.mediafire.com/?4v1tz1y3f0nwgwa
1.Download that file to your computer
2.Connect phone, select dropdown and enable usb disk drive
3.On computer right-click the mikfroyo file you downloaded and send it to your phone (i.e. - whatever drive your computer list it as, maybe E:\)
4.That will put the Rom file (which is a .zip file) on the ROOT of your sdcard [Root - meaning the file is not located in any folders on the sdcard]
5. Change usb connection to charge only
6.Boot into recovery
7.Make a full backup of your current Rom (Probably called Backup/Restore Menu in Recovery)
8. AFTER you make a backup, you are still in recovery - now select wipe Data/Factory Reset
9. After that wipe is complete, select wipe cache/dalvik-cache
10. Now, in recovery go back a menu or so and select Flash zip from sdcard, find the mikfroyo rom file you put on the sdcard and select it, Yes, to flash it.
11. Once it is finished, select reboot system now in your recovery
12. Be very patient while booting - can take 5 mins or more sometimes.
13. Once booted, update google info and then go to market and download Titantium Backup and restore the apps you want that you orginally backed up.
That is a very detailed step by step.
Note: Do NOT try to flash anything with battery less than 30%

Wifflepig said:
I've been reading that if I remove the apps, I run some risk of OTA updates failing or some such. Is that not such a big deal, after all?
Click to expand...
Click to collapse
NEVER take an OTA update after Root, it could brick your phone.
It isn't a big deal if you remove system apps and it messes something up assuming you have a backup that you can restore through your recovery.

Wifflepig said:
One question I do have -- when I do a backup with the ClockworkMod recovery -- is that everything? Is that my "safe checkpoint" - so if I screw something up, I can restore from that point?
I guess if I biff it entirely, I can always roll back to unrooted stock with that PC36IMG.ZIP and unrevoked-s-off.zip file.
Click to expand...
Click to collapse
I don't recommend Clockwork, many people have issues with it and I don't use it so I am not sure, but some versions of Clockwork don't backup everything (which might include 4g keys, etc)
I recommend this recovery: http://forum.xda-developers.com/showthread.php?t=705026
Read through this rooting guide: http://forum.xda-developers.com/showthread.php?t=829045
See step 6, this will backup your 4G unique keys:
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.

Heaterz16 said:
NEVER take an OTA update after Root, it could brick your phone.
It isn't a big deal if you remove system apps and it messes something up assuming you have a backup that you can restore through your recovery.
Click to expand...
Click to collapse
How the heck do you block OTA updates?

how to back up all internal memary
i use titanium backup how to back up internal software and how to restore tham

Also - I already rooted with Unrevoked3 and it put the ClockworkMod Recovery on the Evo 4G (it's hardware 0003). Everything *seems* to be working fine.
If I decide to go back to unrooted (s-on and the pc36img.zip for my phone) - do I need to worry about my wimax RSA keys at all, or can I just flash s-on then the PC36IMG zip and be back to square one?

Attached to the message is a copy of my nandroid backup from clockwork - it sure seems like it backed up the wimax image for me.
Also, just to be safe, I did do the ADB shell to make an RSA_oem.key file - it was 4575kb, in my root folder.
I swear, it sure seems like things are fine. I'm a little apphrehensive about trying to flopswitch to a different recovery tool if things are working as expected. I fired up the 4G antenna, and it came on and tried searching for 4G (I am not in a 4G zone at the moment).
I still have one remaining question - how do I block OTA updates from Sprint, to avoid them hosing the phone? I didn't see anything obvious in the Update Phone bits.

You should be fine running Clockwork - I just recommend Amon.
Glad to see you backed up your RSA keys and I agree it looks like you have a good Wimax.img. You only need either of these if somehow flashing another Rom messes up your 4g - you should be ok, just good to have just in case...
As for blocking OTA updates I haven't had any OTA updates since I have had the EVO, but they don't auto-install, you can just decline them if the message ever pops up.
As long as 4g keys are intact when/if you want to unroot, then all you have to do is run S-on and then restore the ruu as you stated.
Sounds like you definitely have your 4g keys and wimax intact, but you can always download Wimax Keys Checker from the Market for good measure as well to check.
Glad to hear everything looks good - are you going to try MikFroyo?

Heaterz16 said:
You should be fine running Clockwork - I just recommend Amon.
Glad to hear everything looks good - are you going to try MikFroyo?
Click to expand...
Click to collapse
when my testicles grow a few sizes more and I've done more reading and research. I hear nothing but good things about MikFroyo 4.5, and I'm at about page 30 of his 1000+ page home post. I spent two weeks reading everything under the sun just to get to a stage where I felt reasonably confident in rooting.

Wifflepig said:
when my testicles grow a few sizes more and I've done more reading and research. I hear nothing but good things about MikFroyo 4.5, and I'm at about page 30 of his 1000+ page home post. I spent two weeks reading everything under the sun just to get to a stage where I felt reasonably confident in rooting.
Click to expand...
Click to collapse
I just got a serious lawl from reading that...soon my young user. But if you're on a sense rom, just don't accept the OTA, and if you're on aosp, it doesn't even ask you.

Wifflepig said:
when my testicles grow a few sizes more and I've done more reading and research. I hear nothing but good things about MikFroyo 4.5, and I'm at about page 30 of his 1000+ page home post. I spent two weeks reading everything under the sun just to get to a stage where I felt reasonably confident in rooting.
Click to expand...
Click to collapse
Haha, well you already did the hard part, rooting. Chances of bricking it now are about slim to none, unless you pull the battery during a flash of a rom. Worst case scenario, you get a bootloop because you forgot to wipe first or something, which is easily fixable.
If you want to read up on his thread, I would read starting on last page and read backwards. Otherwise, you will read all the issues in the original version of MikFroyo, the current 4.5 is virtually flawless.
Btw, I am glad to see you are willing to read before you do things - most people don't.

I'll probably tackle a custom ROM (MikFroyo 4.5) next week. From what I'm reading, it's all about staging a ZIP or image to the root, and using the boot tool to flash it into the system. That, and be careful about radio keys, and the like. Seems uncomplicated enough.
Thanks to both of you for the help, I do appreciate it a lot. I've not been impressed with TitaniumBackup's freezing - a buncha junk still fires off on reboot of the phone - I'll try the AppBrain one here, I think. TB works good for backing crap up, though. As far as I can tell - haven't needed to restore anything yet - but it does definitely make a crapton of files in the backup process, so that's a good thing - I guess.

[Q] RA Recovery... Help

Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid

Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I don't know the name it needs to be. But if you need stock rom Ruu sense to unroot I have links to the latest Ruu you would need in my guide.

Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I was actually at a restaurant eating dinner when I was initially replying to your post and then all of a sudden, my phone rebooted and kept bootlooping so I had to rewipe and restore a nandroid backup while driving home...Sorry. Anyway, you cannot rename the folder which the nandroid backups are kept in, but you can rename the backups themselves as long as you don't use special characters. If you did change the name of the folder that the nandroids are in, you will not be able to restore. If you remember the name of the folder, change the name back to what it was. If you're familiar with ADB, connect your device to your computer, start the Terminal app (I use a MacBook) and then type, "adb connect". It *should* display the name of your device which is the same name as the folder that the nandroids are kept in.

Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.

k2buckley said:
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!

Skid71 said:
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Click to expand...
Click to collapse
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.

Yes, I confirmed that the name of that folder should indeed be the serial number of your phone, in all capital letters. To get your serial number, you can either use adb, by typing 'adb devices', and the number it gives back to you will be your serial. If not, shut your phone down and pull your battery. Your serial number is back there. If you rename that folder with your serial number, you should be good to go (hopefully). Give it a shot.
Edit: And just to clarify, the one you CAN rename, is the BDS-20110525 one. Just be sure to not have any spaces in the name, or odd characters, as has already been noted. You should be on the right track after that.

k2buckley said:
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Click to expand...
Click to collapse
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
**Edit** I did use a - when renaming the Sense ROM. No spaces. That sound alright?
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid

Skid71 said:
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Click to expand...
Click to collapse
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
EDIT: forgot to answer your second question:
To be honest, I don't use Amon Ra 2.3. I have always stayed with the earlier version of 1.8.0, as it has NEVER faild me, so I saw no reason to change it. It is slightly different than the version you're on, as there are no backup options. It just automatically backs up what it needs to. With your version you do have the option to select what you backup. I for sure would make a couple backups that include your wimax.img. That is important to have, for if you ever lose your RSA keys, that backup of the wimax.img is how you would recover them. You would only need to include sd-ext if your sd card is partitioned, and you're using DT a2sd. If you are, then including the sd-ext is a must. If you don't have your card partitioned, or don't know what DT a2sd is, then you don't need to worry about backing up your sd-ext. I honestly don't recall what the other options are, and hopefully someone else who actively uses that recovery will help ya with that. I believe I remember there being an android_secure, recovery, or something like that. Sorry. Just definitely include the wimax.img. I believe that my friend Dougjamal posted something in the General section about the recommended way to backup using Amon Ra. Search that out, and you may find the answers. Good luck

Here's how I rename my nandroids and it works.
\nandroid\HT121HL07014\BDEARS-20110318-0300-koni_III
Anything else i Ever tried = fail

k2buckley said:
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
Click to expand...
Click to collapse
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.

Skid71 said:
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Click to expand...
Click to collapse
Well, I think you should be all set. If not, this is what I would do. Take both of your nandroid backups (the folder labeled BDS-2011....) and copy them to a different folder.
Then be sure you have a directory on your sd card named: nandroid/(your serial number). Then place both of your nandroid backups in that folder. (the one with your serial number). Then boot to recovery, and select backup/restore. Then select 'restore backup'. You should then see the folder named as your serial number. Select it. You should then see your backups. Select the one you want to restore, and try to do it. It should work.

k2buckley said:
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
(laughing)....You know it's not a big deal with me. As much as we post in these forums, it's a surety that we will post similar replies around the same time. As for the rom, it was SalvageMod. It hadn't happen prior to today and it haven't happened since. I was eating and replying from inside a Cracker Barrel restaurant when it occurred....lol
posting & replying via the XDA Premium app.

Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid

Skid71 said:
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Click to expand...
Click to collapse
You're very welcome, my friend. Before purchasing my Droid Incredible last year, I was a die-hard Blackberry user. (First Blackberry was the 7290 and the last one was the original Bold 9000 with several other models in between). After I rooted the D-Inc, I realized that the capabilities with Android devices were vast. I then wanted a larger screen and was torn between the Droid X and the EVO. Being that I was already familiar with HTC Sense, I chose the EVO and without doubt, I made the right choice. This device is amazing and through trial and error and from being helped by the good people who frequent these forums, I've learned a great deal and am still learning. I love this community and I try to help others and often as I can. The success rate is less than 100% but the effort is more than that....lol. Anyway, take care and enjoy your day...
posting & replying via the XDA Premium app.

Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App

sand1303 said:
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amon Ra is known to be more reliable. It wipes better, and flashes more reliably. Clockwork works flawlessly for some, but not for all. Amon Ra seems to be nearly flawless for all who use it. Also, if you continue using clockwork, you will surely run into some zips that you cannot flash, such as anything that is scripted with edify. Clockwork only supports amend scripting, and there are still PLENTY of zips out there that are edify only. In that case, clockwork will tell you that it can't flash it, and you need to change the scripting to amend. Amon flashes both amend and edify. Also, the newest clockwork doesn't flash radios for some reason, the flash will just not take.
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.

k2buckley said:
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
Click to expand...
Click to collapse
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App

sand1303 said:
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea, sorry didn't mean to come off harsh. Sorry about that. And yes, Amon Ra doesn't work with rom manager. I won't get started on my opinions on ROM manager, lol
Clockwork jacked up my phone before and left a bad taste in my mouth!

It's all good!
Sent from my PC36100 using XDA App

Confirm Steps & Apps to Install New ROM on G2 (Mimicry 1.3.2)

I have had my G2 for about 18 months and have been running into a lot of issues recently. I've decided to fix those issues by rooting & getting a new ROM installed. I'm a tech savvy guy, but have not done anything on the phone end due to not wanting to break whats working. I've decided to go with the Mimicry 1.3.2 ROM since the install process uses Aroma and is very straight forward. Before I pull the trigger, I just want to make sure I have all the steps clear so that I don't go "Oh sh**" in the middle because I missed a step. There's also a couple of steps that I'm not clear on. Here's what I researched:
-Root phone using HTC's bootloader unlocker
-Format phone's flash memory to EXT4
--What is the best app to do this with? Will my phone work with Gingerbread after I make this change?
-Download Mimicry 1.3.2 and Google Apps put the zip files on my phone (not SD card)
-Power off phone and then push the volume down and power buttons together and choose to install the ROM
-Answer prompts in Aroma (including installing WiFi calling)
-Flash Google apps
--How exactly is that done?
-Restart phone and start setting up apps again.
Does that look correct and is there anything that I'm missing? Thank you in advance for your help.

Well first off I would stay away from HTC official unlocked bootloader, its worthless and will give you headaches in the future
use the wiki to root, either follow the wiki in cyanogen or here on xda, if you even slightly tech savvy it will be easy
following that guide you will have clockwork recovery, but I suggest moving to 4ext recovery, among many reasons is the ability to format to ext4. Otherwise the next easiest way to format would be to flash a super wipe script with ext4 format written to it (just search xda and you'll find it easier)
Now after you are rooted with an engineering s-off hboot consider flash the .19 radio, not super important but many find this to have the best reception and battery life.
Next make sure your SD card is fat32, I also suggest an ext4 partition there as well (easily done through recovery) but skip the swap
Now feel free to flash mimicry, and may I add this is one other best ICS Roms for the vision, and blk_jck is a very helpful Dev as well.
Good luck, if you run into issues there will be answers all over xda, just search a bit, happy flashing!
Sent from my Nexus 7 using xda premium

Thanks
Thanks for the heads up on the HTC bootloader. I'll check out the Wiki on how to PermRoot my phone.

Mimicry, recovery, soft bricks, and new ROM
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers

1.3.2 adds few framework level changes and no device level changes. Definitely nothing that should cause errors or problems booting anyway.
Sent from my HTC Vision using xda premium

Good Info
timram said:
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
Click to expand...
Click to collapse
Thanks for that info. I am taking a look at the Cyanogen Wiki and seeing what I have to do. I'm thinking that I will jump directly to Mimicry 1.3.2 instead of installing Cyanogen 9 first. Hopefully that file doesn't hang out there and causes that boot loop to happen to me (thanks for that explanation, BTW).
So do I have to use that ClockworkMod to load the ROM, or does EXT4 do the same thing (as far as loading the rom goes)?

...where thanks is due
many thx, blk jack, I should have specifically mentioned your awesome contributions as well, and
have remedied with thanks meter as i came/come across it.
Will re-try the 1.3.2 shortly. If I run in to the same glitches, I will try and make note of the specific errors
(or any other bugs, for that matter) and let you know.

Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting

Checking it out now
iamnoobie said:
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
Click to expand...
Click to collapse
I'm actually looking at that wiki right now. I just finished backing up all the contents on my SD card. I can't backup the apps on my phone since it's not rooted, and I can't use a backup app unless I'm root. So it looks like that is a catch 22. Personally, I don't mind wiping everything anyways since I'm going to be making the jump to ICS. I guess I'll have to beat all those levels in cut the rope again :crying:

@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.

timram said:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
Click to expand...
Click to collapse
Thanks for that. I've now downloaded the Android SDK and am now trying to test the connection to my G2 using adb. So far, no connection. Grrrr. I'm looking around now to see how to get my phone detected by adb since it doesn't seem to have anything on the cyanogen wiki.

you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium

HTC Sync
demkantor said:
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried the adb devices command and it didn't return any connected devices. Looking in the xda wiki, they are saying that I need to have HTC Sync installed. I'm downloading that right now. They probably should put that in the cyanogenmod wiki also.

I got my phone detected by adb! I did some preliminary checking and I think I should be good to go on rooting. I think I will root my phone tomorrow when I have plenty of time to troubleshoot any issues that my come up.

This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app

prairie-dad said:
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Click to expand...
Click to collapse
Cyan wiki worked for me! (strawmetal didn't - I blame myself though).
ext4 and mimicry are what I'm running now (after going through CWM, CM 7.2 and CM9 RC1 & RC2) and I'm very happy with both. Mimicry is great!

prairie-dad said:
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium

minor glitches, but rooted and s-off fine
demkantor said:
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
all went well till the very, very, very end. I went to reboot into clockwork recovery, and...nothing doing! holding down the trackball, volume down and power...and waiting and waiting...just got me into the bootloader with no option to go to recovery...just reboot, reboot the boot loader, and power down.
So I thought, maybe I somehow failed to get the recovery img where I wanted it...no big deal. I logged onto the old Market (this is 2.2, after all) and purchased 4ext (which is what seems to be everyone's choice) and installed it. Then I said I wanted to reboot with mimicry and gapps, hit "go," and...it rebooted into ClockworkMod Recovery...where it now sits, I assume backing up the existing system. Mimicry 1.3.2 and gapps images were sitting on my sdcard root, btw.
Very odd, and a little perplexing...I will wait it out a while before powering off and up again.
any thoughts? Must I remove clockwork mod manually (I assume that when I installed 4ext it made itselfthe default recovery method...) or does 4ext just sit atop Clockwork Mod...and what I am seeing now is normal...? I've been waiting a few minutes now, and see nothing but the Clockword Mod icon, the top hat.
Sigh...but pretty clearly almost all the way home.
Thanks to all,
dave

I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium

darn ClockWorkMod/4ext clash!
demkantor said:
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
---------- Post added at 07:33 AM ---------- Previous post was at 06:42 AM ----------
prairie-dad said:
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
Click to expand...
Click to collapse
Mimicry is booting now. All good. I ended up using the clockwork mod version, 3. something, that I installed when following (too slavishly?) the CM wiki's instructions (otherwise excellent!) Then (and now) I have problems booting into the bootloader, and it doesn't show a recovery option... Running 4ext (which I purchased) seems to be great (looks really useful) until rebooting...when CWM comes up instead.
I kept using volume up or down to pick what I wanted, then pushed the power button to select...wrong! It's the trackball you click, which I only hit upon by accident. Once I got that working, I flashed mimicry and Gapps, and I am off to the races again.
Thanks to all, but I want to figure out what is with recovery for the future.
What buttons do I push to get to bootloader...so far all I have gotten to work is via USB cable and "dab reboot boot loader."
dave