Develop Bugs

Developing A Ramdisk (Unpacking & Repacking Boot.img)

I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!

BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...

Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.

Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.

Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan

kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.

lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.

kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.

[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.

Worth rooting?

Hi guys.
Obviously I am new, and noob so this might sound silly, but is it worth rooting?
I mean, I have been having stock Desire Z for, I dunno, almost 2 years, and it's been working perfectly, but since HTC and Google are moving on, leaving me on 2.3 and without any new updates, I was thinking of moving on on my own.
The thing is, I am as noob at rooting as I am in here, and bricking scares the **** out of me. Also, I don't know what ROM to chose, if that is the only thing to chose after rooting. I've stumbled upon cyanogen mod, and there are quite detailed step-by-step description on how to downgrade/root/install CM7, but CM7 looks like crap - I don't like it really.
I do like this http://forum.xda-developers.com/showthread.php?t=1546915http://forum.xda-developers.com/showthread.php?t=1546915 thou,, but since it's still beta, I don't want to end up with half working phone when I need it the most.
So, should I go for it, or stick with my guns?
and thx for replying or even reading :good:

I can't really comment on Sense roms (never cared for them, too bloated in my opinion). But I would prefer either Mimicry 1.3.1 or EliteMod ICS (which I'm using now), in regards to ICS (4.0.*).
Far as guides. Some like the Cyanogenmod one can be 'easier' to read, but the XDA wiki has a lot more information.
http://wiki.cyanogenmod.com/index.php?title=HTC_Vision
Since you're on gingerbread now you would go the Desire-Z Gingerbread route for unlocking/exploit before proceeding to root it. (but on the plus side sticking with a Desire-Z hboot will ensure your /system size is big enough to play with the Sense roms).
With ICS some things to keep in mind is that the most common issues tend to be :
1) Camera isn't "fully" working, in some cases like on mimicry and elitemod (or other non-Sense ICS roms), you can take a picture, you can record a video, but usually only with the stock camera app and usually won't have features like 720p recording or special effects.
2) Graphical glitch with the text can happen on an app, although rarely occurs, is easily fixed by closing the app or restarting (tends to stay with one app when it happens).
Those are probably the two most common issue you'll see with just bout every ICS rom out there for DZ/G2.
By the way some of the Sense roms are incorporating the 3.0 kernel from the Virtuous Infinity Preview (Full Sense 4.0), as such they're getting a decent camera with filters, but course there are still some bugs. (Previously Sense 4.0 roms had no camera functionality at all).
Edit
To clarify, even if you use the CM Wiki to unlock/root you do not have to install Cyanogenmod 7.2 afterwards, you can pretty much install any compatible rom once you've gotten it unlocked and running with a custom recovery (though I prefer 4EXT over clockworkmod).

I am sure it is worth ... i was just like u ..satisfied with my GB but i was so curious and so on so i followed this guide: http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting and now iam rooted at the moment iam running Elite ROM ice cream sandwich and its ********* fast .... when you have root and you try new rom you will never want to stop of course there are some risks but I think that if you will have any kind of problem here on XDA is so many great people willing to help you ... my advice is to do it go step by step according to that guide and if you dont understand something just ask here on xda Best of luck....

back in the g1 days a friend of mine rooted his, i was astonished what could be done to phones now adays. i quickly rooted my g1 and began learning a ton about everything mobile, just like many before and after me i was hooked. even if you never found a better rom than stock the learning process is well worth it. even if you dont use most of the new features available to you at least having them is worth it. and unless you dont research/read first, or are mostly stupid/have bad luck, you wont brick your phone. i have rooted 50~60 phones and tablets, maybe more and never had a hard brick, sure when i first started out there was some close calls but with a little common sense you will be fine, also know you are now part a large community eager to help
so follow the xda or cyanogen wiki and downgrade and root your phone, move on to the rom compilation (found in the developers thread here) try a few roms and see what you prefer. you will be happy you did
on and one last point; the best reason to root your phone right when you get it, if there ever is a problem it is much easier to fix a rooted phone with software/firmware problems then an unrooted one. the only drawback could be if you need to send it back for warranty... but how likely is that, and the phone you have now im sure has little/no warranty left
happy flashing!
follow kbeeize's advice on how to root and try a few roms out

PS: One of the major advantages of having a custom recovery, is the ability to perform a backup of your currently installed rom. If you screw something up, you need only go back into recovery Wipe (factory-reset/cache/etc) and restore the backup to get right back to where you were. And you can have several backups too if you were trying out several different roms.
So basically the process of rooting/unlocking offers a safety net once you're up and running, be it in the recovery , or apps like Titanium Backup. Getting there is mainly the intimidating part.

kbeezie said:
Mimicry 1.3.1 or EliteMod ICS (which I'm using now), in regards to ICS (4.0.*).
Far as guides. Some like the Cyanogenmod one can be 'easier' to read, but the XDA wiki has a lot more information.
Click to expand...
Click to collapse
So you would recommend EliteMod & Cyanogen guide for starters?
kbeezie said:
Since you're on gingerbread now you would go the Desire-Z Gingerbread route for unlocking/exploit before proceeding to root it. (but on the plus side sticking with a Desire-Z hboot will ensure your /system size is big enough to play with the Sense roms).
Click to expand...
Click to collapse
Uhhh... What?
kbeezie said:
With ICS some things to keep in mind is that the most common issues tend to be :
1) Camera isn't "fully" working, in some cases like on mimicry and elitemod (or other non-Sense ICS roms), you can take a picture, you can record a video, but usually only with the stock camera app and usually won't have features like 720p recording or special effects.
2) Graphical glitch with the text can happen on an app, although rarely occurs, is easily fixed by closing the app or restarting (tends to stay with one app when it happens).
Those are probably the two most common issue you'll see with just bout every ICS rom out there for DZ/G2.
Click to expand...
Click to collapse
I can deal with that. Really, camera for me is one of the most useless apps. So stock app will do just fine
kbeezie said:
To clarify, even if you use the CM Wiki to unlock/root you do not have to install Cyanogenmod 7.2 afterwards, you can pretty much install any compatible rom once you've gotten it unlocked and running with a custom recovery (though I prefer 4EXT over clockworkmod).
Click to expand...
Click to collapse
So, rooting won't delete everything from my phone, it will just be unlocked, so I could install some ROM apps that would do the rest of the work for me?
jumptoin said:
when you have root and you try new rom you will never want to stop of course there are some risks but I think that if you will have any kind of problem here on XDA is so many great people willing to help you ... my advice is to do it go step by step according to that guide and if you dont understand something just ask here on xda Best of luck....
Click to expand...
Click to collapse
Is changing ROM deleting all my apps, messages etc., and is it doing so every time I change it. I've spent quite a lot of time and care to set the whole thing up, so I don't thing I would swap the ROMs so easily as you say
demkantor said:
back in the g1 days a friend of mine rooted his, i was astonished what could be done to phones now adays. i quickly rooted my g1 and began learning a ton about everything mobile, just like many before and after me i was hooked. even if you never found a better rom than stock the learning process is well worth it. even if you dont use most of the new features available to you at least having them is worth it. and unless you dont research/read first, or are mostly stupid/have bad luck, you wont brick your phone. i have rooted 50~60 phones and tablets, maybe more and never had a hard brick, sure when i first started out there was some close calls but with a little common sense you will be fine, also know you are now part a large community eager to help
so follow the xda or cyanogen wiki and downgrade and root your phone, move on to the rom compilation (found in the developers thread here) try a few roms and see what you prefer. you will be happy you did
on and one last point; the best reason to root your phone right when you get it, if there ever is a problem it is much easier to fix a rooted phone with software/firmware problems then an unrooted one. the only drawback could be if you need to send it back for warranty... but how likely is that, and the phone you have now im sure has little/no warranty left
happy flashing!
follow kbeeize's advice on how to root and try a few roms out
Click to expand...
Click to collapse
THX! :good:
kbeezie said:
PS: One of the major advantages of having a custom recovery, is the ability to perform a backup of your currently installed rom. If you screw something up, you need only go back into recovery Wipe (factory-reset/cache/etc) and restore the backup to get right back to where you were. And you can have several backups too if you were trying out several different roms.
So basically the process of rooting/unlocking offers a safety net once you're up and running, be it in the recovery , or apps like Titanium Backup. Getting there is mainly the intimidating part.
Click to expand...
Click to collapse
So it's like making an image file of the whole windows OS with all the programs preinstalled and restoring it when things go bust?

StipeP said:
So you would recommend EliteMod & Cyanogen guide for starters?
Click to expand...
Click to collapse
EliteMod ICS isn't really for everyone, something like Andromadus Mimicry would be an easier start if you wanted ICS.
StipeP said:
Uhhh... What?
Click to expand...
Click to collapse
The T-Mobile G2 hboot (0.76.200) has a /system of ~400MB, /cache of ~200MB and /data of ~1.3GB, but 400MB is not big enough for a Sense rom. So if you were following the cyanogenmod wiki for exploiting/rooting, you would need the Desire-Z Engineering hboot (0.84.2000) which has a /system of ~550MB, /cache ~300MB, /data 1GB. Otherwise you would have to avoid Sense roms or roms that say you need a DesireZ hboot.
Since you said you had a Desire-Z you may not even run across that issue.
StipeP said:
I can deal with that. Really, camera for me is one of the most useless apps. So stock app will do just fine
Click to expand...
Click to collapse
Then that's all good then.
StipeP said:
So, rooting won't delete everything from my phone, it will just be unlocked, so I could install some ROM apps that would do the rest of the work for me?
Click to expand...
Click to collapse
Depends on how you root, and if your phone needs to be downgraded/exploited. Which most of the time it does (i.e.: to get ENG S-OFF), which will of course erase the existing data on the phone so backups is suggested.
StipeP said:
Is changing ROM deleting all my apps, messages etc., and is it doing so every time I change it. I've spent quite a lot of time and care to set the whole thing up, so I don't thing I would swap the ROMs so easily as you say
Click to expand...
Click to collapse
That's where root tools like Titanium Backup come in very handy. You can flash a band new rom, open up Titanium Backup, and then restore all your apps along with their settings/etc.
StipeP said:
So it's like making an image file of the whole windows OS with all the programs preinstalled and restoring it when things go bust?
Click to expand...
Click to collapse
Normally once you get an initial rom setup, you can do a backup in recovery. If things go bust, you just reboot into recovery, wipe/factory-reset and then restore from the backup which will put the phone at the exact same state as you backed it up.
But yea I guess it's kind of like taking a Ghost image of your hard drive, which is stored on the SD Card at /clockworkmod/backup

Dear StipeP,
Greetings!
I bought my Desire Z, my very first android mobile in April 2010 and since then I was thinking 'O my God! what the **** people are talking about rooting their mobile!!!'. It was not that I was not curious, it was the difficult looking procedure and always lingering fear of bricking my set . At that time, I was a toooooootal noob . Then HTC pushed gingerbread update. All was well before ICE rolled out and some other mobiles were getting it while desire z was no where in line. I decided I should give it a try but still I preferred some 'one click root' methods over the detailed one given at XDA (it seemed too intimidating). But every such method could not root a desire z on android 2.3.3 (they could have when I was on Froyo). Then I finally made my mind to take the bull by horn and started reading as much as possible about rooting the hard way. Finally, I went for the XDA-wiki and also stumbled upon a guy named Strawmetal's wonderful effort of putting all the necessary files and instructions at one place. One night, I sat after dinner just rooted it (though I remembered all possible Gods at some steps like matching the MD5 sums:fingers-crossed. I was so excited that I didn't sleep the whole night!
Now, question was which ROM to install ( I hated to be back on Froyo). I started fiddling with some gingerbread ROMs and then shifted to ICS ROMs. There are problems as mentioned by others. I would mention below some pros and cons (those matter to me) of these ROMs:
1. Gingerbread ROMs are generally quite stable. Some excellent examples are Virtuous Glite v2.01, EliteMod120316 (this is awesome!) etc. I found BeatMod Bliss Sense hybrid to be too heavy (it's a Sense 3.5 ROM).
2. Camera works fine with Gingerbread ROMs generally (It was good in EliteMod120316).
3. ICS ROMs are faster. Even browser there seems faster to.They give a lot of customization options (Rightnow, I'm on EliteMod 120728 and believe me, it would just enthrall you with its beauty and customization options).
4. For me, ability to read Hindi fonts is a bonus and ICS ROMs do this.
5. Regarding Camera on ICS ROMs, it is true that they are not good. But the Camera on EliteMod 120728 is working well. Only you cannot record 720p video:crying.
6. I'm yet to try some other good ROMs like CM9 unofficial so cannot say much about them.
7. One issue that I faced was that I could download from Play Store when using a gingerbread ROM but could not when using ICS ROMs. It was giving "error 403". Finally, resolved that today (of course, with help from others).
One thing that I should mention here is that after rooting and trying some ROMs, I felt frustrated and thought is there any way to go back to stock gingerbread rom without loosing root. Main issues was Camera (I use it a lot). But more I read and kept finding/trying new ROMs, more the desire to revert to gingerbread subsided. Finally, when I got EliteMod 120316, I was more than content. And now am using EliteMod 120728 (an ICS ROM).
Last but not least, I believe that the biggest advantage of rooting my desire z is not ability to run custom ROMs but the learning process and getting an opportunity to mingle with extra-ordinarily helpful XDA-guys.
Now, you have to take a decision about taking the plunge
Best of luck

Right, enough courage; time to get cracking.
I will go process by process, slowly following this: wiki.cyanogenmod.com/index.php?title=HTC_Vision
If I get stuck, all my hopes are on you guys.
Wish me luck

StipeP said:
Right, enough courage; time to get cracking.
I will go process by process, slowly following this: wiki.cyanogenmod.com/index.php?title=HTC_Vision
If I get stuck, all my hopes are on you guys.
Wish me luck
Click to expand...
Click to collapse
All the Best...
p.s.: take your time and better take notes of steps. It would help in bringing clarity. And make sure to copy your commands and outputs from ADB to a notepad. It would be of help if, God forbid, anything goes wrong. If you have already downloaded and setup the ADB, just try the msm_rotator command (adb shell cat /dev/msm_rotator). If you get following output, you are ready to go: /dev/msm_rotator: invalid length

Hi,
Another Android rooting NOOB, but experienced with Linux, including embedded (that's the day job )
Looking to root my HTC Desire Z, as is being discussed here.
From all the threads, it seems you have to downgrade to a very old stock ROM before starting. Several talk about being able to take a backup from Clockwork Recovery after you've rooted the phone in case things go wrong, but obviously by then the existing phone build will be gone.
What I'd really like to be able to do is to take a full backup of the stock Gingerbread setup I've currently got, so that if either (a) things go wrong or (b) I don't like the end result I can get back to where I am now.
None of the threads I've found so far (here, here, here and possibly others, I've been surfing around a lot the last couple of days!) talk about any way of doing this, some talk about using Titanium Backup or MyBackup Root to backup Apps, Call Data, SMS logs etc, but these presumably aren't a full OS backup.
Is there a relatively easy way of doing this from the fre3vo temporary root? Presumably 'dd' against the various /dev/block/mmcXXXX partitions will get most (all?) of the data? Are there sections that aren't available from Android device files as root?
One more (hopefully minor) thing - having worked down the start of this downgrade thread[URL], for now I've skipped the "Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard" section and tried the "Temp-Rooting to Backup" section (from my understanding of these two sections, I don't think anything from the section I skipped is relied upon in the backup section). I seem to find that the /system/bin/su file keeps getting corrupted or deleted. Is this HTC trying to stop me doing this, or is it one of the applications (SuperUser?) trying to protect the file and getting it wrong? In case it's making a difference, I also have Better Terminal Emulator Pro installed, which I'm using the "bash" from for some of the steps, as it has proper Linux auto-complete etc. which makes life easier.
I think I've managed to make a usable backup with MyBackup Root, but obviously can't easily test this without going further.
I'd really like to be as sure as possible that I can get back to where I am now before I start the downgrade to Froyo process...
Thanks in advance for any advice on this
Michael

I am worhtless.
Right now I am downgrading GB folowing CGmod guide wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread), and I am stuch at step 6. On the computer, open terminal and run the following commands:
Erm, what terminal????
btw, I extracted and copied the downloaded files into ADB install folder. That is the right one?

what terminal ? .... u just click start run and type in "cmd" ,,, or find command promt

says: adb is not recognized as an internal or external command, operable program or batch file.
I am sorry to bother you, but I would be very grateful

so you downloaded adb from the sdk package right? you need to either change directories in cmd or change the path in enviromental variables
easiest thing to do would be hold shift and right click in the folder adb and files are in and choose open command here. then the path is chosen
also make sure debugging is turned on (in phone)
Sent from my HTC Vision using xda premium

demkantor said:
so you downloaded adb from the sdk package right? you need to either change directories in cmd or change the path in enviromental variables
easiest thing to do would be hold shift and right click in the folder adb and files are in and choose open command here. then the path is chosen
Click to expand...
Click to collapse
did as you said but still the same problem: adb is not recognized as an internal or external command, operable program or batch file.
If only I could post screenshots here for you to see what exactly am I doing (wrong)

what does it say when you open the cmd?
C:/user......?
is that the folder adb.exe is in?
are you using windows 7, vista, xp? mac, linux?
Sent from my HTC Vision using xda premium

demkantor said:
what does it say when you open the cmd?
C:/user......?
is that the folder adb.exe is in?
are you using windows 7, vista, xp? mac, linux?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I have ADV Manager.exe and SDK Manager.exe
No adb.exe
This is what I have downloaded and installed developer.android.com/sdk/index.html
(Win7)

ok, you may need to open sdk and download adb from there, otherwise you can check if you did without knowing it. go to your harddrive (C) and see if there is an android folder or android sdk or something like that, look for I think platform tools in there and see if there is a program called adb
if you can't find this try search in computer
or just open the sdk manager and download the tools in the first chunk, specifically platform tools
Sent from my HTC Vision using xda premium

Here you go.

A few questions before rooting...

I am going to root my phone and have a few questions before I do. I am coming from a sensation and with the htc I only had 1 way to root so are any of the methods better or worse than others? I was planning on using to root injected stock rom method.
Secondly, I've read and still don't understand, could somebody explain the loss of imei to me? Htc doesn't have anything like that so I am confused about the backup of it?
Finally, could somebody suggest a good starting point for a rom and kernel combo? Unlike my htc I'm pretty happy with the stock rom sped and battery. I mainly want to tweak the looks of things a little, maybe a new battery icon and moving the clock position.

Best way to root is the video in my signature (use my files, too). It's easier and faster than the way you describe. I wish people would forget that stupid flash counter exists. It's not like we can't reset it.
Loss of IMEI very rarely happens when you flash. But, once you flash CM10, just run the terminal emulator that comes with it: su > reboot nvbackup. Now your IMEI is backed up, and you are protected against possible, but unlikely, loss. I've flashed every day for two months and never lost mine.
Rom: Why use ICS when you can use JB? IMO, the sole reason to use an ICS build is wifi calling. Use CM10. Use the stock CM kernel. CM doesn't have center clock (AOKP does), but IMO, CM is the better of the two. A lot of people like to flash custom kernels. They usually provide marginally better battery life, overclocking/undervolting, etc. I feel that none of these are necessary. There is an additional problem that the 3rd party kernels always lag behind CM's kernel merges, also. This typically results bootloops. So make sure the kernel you flash (if you do), is compatible with the newest CM build.

No the method does not matter, root is root. Read about them and use the one you are comfortable with.
Yes, HTC does have IMEI. All GSM phones do. It is basically the serial number your phone uses to connect to the network. All you have to do is follow the instructions in one of the threads to back it up.
For stock based ROMs on ICS, I like Wanamlite.

Aerowinder said:
Best way to root is the video in my signature (use my files, too). It's easier and faster than the way you describe. I wish people would forget that stupid flash counter exists. It's not like we can't reset it.
Loss of IMEI very rarely happens when you flash. But, once you flash CM10, just run the terminal emulator that comes with it: su > reboot nvbackup. Now your IMEI is backed up, and you are protected against possible, but unlikely, loss. I've flashed every day for two months and never lost mine.
Rom: Why use ICS when you can use JB? IMO, the sole reason to use an ICS build is wifi calling. Use CM10. Use the stock CM kernel. CM doesn't have center clock (AOKP does), but IMO, CM is the better of the two. A lot of people like to flash custom kernels. They usually provide marginally better battery life, overclocking/undervolting, etc. I feel that none of these are necessary. There is an additional problem that the 3rd party kernels always lag behind CM's kernel merges, also. This typically results bootloops. So make sure the kernel you flash (if you do), is compatible with the newest CM build.
Click to expand...
Click to collapse
Thanks for the reply, CM10 wasn't officially supported with the htc so it never really worked great, but it looks like the M version is pretty smooth and ironed out so I'll definitely try that. I guess a lot of the threads I've read were early ones from before the flash counter could be reset, I thought it was a bigger deal than it seems like it is. I'll try your sig's root method. Oh yeah, wifi calling doesn't work for me right now with the stock rom so losing it isn't a big deal at all.
joshnichols189 said:
No the method does not matter, root is root. Read about them and use the one you are comfortable with.
Yes, HTC does have IMEI. All GSM phones do. It is basically the serial number your phone uses to connect to the network. All you have to do is follow the instructions in one of the threads to back it up.
For stock based ROMs on ICS, I like Wanamlite.
Click to expand...
Click to collapse
I wasn't saying HTC doesn't have imei, I was saying in a year of having it and before with the G2 I never once read any threads about people "losing" it, so I wanted to know what makes the s3 different.

That was SOOOO much easier than the sensation was. The senny took me over an hour, I had to learn adb and had to check and recheck a ton of commands before entering each to make sure I didn't brick anything. This was fast and easy, but now I can't seem to get into twrp recovery? Every time I try vol up/home/power it boots into what I'm assuming is the standard stock recovery?

My signature has an explanation for that.

Thanks again, I don't understand why but I installed cwm touch and it worked and then used goo manager to install twrp again and now it works fine. I know there's a whole thread about twrp but what do you like and why?

I stopped using TWRP because the keyboard (at least at the time) didn't work properly. It would close for no reason, making me retype the file names. Took me 5-6 times once, for this file name: CM10-XXXX. 9 characters. Would just keep closing and resetting the characters I had already typed. I've heard the new version, 2.3, has some pretty bad bugs, but I haven't used it, so can't confirm. Developer is currently fixing said problems. I also find the slide-to-continue gimmick to be ridiculous. I will say, however, that flash-queuing is a good idea.
I won't even discuss CWM because we have CWM Touch. The layout is nonsensical. Everything seems to be in random order, no dividers to make things easier to read, no prompt on fix permissions. Other than that, it's great. It allows you to delete stock recovery, and it keeps root for you when you flash OTA files with it.
CWM Touch is what I use, and will continue to use until something better shows up.

One more question, is there a way to double check once I've done the su/nvbackup using terminal emulator, or should I just assume that if the phone rebooted after running that command that it was successful?

When you reboot with that command, you will see blue text at the top left corner of the screen, like when you are going into recovery. It says it's copying modemst1 and modemst2 to fsb and backup. Yes, the names are incorrect, but you get the idea.

[Q] Error 1: android.view.ViewRoot in touchpad activator?

Hey guys, I finally figured out how to install ics/jb roms, so i've been installing stuff nonstop lately. One problem I'm getting however, is when I use the touchpad activator app (in sonygenmod cm10), I get the error - Error 1: android.view.ViewRoot - and I'm not sure what to do. I remember it working before, when I used the Lupus Kernel jb v8 multiboot aware (Cause I didn't know to use the non-multibootaware), and in the process of trying to fix the patch that came with the mod, switched kernels multiple times, from Lupus Kernel jb v13 720, to 480, to turbo kernel, and back and forth. (My problem was with the patch, the patched rom was just kinda slow overall compared to the non-patched, the touchpad didn't work because of error 5, and several other smaller issues).
But now, after I said screw it, I don't need the patch, I go back to jbv8 multiboot 720, and now the touchpad gives this error. I've tried switching kernels again, and back, using the repair function in the multiboot version, and restarting the phone multiple times. Not sure what to do anymore.
Can anyone please give me any help?
Thanks in advance.
(Also, If anyone new what was wrong with the patch and could help me fix that, it would be nice too )

It seems like it's checking for root access and something is gumming up the works (and not just of the "oh, this phone isn't rooted" variety either). Do you have anything else on the phone that has root access, and if so, are there any problems with those apps?

Thunderbird8 said:
It seems like it's checking for root access and something is gumming up the works (and not just of the "oh, this phone isn't rooted" variety either). Do you have anything else on the phone that has root access, and if so, are there any problems with those apps?
Click to expand...
Click to collapse
Thanks for the response.
I tried installing BusyBox, and Root Checker.
Busybox worked like normal, was able to install busybox successfully. For some reason it said there was more than one version of busybox installed this time, witch I don't remember it saying last time.
Root Checker says it's rooted, but while checking it said the system was running very slow.
I'm not sure what other apps I should be checking with.

That's a missing file from the framework.jar. It goes with the touchpad fix.

Lordomn said:
That's a missing file from the framework.jar. It goes with the touchpad fix.
Click to expand...
Click to collapse
Oh, so what should I be doing? Should I redownload the rom file?

Well does the Rom have touchpad support already in it. If so I would suggest to do a fresh install.

Lordomn said:
Well does the Rom have touchpad support already in it. If so I would suggest to do a fresh install.
Click to expand...
Click to collapse
Yeah it does have touchpad support, and I've already tried a fresh install like 3 times.