Database Users

How to get older version of ROM Manager?

I just formatted my phone back to factory settings. I am in the process of installing all my apps again and just realized I purposely never updated my ROM Manager to the latest version because of the new permission is asks for (the one that lets ROM Manager use your account authentication information). So, is there any way for me to download an older version of ROM Manager?
Thanks!

DarkAgent said:
I just formatted my phone back to factory settings. I am in the process of installing all my apps again and just realized I purposely never updated my ROM Manager to the latest version because of the new permission is asks for (the one that lets ROM Manager use your account authentication information). So, is there any way for me to download an older version of ROM Manager?
Thanks!
Click to expand...
Click to collapse
try here
http://search.4shared.com/q/1/rom manager.apk

*bump* Anyone with a more legit source than 4shared? Thanks!

Install the new one and quit being paranoid?
Sent from my SGH-T959 using XDA App

Dude, koush is really well respected and trusted.

bauerlucas said:
Install the new one and quit being paranoid?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1.. then you can install older version if you dont like.. built in on ROM Manager..

Thanks for the suggestions but I have my reasons for having strict access control on my phone.

Is it because you are a Dark Agent?

Yes, you got me.

Is there no way to download older version of apps from Market?

^ why don't you just email koush man? I'm sure he would send you the .apk, and think you are crazy paranoid too.

Good suggestion.

Rom Manager
s15274n said:
^ why don't you just email koush man? I'm sure he would send you the .apk
Click to expand...
Click to collapse
I send him two polite emails about Rom Manager, and he never to the time to answer. A bit sad somewehere.

What do you use ROM manager for? Use the update.zip for root and to install recovery and then use recovery for all of your flashing. I only used ROM manager one time to install recovery
Sent from my GT-I9000 using XDA App

bfranklin1986 said:
What do you use ROM manager for? Use the update.zip for root and to install recovery and then use recovery for all of your flashing. I only used ROM manager one time to install recovery
Click to expand...
Click to collapse
That is what I am trying to do, but cannot as it wont flash Clockwormod.Therefore cannot root. I cannot use abd as I am on mac OSX 10.4.I suppose that what you meant by the update zip.
T.

s15274n said:
GREAT, I AM ON JFD NOW - HOW DO I ROOT?
You are likely still connected to your PC and booted up to the T-Mobile jingle. Great, drop the notification bar down and mount your phone...
HERE ARE THE STEPS TO FOLLOW....
BUT FIRST... WHAT UPDATE.ZIP FILE DO YOU NEED?
There are two options here. Choose before you start.
A – an update.zip (633KB) that roots your phone only. You can then install Rom Manager from the Market to flash CWR (Clockwork Recovery) and install custom ROMs. There have been issues with CWR not flashing properly recently (June 2011), hence Option B.
B – use the other update.zip (1.7MB) and this will flash CWR for you – allowing you to immediately flash a custom ROM.. I do this because it's faster.
So, A or B?
1.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
B: Download this update.zip file to flash CWR... you will need to flash a custom ROM for Root. I prefer this method.
Also, download the ROM you plan to flash (assuming you are not sticking on JFD – why would you).
LINK TO THE DEV SECTION
2. Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/
3. Unplug the USB (assuming you are still connected after using ODIN)...
Hold down volume up + volume down + Power for about 9 seconds.
If you prefer, you can power off your phone, then hold in all 3 buttons to boot into recovery, I don't see the point in waiting for the phone to power off.
This will get you to a recovery menu (blue/purple text) after some yellow text.
4. In this (the stock recovery menu) select 'Reinstall Packages'
Use volume to navigate + power to select.
5. It will cycle a bit, you will see that yellow text again, then it will return to the stock recovery. Select Reinstall packages again.
You are now in CWR (clockwork recovery).
You can either reboot, flash your new ROM or make a backup now... I COVER HOW TO FLASH ROMS LATER – JUST KEEP READIN BELOW
Yeah, it is that easy!!
Click to expand...
Click to collapse
Give S15724N a thanks. The first update.zip will just root you. The second with boot you into CWR so that you can flash a custom ROM (all of which have root)
edit: here is the post so you can grab the files

Clockworkmod does not work!!!

I'm really at a stage now where i wanna just throw my htc desire hd at the wall!!!! I am trying to just install a custom firmware, not much to ask considering the mammoth amount of hacking you have to do to even downgrade the firmware. I have done absolutley everything that needs to be done to root this device, i have downgraded the firmware i have rooted it, switched off eng s-off and radio s-off i have full root acess with terminal emulator, i put the update zip on the sd card it says something about installation invalid thats because first time i did not disable radio s-off then it went slightly further but then said some other error i have tried everything, i tried rom manager and selected reboot in recovery mode but now it just makes the phone freeze on the htc boot screen when selecting recovery from the boot menu, can someone please please help, how hard can it be just to install coredroids firmware, why can't it just be as easy as the pd98img firmware
help much apprieciated

clockworkmod recovery works fine. Something has just gone wrong with your installation.
To avoid complications later on, you haven't "switched off ENG S_OFF" you've made made S-ON S-OFF and added ENG S-OFF.
You talk about update.zip, is this for a ROM (CoreDroid?)? Which ROM? Did it tell you to rename it to update.zip? If a ROM then it had nothing to do with Radio S-OFF as you only need that for flashing radio.img files and if it was a radio you were trying to push you should use fastboot not recovery. Are you using the right version of recovery (it's very specific about the version required)?
When everything has been installed correctly and instructions followed it is VERY easy to install coredroid's ROM.

hi thanks for the reply, i just follwed the instructions for installing a custom rom as it asks u to chang it to s-off but the guide also says you need to install the update.zip for clockworkmod to get to choose the custom flash rom you want to use but all i get when i select update.zip from the recovery menu is e:signature verification failed installation aborted

Ok, they don't make it very clear do they?
Have you got ROM Manager installed?
Have you got clockworkmod recovery installed? If so what version is it. If not then use ROM Manager to flash it and flash 2.5.1.3 version (as that what it says).
Get the above. Then let me know.

hi mate its version 4.2.0.2 if i select flash clockworkmod recovery it completly causes the recovery menu in bootloader to just hang on the htc startup screen

stephenuk said:
hi mate its version 4.2.0.2 if i select flash clockworkmod recovery it completly causes the recovery menu in bootloader to just hang on the htc startup screen
Click to expand...
Click to collapse
Sorry, I meant recovery version but it looks like you still need to do that.
In that case push the recovery.img file (grab from the Coredroid thread) using fastboot.
Normally issues are because people miss things but you've confirmed you have ENG S-OFF, Radio S-OFF and root.

ok i tried running this image file in fastboot from this thread http://android.modaco.com/content/z...led-tft-30-nov-2-5-1-3-clockworkmod-recovery/
its written ok but when i select recovery from bootloader it just hangs on the htc startup screen grrr this is just impossible.

That's not for the desire HD.
Grab a 3.x.x.x version from clockwork 3.0.2.8 thread and try that (you can downgrade easily once we got something working).
Sent using witchcraft via XDA Developers Premium App.

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)

Verified, ran August GB RUU and phone re-rooted

Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************

kzoodroid said:
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
Click to expand...
Click to collapse
I can't seem to find a link to to superuser inside ROM Manager. Can you tell me where to locate it?
thanks,
John

under download rom > extras

kzoodroid said:
under download rom > extras
Click to expand...
Click to collapse
You can also get it from here

Thanks to you both. I didn't even click on the Download ROM because it's premium and I'm still getting my feet wet with the whole root thing. I'm off to try the GB RUU w/radio and then re-root.

What if you have s-on?

You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.

kzoodroid said:
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
Click to expand...
Click to collapse
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..

deadsoulboy said:
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
Click to expand...
Click to collapse
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.

kzoodroid said:
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
Click to expand...
Click to collapse
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC

Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.

Flash clockworkmod recovery first, then the superuser zip.

I tried that but it gives me an error saying: "An error occurred while attempting to run privileged commands!".

If you flashed the GB RUU and lost root and/or s-off.
Someone correct me please if I'm wrong but couldn't you download the froyo RUU and load it then root and s-off?
Sent from my ADR6300 using XDA App

How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?

deadsoulboy said:
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Click to expand...
Click to collapse
The Eris had a manual method (race method) for rooting the phone but I could never find one posted for the Inc. It involved having the phone connected to a pc with adb running and then taking out the sdcard and rebooting, at a certain point of the boot process you counted to 4 and then pushed the sdcard back in. If you did it correctly adb was able to connect to the phone and you could slip a custom recovery and su in. It was rather complicated and only a handful of people ever did it correctly myself included and it was eventually replaced by a one-click method. The one-click method still pretty much does the same thing you just don't have to manually remove the sdcard or have the phone connected to a pc. In some ways the Eris has a lot more support from its community than the Inc does probably because it was Verizons first android phone.

k_nivesout said:
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
Click to expand...
Click to collapse
I second this it has to be a flashable version (contains android-info text file + the recovery image) to work. I used the 3.0.0.8 file from doug pistons website which is already to go just needs to be renamed PB31IMG.zip and make sure it isn't being named PB31IMG.zip.zip as file extensions can be hidden especially if you are renaming it on a pc. I downloaded it directly to my phone and renamed it there so the extension wasn't hidden.

swskeptic said:
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Click to expand...
Click to collapse
I beleive that is becasue you stil have the stock recovery? Did you flash the clockwork recovery from dougpiston.com?

I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.

swskeptic said:
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
Click to expand...
Click to collapse
First thing are you getting into recovery from the hboot menu? And you can't get into recovery from ROM Manager because you need superuser installed to do it that way. It still sounds to me like you don't have ClockworkMod Recovery installed. Maybe only version 3.0.0.8 works I'm not sure but that version is for both amoled and SLCD screens. So either try reflashing your copy of 3.0.0.7 or try flashing 3.0.0.8. I do think I had to flash the recovery a couple times to get it to stick.

DEsire Z/G2 added to official bootloader unlock program

Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/

noob here with a question... rooting is the same as unlocked bootloader??

coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.

thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?

coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.

I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?

flash custom recovery first, from there flash the rom

if you're s-on, bootloader is still locked....

artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying

I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.

how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.

pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!

flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.

HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.

Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.

I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.