Database Develop

[RECOVERY] ClockworkMod Recovery for Vibrant (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-vibrant-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Vibrant as your phone.
Accept the Superuser prompt.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!

Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App

youneek said:
Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes! That is expected! The very first boot WILL FAIL, the recovery needs a kick start to complete installation.

little tip
after I downloaded Rom Manager and had it download the recovery for my Vibrant.
After the success message I waited nothing happened so you may have to select to manually reboot into the recovery, then select "reinstall packages" to finish the installation.

I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong

metalfan78 said:
I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong
Click to expand...
Click to collapse
he either took it down and is gonna release it later or something... just wait..

I don't even see "Vibrant" in that list
Nevermind....see above

lp894 said:
I don't even see "Vibrant" in that list
Click to expand...
Click to collapse
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.

Sweet I can't wait to have a real recovery

Koush said:
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.
Click to expand...
Click to collapse
I can confirm I used Wifi and have already completed my first backup using Clockwork
thanks Koush.. buying the prem version to show my support!

Bummer I guess ill have to wait until I can find a hotspot

I downloaded the clockwork Rom Manager premium and I press the pFlash Recovery button. But I don't see Vibrant in the list either.

Please make sure you guys are on wifi. T-Mobile is caching your webpages and serving you older versions.

when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..

ElChibo said:
when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..
Click to expand...
Click to collapse
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.

metalfan78 said:
Bummer I guess ill have to wait until I can find a hotspot
Click to expand...
Click to collapse
No, you don't have to. Just go into your browser, go to menu-->more-->settings-->clear chache and that will get you going

Koush said:
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.
Click to expand...
Click to collapse
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?

ElChibo said:
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?
Click to expand...
Click to collapse
If flashing manually, yes. Just flash using ROM Manager though, and it will handle that all for you automatically.
I can't permanently replace the recovery until the kernel source and whatnot is released for the Vibrant.

Hells yeah!!! Will someone PLEASE put a shipped firmware out now? Like the T959UVJFD. I appreciate the life saving effort from MS_Guru, but t959uvje8 is not jiving with me and my 3g and/or wifi...

Amazing work! Excellent idea for a 100% safe recovery! Kudos!!
Sent from my SGH-T959 using XDA App

[Update] - ClockWorkMod v2.5.0.4 Released

Grab it here:
General: http://koush.tandtgaming.com/recoveries/
Direct Link: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
Use unrEVOked v3.1 to flash custom recoveries (at your own risk, of course)
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone

Updated, no issues. Thanks!

Thanks. I updated without issue.

is it better than the old?
Sent from my Incredible using XDA App

jdkoreclipse said:
is it better than the old?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes.. it's 0.0.0.3 times better than the old!

If you rooted with unrevoked 3.0 can you just use that with this image?
Sent from my Droid Incredible using the XDA App

Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?

i don't really see a point in updating since it already works for me now...

rom manager reports the older version for me, but booting into recovery it is reporting the newest .4 version

Lexus One said:
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
ROM Manager cannot flash recovery because NAND is still locked. Only through the unrevoked tool does NAND temporarily unlock in order to flash clockwork. So if you followed the steps correctly using the unrevoked tool then you have the correct version. Booting into recovery (I think you can't boot through ROM Manager, boot manually or via boot loader) should show the updated version.

Lexus One said:
I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?

elborak said:
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
Click to expand...
Click to collapse
recovery by ROM Manager I get 2.5.0.1
recovery by vdown & Pon I get 2.5.0.4
Thanks, now I'm confused even more. Why are they different? And when I go back into ROM Manager it still reports 2.5.0.1. So my original question still stands: How do I get ROM Manager to display the correct version of recovery which is really 2.5.0.4? Even more...why does the recovery manager report 2.5.0.1 when booting into recovery via ROM Manager? This is reallyyyy strange!

I answered your question two posts back...

s197 said:
I answered your question two posts back...
Click to expand...
Click to collapse
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.

Lexus One said:
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Click to expand...
Click to collapse
If i understand this correctly: The version that ROM Manager reports and boots into is actually a virtual version. This is because, due to the fact that NAND isn't unlocked yet ROM manager can't actually write to it, So when it is "flashing the recovery" it really is only flashing a "virtual recovery". This is why you could on some phones have an older version of recovery flashed and ROM manager would report a newer version that is available.
In short to answer your question, you can't get ROM manager to report the newer version until rom manager has that newer version in it's list, which it currently does not. And even when it is in the list it makes no difference anyway, because unless you boot into recovery using the power button and volume button, the recovery that you boot into will be a virtual one anyway.... so it really makes no difference what ROM Manager is reporting.
And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.

obsidianblackhawk said:
<snip> And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
Click to expand...
Click to collapse
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?

Lexus One said:
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Click to expand...
Click to collapse
other than flashing a new recovery, the recovery that rom manager boots into works exactly the same as the "real one" in fact i don;t do it the "hard way" any more.

This is probably a dumb question but do I open the img file after I plug in the phone?

Lexus One said:
how to get ROM Manager to report the correct version.
Click to expand...
Click to collapse
Easiest way is this:
1) Uninstall ROM Manager.
2) Reinstall ROM Manager.
ROM Manager will now display no version, as opposed to the wrong version.
And then...
Never again use the "Flash ClockworkMod Recovery" command in ROM Manager. If you want to update recovery, use the unrevoked flasher with the custom recovery option.

Changes?...

Help! Can't get into recovery/clockwork...

Could somebody kindly tell me how to boot into clockwork recovery? I've tried reboot into recovery from cm7s built in poweroff menu, Rom manager, and manually(both pressing down volume at start, or holding the nook-button at start). Searching google the only answer I found is pressing the n-button for two seconds while booting, but that doesn't work. Do you have to have some jedi-like timing to get into recovery? Doesn't matter what I do, I always end up cm7.

BrotherZero said:
Could somebody kindly tell me how to boot into clockwork recovery? I've tried reboot into recovery from cm7s built in poweroff menu, Rom manager, and manually(both pressing down volume at start, or holding the nook-button at start). Searching google the only answer I found is pressing the n-button for two seconds while booting, but that doesn't work. Do you have to have some jedi-like timing to get into recovery? Doesn't matter what I do, I always end up cm7.
Click to expand...
Click to collapse
No Jedi tricks.....I usually hold the n for a 6 count. Also, what version of recovery do you have? Current is 3.0.2.8. I had 3.0.1 do some flaky stuff the other day and had to flash current version
sent from my Ginger-Hero CDMA

Thanks for the reply.
Yeah, that seems to be it. If I go in to Rom Manager, it says I don't even have clockwork installed. So I can't even tell which clockwork I used!
I used this guide when I installed CM7
http://forum.xda-developers.com/showthread.php?t=1030227
So I should have installed Clockwork. A while since I did it, but going by my download map I used 3.0.1.0. But how should I flash the current version when I can't even access recovery?

Just use rom manager to flash the latest and greatest. Makes things a lot easier

BrotherZero said:
Thanks for the reply.
Yeah, that seems to be it. If I go in to Rom Manager, it says I don't even have clockwork installed. So I can't even tell which clockwork I used!
I used this guide when I installed CM7
http://forum.xda-developers.com/showthread.php?t=1030227
So I should have installed Clockwork. A while since I did it, but going by my download map I used 3.0.1.0. But how should I flash the current version when I can't even access recovery?
Click to expand...
Click to collapse
Like Ace said. Boot CM7, open Rom Manager and one of the 1st menu options is flash recovery. Use that and it will install recovery to EMMC.
sent from my Ginger-Hero CDMA

Thanks all. Usually I use cwm manually, wasn't aware of that Rom Manager made everything so easy. =)

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

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.
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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://forum.xda-developers.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...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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...
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!

Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.

already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now

Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.

Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!

well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?

Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium

Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC

Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.

for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.

Just put your new recovery in the superguide and gave you credit. Keep up the good work!

There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew

drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100

Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew

drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100

Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk

I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.

hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.

Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse

ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks

[Q] Cannot boot to CWR

OK, so I'm using ICS beta 4 for the Streak, and on ROM manager it says I have CWM 3.0.2. But when I try to boot into it, I either get stock recovery or fast boot. When I click on Software upgrade via update.pkg on SD card, on the stock recovery my screen turns blank and I have to hard reset.
Can someone help me get Clockwork Recovery please? Thanks!
PS. I used NVflash to flash ICS, don't know if that helps, but Im trying to provide sufficient information.

ICS B4 comes rooted with SuperUser7 and CWM 4.0.1.4 installed. Don't think that your supposed to use a ROM manager with it. Not sure how you have another CWM version unless you installed it yourself.
Reflash again and don't use the ROM manager app.

OK, well if it came with it, why can I not boot to it. I downloaded ROM manager but never used it. Never installed and other version of CWM, and if I did install another version, wouldn't I be able to see it? I can not boot to CWM.
Thanks for your suggestion, but reflashing is last option. Does anyone else think they know what's going on?

DO NOT USE ROM MANAGER!
First off, CWR isn't working very well right now, I have a new recovery image I've created that adds some functionality to recovery but its still a work in progress.
To get into recovery mode:
1) Power off device
2) Press Power and Volume+, hold
3) You will come into the Dell recovery menu
4) Use Volume (-) to get to "Install Package" and press Power to select
5) You are now in CWR

When I tried that it lagged a second and then booted normally. I'll post a video in a bit.

Oxymorphiend said:
When I tried that it lagged a second and then booted normally. I'll post a video in a bit.
Click to expand...
Click to collapse
Did you use ROM MANAGER and flash a recovery? If you did, recovery is hosed and you will have to fastboot flash the recovery from the B4 directory.

I did use rom manager. And where would I find it in the directory?

Oxymorphiend said:
I did use rom manager. And where would I find it in the directory?
Click to expand...
Click to collapse
Look in your ICS B4 download, you'll see "recovery.img" file.

Thank you both. I finally signed up when I had my first problem, and you guys hooked me up with speedy replies. Much appreciated.