Database Develop

A Request for the Unrevoked Team

I don't want to jump on IRC and I don't know where else to post this, but I have a small request, if possible. Can you fine folks make the recovery flasher so that you can add your own updated recovery images? Currently, the flasher only only installs clockwork 2.0.1.0 and there is a version 2.0.1.3 available, but no way to make it stick.

Install ROM Manager from Koush on the android market, and update your recovery that way.

It does not stick. Please read my post. Its easy enough for you to check yourself. I have Rom Manager already. It cannot work any magic. Once you reboot, you are back to the original version that the recovery flasher puts on there.

really? mine works great....

Boot into clockwork and look at the version number. No, it does not.
Rom Manager thinks its flashing an updated version, but thats not the case.

Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.

Post an image please.
Nobody called you a liar, and if you think I am being a jerk, you are way too sensitive.

I have this same problem. Mine is at 2.0.1.0. I believe koush was in the irc channel last night saying something about it.

Thanks for the update.

fennellchrid said:
Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.
Click to expand...
Click to collapse
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.

I am currently at work... If I had a camera I would. Ask some other people to do it, and I promise they will tell you the same thing. If you read in the Recovery Reflash Tool forum, you will see others talking about this very same thing.

I see just as many from the other side of the fence. What do you think of that?

sdorn77 said:
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.
Click to expand...
Click to collapse
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.

that's correct, koush's rom manager uses a fake flash to upgrade the recovery versions. It does not stick if you boot normally into recovery without rom manager. If we weren't pursuing other things you will like even more we would make a way to flash custom recoveries. But we will instead work to eventually give you true nand unlocked everything. just in the meantime except what you have please. You don't always have to have the latest! I
If a serious issue is found requiring a real update we will get to it.

Please don't take this as a demand, or dissatisfaction. I am very happy with what you folks have done so far and can certainly wait for whatever the team decides to do I was just reading that some versions of Clockwork were having trouble with Froyo and was looking to the future. Thanks for replying

sdorn is correct. Hitting recovery from ClockworkMod is 2.0.1.3 and a fresh boot into recovery (adb, hboot) is 2.0.1.0. The recovery will probably have to be flashed from unrevoked's tool to get up to the latest version or until NAND is unlocked outside of hboot.

not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,

junjlo said:
not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,
Click to expand...
Click to collapse
Power the phone off, and then boot into recovery by holding Vol Down + Power and selecting RECOVERY. You have 2.0.1.0 installed.

Lock
Mods may want to lock this thread ... it continues to be a debate when the question was answered by Shadowmite.

fennellchrid said:
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.
Click to expand...
Click to collapse
Very classy response.

Stock FRF91 unrooted to rooted FRF91?

I searched and read through some of the threads and really didn't find a conclusive answer to what I am looking for. So I decided to create a new thread.
My question is: Is there any way to root the N1 that has Stock FRF91? I'm not a noob in rooting, just wanted to make sure. I don't really care about unlocking the bootloader (warranty isn't an issue for me).
Can I just use the fastboot oem unlock command to unlock bootloader then install the custom recovery and install custom roms? Or is there a new method to rooting Stock FRF91 currently.
Thanks

Yes.
http://forum.xda-developers.com/showthread.php?t=715798
You're welcome. Get familiar with the search tool.

Frankenstooge said:
Yes.
http://forum.xda-developers.com/showthread.php?t=715798
You're welcome. Get familiar with the search tool.
Click to expand...
Click to collapse
The instructions in that link wont work for stock FRF91 with stock recovery. I couldnt get the Amon recovery to load onto my phone in order to flash the root. I have tried to ADB it 5 times and each time it says successful, but when i go into recovery all i get is the android with the !.
By all means OP, you can try this and if you get it to work, let me know what you did. I tried 5 times and couldnt get it to work.
my bootloader is unlocked also.

ecapox said:
The instructions in that link wont work for stock FRF91 with stock recovery. I couldnt get the Amon recovery to load onto my phone in order to flash the root. I have tried to ADB it 5 times and each time it says successful, but when i go into recovery all i get is the android with the !.
By all means OP, you can try this and if you get it to work, let me know what you did. I tried 5 times and couldnt get it to work.
my bootloader is unlocked also.
Click to expand...
Click to collapse
after you pushed custom recovery, did you press Volume Down button while rebooting to go directly into recovery? because after you install custom recovery and let the phone reboot, the stock recovery will remain; you should try to go into recovery immediately after pushing the amon ra recovery without letting the phone boot up
let me know if that works

What is the method for rooting "without using SDK tools"? There are emulator apps in the market but they refuse to work without super user permissions? I have stock frf91 and looking for a way to root my nexus one?

jblazea50 said:
after you pushed custom recovery, did you press Volume Down button while rebooting to go directly into recovery? because after you install custom recovery and let the phone reboot, the stock recovery will remain; you should try to go into recovery immediately after pushing the amon ra recovery without letting the phone boot up
let me know if that works
Click to expand...
Click to collapse
that did it sir. thank you. Was it like this in 2.1? I dont remember having it revery back to stock recovery when following the tutorials. Then again maybe i never let it completely boot back up...

ecapox said:
that did it sir. thank you. Was it like this in 2.1? I dont remember having it revery back to stock recovery when following the tutorials. Then again maybe i never let it completely boot back up...
Click to expand...
Click to collapse
that's great; it was the same on 2.1, you probably just can't recall at the moment
glad it worked

jblazea50 said:
that's great; it was the same on 2.1, you probably just can't recall at the moment
glad it worked
Click to expand...
Click to collapse
Interesting. So once you use the Amon recovery it sticks as long as you dont reboot after you install it. I guess i was just lucky the first time!

[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?...

[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] [Help] ICS black screen on bootup

Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.

anonymousthing said:
Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.
Click to expand...
Click to collapse
Your phone must be rooted before this and also verify your downloaded zip file with checksum to make sure about proper download.

I actually encountered the same problem a few days ago. I realized it was because I flashed an incompatible Kernal zip file. So I reflashed the ROM and rebooted without flashing any kernals and it worked for me.

I have rooted, and have superuser access. I have also redownloaded and checked the md5 sums. I'll try to download it again and test...

I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S

anonymousthing said:
I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S
Click to expand...
Click to collapse
have u converted you filesystem to ext4?
btw, what rom was previous? stock one or custom?
and i recommend you to use 4ext recovery instead of CWM

I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock

anonymousthing said:
I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock
Click to expand...
Click to collapse
if u have CM7 ur filesystem already converted )))
i think the reason of crashes on boots is old version of recovery. try to upgrade urs CWM or install the latest 4ext recovery
It's very easy to change CWm to 4ext: go to http://4ext.net/ and download 4EXT Recovery Updater, install it. With its help u will instal 4ext

Are you s-off?
Sent from my Incredible S using xda premium

I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime

anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
i'm afraid s-on is the reason of ur problems

I completely agree s-on does matter always.

I have the same problem on Quattro.
If you are s on you have to flash via fastboot the boot.img inside the Rom.zip from your wanted rom after flashing Rom via recovery.
Fastboot flash boot boot.img
Sent from my HTC Incredible S using xda premium

Indeed sniper is correct. However what I would do, get a rom working then look into becoming s-off. Its so much easier to mod your phone after.
Sent from my Incredible S using xda premium

Okay, thanks guys! I'll try it out later and see how it goes by flashing boot.img using fastboot.

Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.

anonymousthing said:
Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.
Click to expand...
Click to collapse
Or just make s-off one time and flash roms without any necessity to flash boot.img manually
Sent from my Incredible S using Tapatalk

I have HBOOT 2.0, sadly I accidentally updated my original htc and it updated HBOOT as well... and I can't be bothered to downgrade now lol
I'll do it later when I have the time to download the downgrade toolkit

anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
I had a issue with something on my SD card after i wiped my SD and tried the re install it worked.
let me know if that helped.