Database Info

Rooting the RUU 2.1 Sprint Leak

I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127

I guess you missed the sticky at the top.
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides

Thanks so much I appreciate it

amdme127 said:
I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127
Click to expand...
Click to collapse
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?

regaw_leinad said:
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?
Click to expand...
Click to collapse
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
becuase when you used the ruu, it overwrote the custom recovery image with the stock test 2.1 recovery image.
You'll have to load the flash_image file on the phone and chmod it. Then flash the custom recovery again. I think I saw a guide somewhere in here.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
If you run the .exe it rewrites the recovery.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
Already answered

So is it true that you can gain root access through ADB!

danknee said:
If you run the .exe it rewrites the recovery.
Click to expand...
Click to collapse
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.

Roman G said:
So is it true that you can gain root access through ADB!
Click to expand...
Click to collapse
Yeah, but, you don't have busybox installed, so you can't do really anything in adb shell.

regaw_leinad said:
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.
Click to expand...
Click to collapse
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image

danknee said:
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?

regaw_leinad said:
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?
Click to expand...
Click to collapse
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well....without the RUU...lol.
The bootloader is modified, so you can't just RUU the old fashioned way.
smw6180 said:
If it doesn't work, try this post: http://forum.xda-developers.com/showpost.php?p=6013606
It's basically going to stock without using the RUU.
Click to expand...
Click to collapse

danknee said:
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well.
Click to expand...
Click to collapse
cool thanks

http://forum.xda-developers.com/showthread.php?p=6142928#post6142928
I wrote up a tutorial on how to root any 1.5 based Hero using the Sprint 2.1 leaked test RUU. This might help.

Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help

amdme127 said:
Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help
Click to expand...
Click to collapse
he posted how to fix that right above you...
http://forum.xda-developers.com/showpost.php?p=6151388&postcount=12

Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again

amdme127 said:
Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again
Click to expand...
Click to collapse
No problem

trouble flashing newBoot.img....

ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks

gmelchert said:
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
....What exactly are you trying to flash??

pseudoremora said:
....What exactly are you trying to flash??
Click to expand...
Click to collapse
the "newBoot.img" for DarchDroid 2.1 jit

gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
You are talking about this thread, right? And if so, you are downloading the STABLE ROM, correct?

yes and no, I'm trying the AOSP jit enabled one

gmelchert said:
yes and no, I'm trying the AOSP jit enabled one
Click to expand...
Click to collapse
Let me check something.

gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.

gmelchert said:
ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
Nothing I see is incorrect. Try putting a delay of about 10 seconds between erasing the mtd2 device and flashing the ROM. This is especially true if you are flashing from recovery.

tkirton said:
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.
Click to expand...
Click to collapse
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.

it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think

pseudoremora said:
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.
Click to expand...
Click to collapse
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.

gmelchert said:
it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think
Click to expand...
Click to collapse
tkirton said:
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.
Click to expand...
Click to collapse
Really? Okay, cause I downloaded the AOSP file and it's definitely a custom ROM... but I'm glad it's sorted out now.

still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh

gmelchert said:
still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh
Click to expand...
Click to collapse
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.

tkirton said:
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.
Click to expand...
Click to collapse
I just tried that and all I got was a repeat command line
"# flash_image boot /sdcard/newBoot.img
flash_image boot /sdcard/newBoot.img
#

http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!

Roman G said:
http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!
Click to expand...
Click to collapse
I used that post in the first place. Basically what I'm trying to do is get AOSP DarchDroid to actually boot so I want to try one of the kernels darch posted. I have not yet been able to get them to flash (what is the correct outcome in cmd when I type "flash_image boot /sdcard/newBoot.img"?) I know you were on of the people who got the jit working, what did you do to get it to work? the rom I mean...

[Q] is there a way to unroot and lock the bootloader again ?

is there a way to unroot and lock the bootloader again ?

quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.

but as of now no way to flash the stock recovery

slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.

distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery

slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !

distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?

quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.

slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.

distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery

slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).

distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse

quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod

got it all working now thanks to you and distortedloop .
thanks a lot guys.

ClockworkMod Recovery 3.0.0.5

This is the latest ClockworkMod Recovery!! Instructions to install below
Downloads At bottom of page.
I am not responsible if you brick or damage your phone... blah blah blah... NANDROID FIRST cuz u never know wut might happen XD.
Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
Download ClockworkMod Recovery 3.0.0.5
Copy the recovery.img to root of the SD card.
Boot the phone into recovery.
Open command prompt.
Change directory to the AndroidSDK directory & type the following commands:
adb shell
mount sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Method II
Flash recovery using: RomManager
Download ClockworkMod Recovery 3.0.0.5
On the SD card, go to: /clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries.
Rename the old image there named recovery-clockwork-2.5.0.7-heroc.img to recovery-clockwork-2.5.0.7-xxx.img.
Move recovery-clockwork-3.0.0.5-heroc.img to that folder and rename it to recovery-clockwork-2.5.0.7-heroc.img.
Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
Method III
Method III
Flash recovery using: H-Boot/S-Off Only
Download HERCIMG.zip
md5: 6dcd265a51cc7090824d7f9f889b370b
Move HERCIMG.zip to root of the SD card.
Power off the phone.
Hold the Volume Down and Power buttons until the phone boots into the bootloader.
Wait for bootloader to scan and find HERCIMG.zip.
Press action to install.
The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
http://www.mediafire.com/?2gwhom1m06tbboy - ClockworkMod Recovery 3.0.0.5
http://www.mediafire.com/?u86sj1w22db8kbt - HERCIMG.zip
thanks to romrepo.info/wiki

It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.

deke2010 said:
It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.
Click to expand...
Click to collapse
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™

laie1472 said:
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Im using my dads computer and i cant install anything on it soo..

deke2010 said:
Im using my dads computer and i cant install anything on it soo..
Click to expand...
Click to collapse
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™

laie1472 said:
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
i already have it on my phone but i cant get screenshots without the emulator on the pc which i cant install cuz its my dads computer.

When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.

METHOD1911 said:
When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.
Click to expand...
Click to collapse
Glad you got it working. To answer the question about .txt on the phone, others have reported that using a different browser works for downloading the .img file correctly. I think they used Dolphin browser from the market.

I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?

Try the ADB method?

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
I will try that now. Quotes necessary around the filename?

No, do not use quotes.

kynov said:
I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?
Click to expand...
Click to collapse
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO

il Duce said:
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO
Click to expand...
Click to collapse
AOSP didn't make CWM.....

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
EDIT: Managed to get 2.5.0.1 back on there. Gonna leave it as-is.

What's the clock speed on this?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
ok Koush did, I know, but the version we are using is tweaked by him.
would you correct me if I said he made his rom, because technincally google MADE it, but he did in fact tweak it,build it,compile it, for the hero.
@aiwetir - 768

Method III worked fine for me. Just follow instructions carefully, and don't forget to do "su" first (lets terminal use root privileges).
I'm curious why RomManager doesn't update the version number. I know I'm using 3.0.0.5 because of the new orange text, but RomManager still shows 2.5.0.1
Anyone?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
Pretty sure he tweaked cwm3.0.0.5 to make it work for our phones ... I'm sure duce didn't mean he made it made it just wrong wordage lol come on Impaler. You know aosp be a tweaker to make our phones the **** lol
Sent from my HTC Hero CDMA using XDA App

il Duce said:
ok Koush did, I know, but the version we are using is tweaked by him.
@aiwetir - 768
Click to expand...
Click to collapse
Beat me to it haha ... Impaler just hating caus3 his epic isn't as awesome as our hero's hahaha jk
Sent from my HTC Hero CDMA using XDA App

Everything Updated in one Place with CM 6.2 and CWM recovery

Okay so I went and got the latest working updates from everything and put it in a convenient package for you.
One Click Root Apk: Version 0.1.0
Radio: 2.42.02.10.29
HBoot: 1.47.0000
Kernel: 2.6.29.6 (up to 768 Mhz and its stable )
ClockworkMod Recovery: 3.0.0.5
CynanogenMod: 6.2 - No longer needed
S-OFF
Step by Step Instructions below.
The instructions are only for people running CynanogenMod and ClockworkMod recovery.
Unzip everything.zip to your sdcard
Also put Kernel.zip on your sdcard
You HAVE to install these in a specific order otherwise some things won't work.
Flash CynanogenMod 6.2 if you havent already. It has the latest kernel in it already which goes up to 768 Mhz. http://forum.xda-developers.com/showthread.php?t=731659 here's the new link
Install Rom Manager and flash ClockworkMod recovery 2.5.0.1. Now you MUST backup with it.
Run the ruu included in the zip. this will give you the latest HBoot.
Boot into hboot mode (volume down and power button) and look to make sure it installed HBoot 1.4.7.0000
reboot
install heroroot010.apk
run heroroot.apk and it will give you darchstar's recovery and put a file on your sdcard called rootme.zip
reboot
reboot into Darchstar's recovery
flash rootme.zip
reboot
you now should have root and should have the super user app. if you dont then something went wrong and you should try again.
if you have root, download rom manager and flash ClockworkMod 2.5.0.1
restore your backup with ClockworkMod recovery
reboot
reboot to recovery
flash radio.zip
it will tell you to reboot after it is done.
this boot will take a while so be patient
reboot again
reboot into recovery
wipe dalvik
flash kernel.zip
reboot
reboot recovery
warning: there is no hboot s-on for the cdma hero YET. they are working on it though.
flash S_OFF.zip
reboot
you now have hboot s-off
reboot into recovery
plug phone into computer
run the following code in adb:
adb shell
mount sdcard
flash_image recovery /sdcard/CWMR3.0.0.5.img
exit
adb reboot recovery
reboot
done!
Update: Heres the link to Everything.zip and Kernel.zip: http://www.mediafire.com/?tj5a734t7n6gi
Thanks to jcase for the root apk
Thanks to theimpaler747 for the new radio
Thanks to Whosdaman for the ruu with the new hboot in it
Thanks to Decad3nce the updated kernel
Thanks to regaw_leinad for the S-Off
Thanks to aosp and ClockworkMod for the recovery

Thanks for all the info Deke -- is there some sort of package that is included with this? I don't see anything...

AboveUnrefined said:
Thanks for all the info Deke -- is there some sort of package that is included with this? I don't see anything...
Click to expand...
Click to collapse
yeah sorry. im having troubles uploading it. it will be on here as soon as posible
Edit: Everything.zip is now uploaded! enjoy!

CynanogenMod: 6.2 ?
When did this happen ?

PTown599 said:
CynanogenMod: 6.2 ?
When did this happen ?
Click to expand...
Click to collapse
bout a week ago

6.2 has been around since mid to late December... if not earlier.
P.S. You may wish to give people credit where credit is due.

You're a hero with a hero -- saved me boat loads of time!

I don't see anything named cyanogenmod 6.2 in the zip or the provided link...

Squiggy45 said:
I don't see anything named cyanogenmod 6.2 in the zip or the provided link...
Click to expand...
Click to collapse
Isn't there a lot of places that can be found?

A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...

Squiggy45 said:
A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...
Click to expand...
Click to collapse
Here's at least one CM 6.2 build
http://forum.xda-developers.com/showthread.php?t=731659

You really need to credit the people who made this stuff in your op unless you want to get infracted or banned. Also this is a pointless thread as these things can be easily found by searching. And you haven't developed anything here so this should be in another forum, not development. Seems like you just keep making threads in development of other peoples work for no reason. Way to go.
sent from my hero, which no longer sucks ass

Squiggy45 said:
A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...
Click to expand...
Click to collapse
i didnt put it in everything.zip cuz i didnt have time. I put the wrong link.. sorry. i just updated the link so try it now.

il Duce said:
You really need to credit the people who made this stuff in your op unless you want to get infracted or banned. Also this is a pointless thread as these things can be easily found by searching. And you haven't developed anything here so this should be in another forum, not development. Seems like you just keep making threads in development of other peoples work for no reason. Way to go.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Im putting on the credits now and this is just a package that has everything in it so people DONT have to search for it so it saves them a lot of time plus it has step by step instructions 4 people who dont know how.. and there is no where else to put it otherwise i would.

Q & A would be a tad more appropriate since nothing is being developed here.

kk. will do next time. and if u guys want anymore of these packages pm me da details. itll be in q and a from now on

Since when is there a CM 6.2? The last stable release is 6.1. Anything else is unstably/nightly/unofficial
http://forum.cyanogenmod.com/files/category/17-htc-hero-cdma/

its been out for a while dude. just look at the link i posted. completely stable. idk why they havnt updated they're site yet. http://forum.xda-developers.com/showthread.php?t=731659

That's not 6.2, that's some custom build. Don't know why it's called 6.2, as there never was a 6.2, they went straight into 7

EGOvoruhk said:
That's not 6.2, that's some custom build. Don't know why it's called 6.2, as there never was a 6.2, they went straight into 7
Click to expand...
Click to collapse
Some phones did get pushed to 6.2, the jaybob build was synced with basically the last of the 6.x Hero source.