Database Users

Clockwork 3.0.0

Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk

fliint said:
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
http://mrcellphoneunlocker.com/recovery.img

Download it from the RomManager.

Thanks
Sent from my HTC Vision using Tapatalk

its not on the rom manager, (yet)

gnunixguy said:
Download it from the RomManager.
Click to expand...
Click to collapse
Rom manager doesn't list 3.0, only 2.5.1.4 as being the latest

ROMmanager is 3.0.0.2 the recovery has not changed since november 10.
There's nothing wrong with cwm. Maybe one will come with GB.
vision

Does this recovery fix the "off issue" what's new in it?

PlatinumMOTO said:
Does this recovery fix the "off issue" what's new in it?
Click to expand...
Click to collapse
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.3.
Sent from my HTC Desire Z using XDA App

AllWin said:
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.4.
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
For latest mine says 2.5.1.3

omarsalmin said:
For latest mine says 2.5.1.3
Click to expand...
Click to collapse
Sorry, that was a typo. Fixed.

i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.

androidcues said:
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
Click to expand...
Click to collapse
let us know the results? did your g2 survive?

can anyone let us know if any problems have been discovered with this so far?

warsng said:
let us know the results? did your g2 survive?
Click to expand...
Click to collapse
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)

Is it even worth it to upgrade at this point in time? I'm a bit worried as it seems to be working pretty damn good with what I'm doing now. No partitions on my SD card because I don't care to put apps on it (it's not the fastest class card anyway).

androidcues said:
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Click to expand...
Click to collapse
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?

warsng said:
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
Click to expand...
Click to collapse
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision

androidcues said:
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
Click to expand...
Click to collapse
appreciate the info , thanks.

Erase Recovery option
Call me naïve, but if people are making full-blown builds with an image recovery and everything from the CM gingerbread source (which includes the Clockwork Mod recovery 3.0.0 image if I'm reading the source properly), could you just go into ROM Manager, go into Settings, and check the "Erase Recovery" option to allow it to erase the recovery between flashes?
I would test this myself, but I need to go home and make myself fresh builds of CM7 and CM6.2 to try swapping/flashing back and forth between. I can report back once I get around to it later this afternoon.
If I understand that option correctly, applying a full flash of these alpha builds of CM7 should write the new recovery image (v3.0.0.0), and if you need to switch back to CM6, you should be able to just reflash a full build of 6.1.1/6.2 back and it will restore the older recovery image (v2.5.1.8 according to the latest froyo version).
EDIT: Negate that thought. Not sure how you would go about forcing the recovery image flash while in recovery. I got to research this a little more...

why stuck on modaco??

hello all, i recently installed clockwork3.0 to try out the cm7 rom and did so. afer that i wanted to go back to cm6 but decided to try out a custom baked modaco in between. I went no problems to the modaco vision rom and then tried to go back to the cm6 and thats where i ran into the problem. It seems as if though all i can flash and boot now is the modaco vision and desire roms. i try enomther and cm and after the flash and reboot im always stuck at the HTC boot screen which i know shouldnt be there and cant format boot in cwork3.0 without failure error. Even a nandroid back to cm6 wont work. Im assuming this has something to do with the modaco rom writing some apps to /system during install. If anyone can point out my error or explain why this could happen it would be greatly appreciated. Thanke, veritasaequita

You need to flash back to the old ClockworkMod Recovery using fastboot? You have done that haven't you? CWM Recovery 3 is only for 2.3 roms atm afaik.

Cool, thanks for the input bro. Yes I sure have. I did see in the dev forum a thread titled install cw3.0 easily from phone. Is it possible to go back to the old cw by way of using the phone also? Once again thanks for your help
Sent from my HTC Vision using XDA App

oh yeah, indeed you have hit upon something. Try installing ROM manager via the Market,... then use that to re-install the old recovery.
But if that fails,... then yes, you SHOULD be able to use a Terminal Emulator to flash without using fastboot commands.

[q] omg need help. Mytouch 4g stuck on mytouch 4g screen.

Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only

Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?

If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App

3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.

thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.

thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.

Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App

danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.

What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App

danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.

The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App

danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.

i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.

hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?

OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.

I used the .zip file to restore my mytouch, but now it wont go into Hboot.

I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you

Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas

[Recovery] ClockworkMod Recovery flashable from bootloader

Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. The answer...yes.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want to use or have access to ADB.
In that case you would:
remove your sdcard from your phone
place the zip on the root of the sdcard (using an adapter or another phone) and make sure it is named the appropriate "PG05IMG.zip"
place the sdcard back in your phone
boot to bootloader as if you're installing a radio (power+VolDown from powerOff). It will then find the zip, recognize it as recovery and ask if you want to install (if it does not prompt then select "Bootloader" from hboot).
Follow the instructions and after it finishes flashing pull your battery to power off (since the ROM will be bootlooping and hboot will constantly find the zip)
Now remove the sdcard and delete the zip (via adapter or other phone) like you did to put it on the sdcard, then place the card back in the phone.
Boot back to bootloader (Pwr+VolDwn)
Select "Recovery" and use CWR to wipe data/cache, flash a new rom, restore, or whatever you wish.
Obviously not the only reason since some people prefer this method over RM but clearly in that case the whole sdcard switching mess is unnecessary. Just do steps 2 and 4 and reboot when prompted like you do with radios.
Remember to remove any PGO5IMG.zip from your sdcard when done.
If this isn't useful to you, so be it. I just figured I'd throw this out there. Maybe it will help someone.
I will keep this updated as new versions come out for those few that find it useful.
**Credit to Koush and jcase**
All I did was decide to throw them in a zip that was useful in some situations for panicking users.
Updates
8/9/2011: Added latest official stable for mecha (4.0.1.5) released 8/8/2011.
8/30/2011: Added latest official stable for mecha (5.0.0.1) released less than an hour ago. Added mirror.
8/31/2011: Added latest official stable for mecha (5.0.0.8)
9/1/2011: Added latest official stable for mecha (5.0.1.0)
9/5/2011: Added latest official stable for mecha (5.0.2.1)
2/1/2012: Added touch based CWR released this morning (5.8.0.2) *NOTE: Have not personally tested.
If any of these cause problems please let me know immediately.
Latest Official=5.0.2.1
jcase modded=4.0.0.5
Mirror: http://www.mediafire.com/?9zt68cegl6qa3
MD5:
66750618ecfba292c0b0e42c50c2c3ee - (CWR3.1.0.2)PG05IMG.zip
1f390edad7e87310fe80b3264a57b14b - (CWR4.0.0.5)PG05IMG.zip
6aac529cedcd2b22afac7391a4cb7efb - (CWR4.0.1.5)PG05IMG.zip
bf25b2601441b9fffb7d68954c4ff3b5 - (CWR5.0.0.1)PG05IMG.zip
dfe1ddf0c574977ee2c1828735ef2dc0 - (CWR5.0.0.8)PG05IMG.zip
8474c8d607177b0144eec624dea687b7 - (CWR5.0.1.0)PG05IMG.zip
c4c1d9c5e553fd7b151352551b931369 - (CWR5.0.2.1)PG05IMG.zip
58557e1e355c795d748c2e6c66251f0a - (CWR5.8.0.2)PG05IMG.zip

Absolute_Zero said:
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. I didn't see the need at the time but I took a few minutes to throw together a test. Let me know if it works for you or not.
I tested flashing the stock recovery from the custom firmware, confirmed it had replaced CWR, then used this to install CWR back.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want or have access to ADB. In that case you would just pull your sdcard, place this on the root (via adapter or someone else's phone) named the appropriate "PG05IMG.zip", place back in your phone, and boot to bootloader as if you're installing a radio. It should then find it, recognize it as recovery and ask if you want to install.
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
If this doesn't work and doesn't have any use for anyone, so be it. I just figured I'd throw this out there.
BTW, this is ClockworkMod Recovery 3.1.0.2 (latest for mecha at time of posting).
Note1: Only tested on Engr hboot with S-off obviously
Note2: I don't have access to an MD5 generator where I am so people that test this should have a booting ROM with RomManager or at least know how to manually reflash ClockworkMod Recovery if it doesn't work.
Click to expand...
Click to collapse
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App

good post will definitely come in hand props

DroidTh3ory said:
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?

Sword.Zero said:
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Click to expand...
Click to collapse
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.

Absolute_Zero said:
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Click to expand...
Click to collapse
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment (CWR4.0.0.5)PG05IMG.zip

DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
In your case it would probably be easier to just use flash_image from terminal on the phone (i.e. flash_image recovery /sdcard/recovery.img) assuming your current rom has it (if not just search and download it) or you have RM installed. The main case I saw this being useful was if you didn't have or want to use ADB and your ROM was unusable (e.g. bootlooping). I may add Jcase's modded recovery to the OP as well since it seems useful/wanted by some.

I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.

Mustang302LX said:
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Click to expand...
Click to collapse
I have been using for a good month now on 3 different bolts... Never had a issue??

Absolute_Zero said:
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
Click to expand...
Click to collapse
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
it is that easy,i have done this,and i have also removed the hboot and stock recovery from PG05IMG RUUs so that i could flash without destroying recovery and my eng bootloader.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
did you make up your own android info file? or what did you take it from?
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well

DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
thanks for the download. has he put up any posts on it? or is it still being developed?

scotty1223 said:
thanks for the download. has he put up any posts on it? or is it still being developed?
Click to expand...
Click to collapse
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App

cool,thanx... ill go over there and look for it.
edot:
here if anyone else wants it

Thanks for this. Just flashed 4.0.0.5 after being afraid/too lazy to do it through ADB (which is also a pain because I have it on my Windows partition whereas I regularly use Mac).

scotty1223 said:
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
Click to expand...
Click to collapse
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
Click to expand...
Click to collapse
Exactly my reasoning. I've seen to many people unaware of what to do in that situation
did you make up your own android info file? or what did you take it from?
Click to expand...
Click to collapse
I checked a few from the firmware and radios and they all looked the same so I just pulled one of those.
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
Click to expand...
Click to collapse
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.

DroidTh3ory said:
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey get out of here, you've got candy to make! I keeeed I keeeed! Great work on the recovery guys, VERY useful!
Sent from my ADR6400L using XDA Premium App

DroidTh3ory said:
I have been using for a good month now on 3 different bolts... Never had a issue??
Click to expand...
Click to collapse
Yup. Been using it since it's release. Restored many backups with absolutely no issues.

Absolute_Zero said:
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
Click to expand...
Click to collapse
id be willing to bet most people dont know,lol.they prolly just blindly downloAd rom manager and flash it. i checked to see if it was there,after seeing this as one of the last statements in the root post: Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
Absolute_Zero said:
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
Click to expand...
Click to collapse
its one of the things i really love about htc. i got used to installing recoverys,splash screens,etc. on my incredible,then started experimenting with img files on my eris,and discovered it was quite possible to simply move the images around kinda neat if you want to try a leaked ruu but dont want to wait for someone to post a CWM flashable roms. just pull out the hboot and stock recovery and flash away
it was quite common to manipulate things in hboot on the inc,but never mentioned in the eris forum,where most of the gurus frowned upon the s-off bootloader.kind of a shame... more bricked eris's prolly could have been revived after the clockwork fiasco if s-off was part of the common root process.
thanx for the android info info. when i make them up,it doesnt seem to matter which one i use. i dont think it even checks the text inside,i think you just need a text document titled "android info" lol

Thank you for the updated 5.0.0.1 cement recovery.

cam30era said:
Thank you for the updated 5.0.0.1 cement recovery.
Click to expand...
Click to collapse
Autocorrect fail? or did you have a problem with 5.0.0.1?

New EVO User, Old XDA User

So can I or can't I root my phone?
Any tutorials? Searched for an hour. :/
Coming from MIUI HD2 by the way.

If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448

I don't mean to be mean, but 5 posts below yours answers your question.

mattykinsx said:
If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448
Click to expand...
Click to collapse
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.

kariuki said:
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.
Click to expand...
Click to collapse
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there

Papa Smurf151 said:
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there
Click to expand...
Click to collapse
Thanks for the reply, but I had recently uninstalled Sync, I restarted my pc, and now it's working.
Had everything working, when I tried to boot a ROM, it was stuck on the htc EVO 4G screen. I went into recovery and wiped everything. Now I'm definitely lost.

Bump, hope it's not bricked...

If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!

Art2Fly said:
If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!
Click to expand...
Click to collapse
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.

kariuki said:
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.
Click to expand...
Click to collapse
It also helps to know what recovery you're using to flash. Depending on the rom amonra works better than clockwork. I use amonra but that's just my preference. Not getting past the white htc screen isn't that problematic, battery pull vol down+power. How long you sit on the htc screen depends on the rom, some roms take all day to boot on that first one and you need to just let it sit and not panic. Some roms just don't work on some phones. I love Evolved's work but I could not get his "Directors Cut" rom to get past the white htc screen but my guy has the same hardware as I do and his booted right up. To me there is no perfect rom, it's the rom that's perfect for you. We're all different people and like different things. Happy flashing.
p.s.- Just make sure you do the usual wipes before flashing alot of devs also have a format zip that you should use as well. It really doesn't matter which one. Used them all and don't really have a preference to either of them.

Try doing a search next time buddy..

someonenewhere said:
Try doing a search next time buddy..
Click to expand...
Click to collapse
Why should he? Every question he asked, with attitude even, was answered in his thread even though the answers to all his questions were available all on the front page of the forum.
Sent from my Nexus S 4G using Tapatalk