[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

Search This thread

kozmikkick

Senior Member
Nov 26, 2010
1,278
1,215
Seattle, WA
Hey cubed. I was thinking. If you added flash boot to the menu then programed it so that you select the Rom you just installed and make it so that it extracts the boot.img from the Rom and puts it into a bootloader friendly zip file and reboots into boorloader. That might be one way to do it. All things that are possible in cmw I believe. Just a thought.

Sent from my HTC Raider X710e using xda premium
 

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Hey cubed. I was thinking. If you added flash boot to the menu then programed it so that you select the Rom you just installed and make it so that it extracts the boot.img from the Rom and puts it into a bootloader friendly zip file and reboots into boorloader. That might be one way to do it. All things that are possible in cmw I believe. Just a thought.

Sent from my HTC Raider X710e using xda premium

Great minds think alike :) That's what I've been working on implementing for the past month or so, although I have a method of getting it to work that is very streamlined (well, relatively speaking versus s-off)


As for the "recovery doesn't work; flashes text then reboots" bug, I'm still looking into it...
 
  • Like
Reactions: Sharpenologist

4D3

Senior Member
Oct 20, 2008
4,353
265
Brisbane
As for the "recovery doesn't work; flashes text then reboots" bug, I'm still looking into it...

Hi,

I have been playing with this on 2 vivids, mine which is laden with apps and an AV scanner, and my wifes which is minimal - Both have the issue, but my wifes has it less, maybe 10% of the time I get it.

Another thing I found, is it seems to wipe the cache or something like that as when it does reboot it seems to have removed applications/settings i have recently changed or installed.

if there is anything you would like me to try for you I have my devices at your disposal.

Thanks
 

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
could i possibly get the ICS HBOOT PH36IMG hotlinked or an attachment, i can't get on goo inside from this computer. Thanks :D

Unfortunately I don't have any other places to host files at the moment... github says I can't upload it there since i'm "over the limit" for free users (whatever that means).

Suggestions?
(I also believe goo was having problems today, it should be back to normal now)
 
  • Like
Reactions: Sharpenologist

Lord Nykon

Senior Member
Jan 2, 2012
57
1
When I try to flash the zip in hboot , I get a listing that says no image or wrong image. When I try to get into recovery, it just freezes on HTC white screen. What am I doing wrong? The zip is exactly labeled as you said it should be


Sent from my MB870 using Tapatalk 2 Beta-5
 

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Hey, I updated the first post with instructions for anyone who can't get into recovery.

The simple gist is to just boot to fastboot, and run "fastboot erase cache", then format /cache from recovery.

Easy fix!

I'll make a build of CWM that doesn't care soon... I smell a CM9 or CM7 release soon though, and it should be included there :)
 

ki11bert

Senior Member
Jul 17, 2011
139
19
I'm using your take two and i don't see the orange l e d on while I'm in recovery. do I assume that its charging?

Sent from my HTC PH39100 using XDA
 

bluenaif

Member
Nov 9, 2010
35
1
(Noob Alert) lol

I'm running Dark Raider 1.5.5. with Faux kernel and I can't get into my CMW. It stays on white and green HTC screen. Is it okay to use "Alternate installation method: ph39img.zip"
 

8125Omnimax

Senior Member
Jul 1, 2006
268
109
New York City
(Noob Alert) lol

I'm running Dark Raider 1.5.5. with Faux kernel and I can't get into my CMW. It stays on white and green HTC screen. Is it okay to use "Alternate installation method: ph39img.zip"

Dude don't cross post so much, guys on here get annoyed, and I'm not sure if any of them are on bath salts....so to avoid being ones dinner keep it to one thread lol. I answered one of your other threads, pm me if you have any issues

Sent from my HTC PH39100 using xda premium
 
  • Like
Reactions: bluenaif

Monkeymannnn

Senior Member
Apr 17, 2012
212
42
Possibly a dumb question, but the ph IMG denoted as the ICS ota one is no longer downloadable. Is the other ph okay to place in the ext sd to go that route? S-off, juoput hboot, currently Pegasus ROM...

Sent from my HTC Holiday using xda premium
 

kevsthabest

Senior Member
May 5, 2009
81
126
Possibly a dumb question, but the ph IMG denoted as the ICS ota one is no longer downloadable. Is the other ph okay to place in the ext sd to go that route? S-off, juoput hboot, currently Pegasus ROM...

Sent from my HTC Holiday using xda premium

The file host for the that image had a database issue and lost all the hosted files.

Just flash it through fastboot, its the most reliable and safest way of going with.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    Howdy y'all!

    I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.

    It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.

    This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one :)

    So, without further ado:

    What is this?
    This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.

    How do I use it?
    You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)

    Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
    Code:
    fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
    You need to replace the stuff in brackets with the path to the img file you downloaded from here...

    Alternate Installation Method (ph39img)
    Much easier installation once unlocked with HTCDev...
    Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
    Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!

    How is this different from the ClockworkMod image that's floating around here?

    Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.

    Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device :) )

    I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me :)


    Changelog
    recovery-take1 : initial release

    recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks :)

    Tips and Tricks (what works, and what doesn't)
    Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...

    • The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
      At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
    • Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://xdaforums.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
      If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
    • If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint :)
    • Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
      This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
      To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
      Sorry about that!
    • Some rom.zip's don't work...
      This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version :)
      If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
    • HELP! I CANT GET INTO RECOVERY! *new!
      If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
      Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
      This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.

    How can I contact (chastise, praise, call names) you?

    On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
    Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.

    I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...

    Standard "it might not work" clause

    This software hasn't been thoroughly tested, and it might not work.
    It might not backup things correctly, and it might not restore them right.
    Please don't trust this software with anything sensitive or life-alteringly important.
    I'd hate to say "I told you so!" :)

    That's not to say this software doesn't work, it's just the standard disclaimer.

    Donation Information
    I love to develop. I don't do this for money, I do it just for the "thanks".

    Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
    Thank you in advance!

    Credits / Thank You's
    • IanWizard-cloud (testing, moral support :) )
    • Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
    • joeykrim
    • toastcfh
    • fattire
    • BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
    • ..and lots of others!

    Thanks for giving this looong post a read! :)
    Good luck!
    5
    Added links for Chargemode enabled recoveries :)
    5
    Heads up: new version supporting chargemode is on it's way :)

    AAAND, I think I may have a solution to be able to flash boot.img (aka Kernels) from recovery. It's a bit of a convoluted solution, but it will work, and should be fairly easy for the user to deal with.

    I'll post a link to the new version (and change the title of the thread) after i've got a few verifications that the recovery chargemode does indeed work 100% as expected.
    4
    THANKS FOR THIS!!!

    I was going crazy w/o the power-off battery charging screen!

    Was it difficult to add in?

    Not too bad, just took a little bit of thinking as for how to properly add it into the makefiles for recovery.

    Now I'm on to my next milestone: restoring/flashing kernels from within recovery.

    HTC actually has a method for doing this properly, it's called "write_firmware_image", and it's how HTC flashes boot.img and modem updates from within recovery. There's no real magic to it, but the process is as follows:

    In the updater-script, a ROM developer calls:
    Code:
    write_firmware_image("PACKAGE:firmware.zip", zip);
    which takes a PG36IMG.zip style file, and writes it DIRECTLY to /cache, destroying the filesystem of /cache in the process...

    After the zip is written directly to /cache, recovery sets a flag in the MISC partition saying "update-zip" then reboots.

    The phone then reboots to hboot and seamlessly applies the update, then reboots back to recovery so that recovery can format /cache to get a working EXT4 filesystem back in there.

    Here's the snag: HTC isn't using any standard for the way they use the MISC partition. Normally, you'd have a partition that the first few hundred bytes or so were dedicated to "bootloader commands", but on ours-- our MISC partition contains our CID and some board flags there. Even better, it would appear that the partition is write protected by hboot.

    Anyway, I'm taking some time out from working on CyanogenMod 9 to get this going, since it's the #1 requested feature so far.

    Also, in case anyone's interested, I mapped out the partitions on our phone: http://pastebin.com/iyBnjRRa .

    Hopefully I'll have an update here soon...
    4
    Hey, I updated the first post with instructions for anyone who can't get into recovery.

    The simple gist is to just boot to fastboot, and run "fastboot erase cache", then format /cache from recovery.

    Easy fix!

    I'll make a build of CWM that doesn't care soon... I smell a CM9 or CM7 release soon though, and it should be included there :)