Database Info

No Multi-Touch RC33 ROM

Here is a version of JF's RC33 1.41 without the multi-touch kernal included.
This one is JF's RC33 build modified with the PRE-MT kernal (1.31). It includes all the goodies that are standard with JF's builds and was recompiled from his source. This update does include the 1.41 recovery image.
ALL CREDIT GOES TO JESUS FREKE for providing us with the source for his modified ROM's
If you are interested or do not know what JF has added to the original images check this link
Just like JF's RC33 build this does not include the radio update which can be found here(MD5:CF8714D273FB0274574D9E3831E11FDD) this will need to be flashed separately in any order. To revert the radio you WILL NEED TO FLASH BACK TO RC29 THROUGH THE DREAMIMG.NBH file that can be found here
RC33 PRE-MT Kernal (MD5:97167BFDD7957F4D95C1538410003146)
http://drop.io/qyyqvmd#
*UPDATED* RC33 PRE-MT Kernal 1.42 Recovery image, No Amazon MP3, No Stock Email, no Term Emulator (which can be downloaded from the market, the author has been making changes so I didn't want to include it)
http://drop.io/689ghtm#
(MD5:F1B80E314926C7409DDCA6C0EE107626)
Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. I must recommend that you also do a wipe in recovery mode (alt+w) before applying the update as most of the esoteric issues that arise seem to be from not wiping. This will clear all your data/settings/apps, and you will have to re-register once it boots back up.
Again THANKS JESUS FREKE

Cool thanks for this, glad to see it worked out.
Do you think I would need to do a wipe going from mt rc33 to no-mt rc33?
Doesn't seem like such a large zip is necessary.
Does the MT really alter so many files?
Hopefully there will be a mini version that does the same thing

Only the Kernal is changed so if you want you can extract the boot.img and use the flash_image tool to re-image it over your current one. JF has a thread about the flash_image tool and how to use it at this link
The reason it's so large is because its a full ROM you can flash from RC29 etc. You could probably get away with not wiping but I have to recommend it since 90% of the issues people run into doing the updates seem to end up with a wipe so why not skip the issues. Its easy so re-sync contacts and reload apps.

Hahha thanks, so then the only diff is in the boot.img? Cool.
So I could just switch boot.img's and flash whenever I want to switch between normal and MT?
Ima try it righttt now

Any chance for a ADP1.1 No Multi-Touch ROM? Please?

why would any1 one want it without the multitouch?

Because of few problems with the MT version.

I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.

Thers is any "problem" with the multi-touch except that devs are not making apps for its kernal. Therefore some apps may act funny.
I personally don't use the MT at all so I don't want it throught the OS. And I don't know if its in my head but the pre-MT kernal seems to give me better battery life.

topdnbass said:
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Click to expand...
Click to collapse
Good to hear. Flashing the boot.img is really all that's needed but I wanted to make a full update just for the exercise etc since this is fairly new to me and fastboot might be more difficult for some.

Yeah It's not really a problem.
I figured it's good that both ways are on here now though.
Thanks again!

If youre already running jf rc33 do you need to do a wipe?

Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.

Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...

learningmore said:
If youre already running jf rc33 do you need to do a wipe?
Click to expand...
Click to collapse
you will probably be fine without a wipe but i recommend wiping when flashing

quietlurker said:
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Click to expand...
Click to collapse
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise

Edited:double post

justanothercrowd said:
you will probably be fine without a wipe but i recommend wiping when flashing
Click to expand...
Click to collapse
Ok i flashed without wiping everything is running good. Phone is much more responsive touch wise. Everything else still works great. Thanks to you and JF

Gadzks said:
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
Click to expand...
Click to collapse
There were request from a number of people for a non multi-touch version. If your not interested simply don't use it.
And as for the other comments....lol

justanothercrowd said:
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Click to expand...
Click to collapse
No worries. If you keep updating your branch in the future, you may want to be sure and change the ro.modversion in the build.prop file.

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/

Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work

thanks for sharing!

appreciate this very much!

thanks flipzmode....always a chance this could come in handy at some point

THANKS! was worried about having a with Google phone until now

thanks flipz

Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)

Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.

This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!

Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.

posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.

someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)

fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today

Thanks!
this saved my phone. I was about to throw it away.

USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.

nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")

Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

Please Sticky - HELP - How To Restore Sprint or CDMA Hero For Warranty Returns

I noticed that no one has set up a guide in this section on how to un-root and restore to factory for Warranty return/exchange purposes.
Below is a guide for the 1.29 Original:
http://theunlockr.com/2009/10/03/how-to-unroot-the-htc-hero/
Here is the Factory Restore for the 1.56 ROM:
http://forum.xda-developers.com/showthread.php?t=608434
Untested Theory:
Restore original Nandroid that you made after you first rooted your phone, that should put you at
a rooted 1.56
Then RUU to 1.56 and you should be factory.
Do not RUU from 2.1 to 1.56 because you are more likely to have issues.
If you can't deal with the minor bugs that are in the current DamageControl v2.0r2 then you might want to RUU restore, however I would suggest to wait it out because an offical 2.1 update might have to be rooted differently than what we have now. I prefer the Dev route.
I'm lucky that I didn't flash a custom ROM that wasn't a Sprint build, so my PRI didn't get messed up but if you did then go here, from dfbonney:
http://forum.xda-developers.com/showthread.php?t=654119
The posts below should also help understand how all this stuff has been gathered.

Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...

The Nandroid back up you make after your root will capture Root stuff, since it is done after the fact.. so it restoring the nandroid will not unroot (is that a word?)
Only way to unroot is with RUU, some people have an issue (50/50) after you flash the Flipz Radio update. Though it could be linked to running a 2.1 Rom and trying to RUU with 1.5.
I do belive they found a way to reflash each of the partition images individually and bring the phone back to life.

Let's do this!
Darkshneider said:
Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...
Click to expand...
Click to collapse
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.

I'm fairly certain my post can help those who've bricked their devices... it should be stickied or in the same post...
http://forum.xda-developers.com/showthread.php?t=654119

GURUGTS said:
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.
Click to expand...
Click to collapse
If you are asking what issues are there if you go from 2.1 back to 1.5? Well, the only one I ever had was with the market not letting you see Protected apps. This was a bigger pain than I thought it would be and the fix is a little tedious.
Some people have issues with restoring Nandroid's, but I believe that is usually because they are running low on SD Storage space for the Nandroid to expand as it is copied to the phone.
The PRI Stuff shouldn't be a HUGE issue, unless you want to use Sprint TV and Navigation and those Sprint Apps. Persinally I hate Sprint TV, picture is to fuzzy and the way they break the eppisodes into 5.5 minute clips gets on my nerves. Then they want you to pay for the good cartoons...bastards!
I think Google Navigation is just as good as Sprints...minus the Voice and the interface isn't as pretty...but Ill take it.

Will restoring with RUU also put the original dialer taskbar and anything else you changed back??

redlinethecar said:
Will restoring with RUU also put the original dialer taskbar and anything else you changed back??
Click to expand...
Click to collapse
Si. Oui. Ja. And Yes.

I noticed there is a guide on fixing the 110 error and a guide on how to unroot using your sdcard but not a general one covering the basics of unrooting with the RUU.
This should definitely be written up all in a post and included in the guide wiki.

i agree so users like me won't annoy people with thousands of questions when I need to get it done lol

redlinethecar said:
i agree so users like me won't annoy people with thousands of questions when I need to get it done lol
Click to expand...
Click to collapse
lol, noobs asking questions that are readily availble will never stop, at least the wikis give us a single location to direct them to...
Welcome to XDA redline!!
Please ask away, search first but if you can't find something we are here to help!

[UPDATE, INFO AND LINKS]*PLEASE READ* Concerns about Amon_Ra and Clockworkmod

UPDATE WITH INFORMATION AND LINKS ON HOW TO AVOID PROBLEMS
Through the posts and information that has been brought to my attention your Hboot is not really of significance, it is just your partitions. You can update your Hboot and maintain older partitions.
I bet you're wondering how to discover if you have these partitions. I owe the credit to this command to XhausX. "A petty reliable way to tell is by your /proc/mtd table. If 'cat /proc/mtd' shows an erase size of 20000 you have the old set up. If it shows 40000 you have the new one".
Once you know whether you have the old or new your options are as follows
OLD Partition: Flash Clockwork mod 2.5 or use the unmodified version of Amon_ra found here http://forum.xda-developers.com/showthread.php?t=705026&highlight=Amon+Recovery+Custom . Also be aware that you can flash the Amon_ra found in clockwork mod because it is unmodified.
NEW Partition: Flash the updated clockwork recovery mod (3.0) or use a modified version of the recovery found in Zikronix thread here http://forum.xda-developers.com/showthread.php?t=829045
Although this is a temporary solution I urge everybody to reach out to developers and offer assistance or bring to their attention the danger of the multiple partitions. I'm unaware if you can put a check into software that would install recoveries but I'm sure it wouldn't be too hard if xhausx script can already distinguish them. Hopefully you all head my warnings. HAPPY ROOTING and GOOD LUCK!
ORIGINAL QUESTION READ ABOVE FOR INSTRUCTIONS
This is going to be in many ways a general warning that will bring something I realized today to the attention of everybody and simultaneously will bring a developer forward to answer the questions I'm about to present. I have a similair thread in the Q & A forums but I wanted to get more coverage for this so that a ton of people don't kill their phones or lose their RSA keys accidentally (have lost mine and it sucks if you live in a 4g area!).
Amon_Ra is a fantastic recovery and has been at 1.8 for a while. In the Hboot 2.2 and 2.10 thread the author brings forth the fact that the partitions for these Hboots has changed and that the modified Amon_ra is made to compensate for this. It is labeled as Amon_ra but it is not truly 1.8 but instead a modified version.
What i take this to mean is that the partitions, where certain information is stored on our phone, was changed for these Hboots and thus the recovery had to be altered to backup and flash information to these new locations. Clockwork mod has now been updated to 3.0 and it fixes this. I'm assuming it scans your phone to see which Hboot you have and acts accordingly.
Now, for the problem
Clockwork mod has an option to flash Amon_ra. However, if you have Hboot 2.2 or 2.10 and this flashes an older Amon_ra or an unmodified for these new hboots(it is much easier to flash recoveries this way and I know i'm not the only one who does it) then if you attempt to nandroid or flash a rom you could very well bork it.
I have searched and found no documentation CONTRARY to this. If there is, point me in that direction and I'll be on my way to check it out and remove this post but I want to make sure nobody accidentally ruins their phone while changing recoveries.
My suggestion to this problem, and if it is in fact a problem I'll be attempting to get into contact with the developers and see if they have a solution. I think it's just a bad idea to have varying versions of Amon_ra floating around that are labeled the same without actually knowing which is for which Hboot.
Thanks for reading and if you have any input please add, I just want to avoid people messing up their phones. I have been through 3 refubs and gone through the rooting process various times and I just want to make sure some noobies don't lose a ton of money in tough economic times because of a simple oversight like this. If the need be we need to put warning out there about this.

Me and TrevE are the ones that discovered this whole thing.
We msg'd both amon_ra and koush and amon quickly threw together a fix. And I tried cw's new recovery on an old and new evo on the new evo it seemd to work but on the old evo it would only back up the boot.img so im all for getting this sorted out...and it is a real problem
here is the work me and treve did
http://forum.xda-developers.com/showthread.php?t=843342
The issue is that the "modified one" from the thread reports version 1.8, the version you can "officially" download is 1.8 but i assure you they are VERY different.
The poster below states he uses 1.8 on his 2.02 evo but the question is what version...of 1.8. Yes it has been reported that some of the older evo's that managed to get the 2.xx hboots can use the "official" amon_ra and it works....and it might...however the newer evos some of which are 003 and 004 that have hboot 2.xx need to use the "modified" one
this is where the issue lies

Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA

NVM I answered my own issue.

mroneeyedboh said:
Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA
Click to expand...
Click to collapse
Do you even read what he wrote???
davenukem said:
This is going to be in many ways a general warning that will bring something I realized today to the attention of everybody and simultaneously will bring a developer forward to answer the questions I'm about to present. I have a similair thread in the Q & A forums but I wanted to get more coverage for this so that a ton of people don't kill their phones or lose their RSA keys accidentally (have lost mine and it sucks if you live in a 4g area!).
Amon_Ra is a fantastic recovery and has been at 1.8 for a while. In the Hboot 2.2 and 2.10 thread the author brings forth the fact that the partitions for these Hboots has changed and that the modified Amon_ra is made to compensate for this. It is labeled as Amon_ra but it is not truly 1.8 but instead a modified version.
Click to expand...
Click to collapse

the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
mroneeyedboh said:
Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA
Click to expand...
Click to collapse

I think what he is trying to say is that there are 2 different versions of "amon ra 1.8" which are both different.
One version fixes the partitions on the newer hboot, and the other one does not.
So, what he is saying is rename the newer amon ra to 1.8.1 or something so that people know they are flashing the right one.
BTW... autoroot has it built it.

davenukem said:
the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
Click to expand...
Click to collapse
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
kthejoker20 said:
I think what he is trying to say is that there are 2 different versions of "amon ra 1.8" which are both different.
One version fixes the partitions on the newer hboot, and the other one does not.
So, what he is saying is rename the newer amon ra to 1.8.1 or something so that people know they are flashing the right one.
BTW... autoroot has it built it.
Click to expand...
Click to collapse
Ok that makes alot more sense.

See, more testing needs to be done. If what you say is true then perhaps it's only the 2.10 hboot with these new partitions? I think the Amon_ra developer needs to communicate with Koush and discover HOW koush figured out how to distinguish between which phone had which partitions. Realistically though, this is a horrible move by HTC, it's bad enough there are so many hardware revisions floating around.
lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Ok that makes alot more sense.
Click to expand...
Click to collapse

davenukem said:
See, more testing needs to be done. If what you say is true then perhaps it's only the 2.10 hboot with these new partitions? I think the Amon_ra developer needs to communicate with Koush and discover HOW koush figured out how to distinguish between which phone had which partitions. Realistically though, this is a horrible move by HTC, it's bad enough there are so many hardware revisions floating around.
Click to expand...
Click to collapse
In HTC's eyes its working for them... messing up the dev community from rooting... but that my friend is only short lived.

lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Click to expand...
Click to collapse
but what version of 1.8 see my post i updated above

davenukem said:
the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
Click to expand...
Click to collapse
Oh I was confused at the time I posted. I thought you meant something other than Amon RA 1.8. When I rooted my phone, I was told in the guide to use AmonRA 1.8 because the lesser version was no good. Because like you said the partitions are different in 2.02 and 2.10. Which in turn (again like you said ) can render the 4g obsolete and unresolvable and the inability to possibly flash roms.

Its gonna suck when us older hardware versions need to get phones repaired. Damn u HTC lol
Sent from my Evo CM6

lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Click to expand...
Click to collapse
It is the partition setup, or to be more specific MTD, that matters. The hboot version was thought to be the culprit at first but now we know it is doesn't matter.
So the hboot does not matter when it comes to this. It is all your partition setup.
Sent from my PC36100 using XDA App

Then I must be using the new amon ra version since I rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=829045

So is there any downside to upgrading to the latest 3.0.0.2 ClockworkMod Recovery on an older HBOOT version? Will I have issues restoring from older nandroid backups?

martonikaj said:
So is there any downside to upgrading to the latest 3.0.0.2 ClockworkMod Recovery on an older HBOOT version? Will I have issues restoring from older nandroid backups?
Click to expand...
Click to collapse
yes because depending on all sorts of variables. in fact i couldnt get cw the new version to work with old hardware and it was acting goofy in new hardware.
the only reason we require the use of the "modified" recovery like haus said is because the partition structure changed. and really has nothing to do with the hboot.

zikronix said:
yes because depending on all sorts of variables. in fact i couldnt get cw the new version to work with old hardware and it was acting goofy in new hardware.
the only reason we require the use of the "modified" recovery like haus said is because the partition structure changed. and really has nothing to do with the hboot.
Click to expand...
Click to collapse
So i should stick with 2.5.1.2 for now? lol
I flashed 3.0.0.0 when it came out, and it led to all kinds of crazy issues. It worked just fine in the recovery menu etc. but i ended up having some bootloops and such.
Also, ROmManager is prompting that 3.0.0.2 of CWM is available. thoughts?

How about providing links to the proper version of Amon_Ra's recovery in the OP? Granted, it'd be nice if he changed the version number, but having the right one somewhere obvious would be nice in the meantime.

Thought I would mention that I flashed clockwork from rom manager. Works fine on my 2.2. Just did a back and some flashing. All goof
Sent from my PC36100 using XDA App

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.​HTC Evo 2.3.3 Gingerbread Root Collaboration​
The Lowdown on Everything​
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission​
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse

Possible Rooting Ideas​

What Works What Doesn't​
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse

There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end

Am I missing something?
Sent from my PC36100 using XDA Premium App

lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>

<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>

What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.

ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community

I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...

This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671

skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?

I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App

github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?

fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.

Who rated the thread bad?

bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved

bubby323 said:
What Works What Doesn't​
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3

some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.

Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!