Develop Bugs

[Q] FML...Should have left well enough alone.

So i somehow went hiroshima on my one x. I'll keep it short and simple. Had my BL unlocked but was running CWM recovery and the stock rom. Tried installing the cyanogenmod 9 and things went to hell after i flashed the boot.img. Now I am stuck at the white HTC screen. I read the disaster recovery but I am still having no luck. I relocked the bootloader and reflashed stock recovery then i tried using the ruu utility but it said that it didnt match and then rebooted with some developer text on the boot screen. I used the getvar command and it says:
version-main: 1.28.720.10
Before the blowup I had ran the OTA.I was on 1.26.720.10. This is the ruu i tried to reflash. I cant seem to find the 1.28.720.10. I also tried pulling the sys and boot img files from the temp directory and manually flashing, it gave an error.
as of right now i have the bootloader unlocked again and CWM recovery reinstalled so i can charge.
please help! $20 reward via paypal to the person that helps me get back to complete stock!
The worst part is i dont even want this damn phone...lol

Try this mate. If you can still get to bootloader and recovery it recoverable. I'd go back to stock so its as if you bought the phone, just to be safe. So...
Open cmd and CD to your fastboot file location. Plug phone in and...
First flash a stock boot.img from your stock.zip
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
Then relock your bootloader.
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
Then run the RUU.
But make sure you have the correct one. So that includes region. If you started on 1.26 and you haven't done any OTA updates then you need 1.26 but with your region code.
Good luck!
Sent from my HTC One X using xda premium

i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?

applejoos said:
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
Click to expand...
Click to collapse
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium

benjamin.j.goodwin said:
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
So since there is no RUU matching my version number I am screwed now right?

Use the 1.29 ruu?

backfromthestorm said:
Use the 1.29 ruu?
Click to expand...
Click to collapse
there is no 1.29 for my region code.

applejoos said:
So since there is no RUU matching my version number I am screwed now right?
Click to expand...
Click to collapse
Do you know how to push a ROM.zip on to your SD card via command prompt?
Try downloading a custom ROM and flash the boot.img then, clear cache, then boot to recovery and flash the ROM. Then reboot. Should work.
Sent from my HTC One X using xda premium

[Q] [Question] Updating the radio image of WFS !

I was wondering that we all need S-Off to our phone to upgrade radio image manually else it gets updated only with either official update or with official ruu update file.....
We all know that we can easily find rom.zip file from the installation process of an official RUU.... I was wondering that if in between the process when the installer check information on our phone, if open the installer and get the rom.zip to change the radio.img from radio.img of europe or any other latest ruu, would it update the device with the latest radio ????
I m going deep into this process cos I couldn't get my phone S-Off due to certain reasons and want to get the latest radio update but I m bootloader unlocked which won't let me update the radio using fastboot commands cos it could only be done using official installation process....
If this helps then all of us would be able to b on the latest radio from htc which has an advantage of higher signal receiving capacity............

nikhilkaushik said:
I was wondering that we all need S-Off to our phone to upgrade radio image manually else it gets updated only with either official update or with official ruu update file.....
We all know that we can easily find rom.zip file from the installation process of an official RUU.... I was wondering that if in between the process when the installer check information on our phone, if open the installer and get the rom.zip to change the radio.img from radio.img of europe or any other latest ruu, would it update the device with the latest radio ????
I m going deep into this process cos I couldn't get my phone S-Off due to certain reasons and want to get the latest radio update but I m bootloader unlocked which won't let me update the radio using fastboot commands cos it could only be done using official installation process....
If this helps then all of us would be able to b on the latest radio from htc which has an advantage of higher signal receiving capacity............
Click to expand...
Click to collapse
I *think* its possible to update the radio while s-on. But a downgrade would not be possible at all.
Sent from my HTC Sensation XE using xda premium

Found another way out !
heavy_metal_man said:
I *think* its possible to update the radio while s-on. But a downgrade would not be possible at all.
Well I m sure downgrading needs a way out but I have found a way to get radio and hboot updated while staying s-on and unlocked....
If we install an RUU directly on unlocked state it doesnt get installed and gives some error but if we manage to install correct region files from the RUU made for our own region and only, system.img, recovery.img and boot.img needs to be flashed through adb tools using fastboot commands and when its done, just be patient and let the installation complete and then when it starts, we get a fresh mobile with new NON-ROOTED phone.... Don't root it so far and check system for updates and let it update and voila ! It'd update radio and hboot....
I m not sure what my hboot version was before update but my radio version was 7.53 before update but after it turnt into 7.57............
Click to expand...
Click to collapse

Or you could take the radio from the ruu rename it to pg76img.nbh (I think) and boot to BootLoader
As long as it is an update it should work without an issue
Sent from my HTC Sensation XE using xda premium

What I did was:
1) Lock bootloader using 'fastboot OEM unlock'
2) Extract rom.zip from an ruu (NOT the latest!) and then separate it into system.img, boot.img, recovery.img, etc...
3) Using fastboot, flash system.img, boot.img and recovery.img.
4) Again, using fastboot, wipe the data and cache partitions.
5) Now boot into your stock android.
6) Download the latest ruu and run it, following the on screen instructions.
7) This ruu will update your entire phone (INCLUDING the radio) to the latest version.
8) Now, reunlock your hboot using htcdev.com.
9) Flash clockworkmod recovery using fastboot.
10) Install whatever custom rom you want, or keep the stock rom.
Simple!
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app

Well done man
Sent from my HTC Sensation XE using xda premium

Thanks, I don't have a clue about developing roms. But I'll give back to the xda community in any other way I can...
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app

I did the same !
artturnip said:
What I did was:
1) Lock bootloader using 'fastboot OEM unlock'
2) Extract rom.zip from an ruu (NOT the latest!) and then separate it into system.img, boot.img, recovery.img, etc...
3) Using fastboot, flash system.img, boot.img and recovery.img.
4) Again, using fastboot, wipe the data and cache partitions.
5) Now boot into your stock android.
6) Download the latest ruu and run it, following the on screen instructions.
7) This ruu will update your entire phone (INCLUDING the radio) to the latest version.
8) Now, reunlock your hboot using htcdev.com.
9) Flash clockworkmod recovery using fastboot.
10) Install whatever custom rom you want, or keep the stock rom.
Simple!
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app
Click to expand...
Click to collapse
Well I did the same And now I m happy with my new radio

Won't work !
heavy_metal_man said:
Or you could take the radio from the ruu rename it to pg76img.nbh (I think) and boot to BootLoader
As long as it is an update it should work without an issue
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
This process won't work until the device is S-Off cos it doesn't get permission to write the radio until it is S-Off. Device unlocked won't help !

nikhilkaushik said:
This process won't work until the device is S-Off cos it doesn't get permission to write the radio until it is S-Off. Device unlocked won't help !
Click to expand...
Click to collapse
Hmm. I didnt think it would have an issue with an official update. Well that's proved me wrong
Sent from my HTC Sensation XE using xda premium

[Q] Can not install RUU

Hello guys.
I'm following this thread to install JB on my HOX.
Currently my phones cid is HTC__102
I almost crashed my phone yesterday as I was stuck in the boot loop, had to use adb to push ICS and install ICS back.
Now I noticed my HBOOT is 0.43, the thread says to download one of the file. I have no idea which one
Tried all 3 all 3 crashed, I'm not sure what happens.
These to run untill I get to this place (see attachment 0.png).
ruu_endeavor_u_ics_40_htc_europe_1.29.401.11_radio_1.1204.105.14_release_260491_signed_c9d22.exe and RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe exit with an error of "UNKNOWN ERROR" (see attachment 1.png)
and
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed.exe crashes and doesn't do anything.
One thing though, the phone is Unlocked, not sure if that matters and I'm using windows 8, but I run all the software in compatibility mode.
Thank you and sorry for my bad spelling.

You need to relock bootloader.
Sent from my HTC One X using xda app-developers app

XxVcVxX said:
You need to relock bootloader.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
And you need to install the Stock Recovery, for 1.29 ROM, link is provided in this thread http://forum.xda-developers.com/showthread.php?t=1594819

you cant downgrade ruu

Now I'm stuck in a loop between power up and hboot.
The phone says "Re-Locked" and won't load the ROM.
Oh the thread I was speaking of is : /showthread.php?t=1562603
Could someone explain me the steps I should make.
for example download this, update this, install this then this, rom and voila.
I'm totally lost here.

tomascus said:
you cant downgrade ruu
Click to expand...
Click to collapse
Now I see, you have 2.17 already, so you have to flash 2.17 minimal.
Btw. strange that you still have hboot 0.43 and a 2.17 base?
You cannot flash the 1.29, so you have to flash:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
So, you have relocked
Edit: You could try to RUN the RUU when device is in Fastboot without going back to stock recovery, cause it's in the RUU, but if that doesn't work... follow next steps.
Btw. Goto fastboot while unplugged and plugin usb cable after entered fastboot, you should see usb appear.
1. Next you need Stock Recovery:
for stock recovery you could run the above RUU, after you donwloaded it, but not install it.
After you run the RUU, it unpacks to the following directory:
C:\Users\[username]\AppData\Local\Temp\{some guid}\{some other guid}\
Get the rom.zip form that directory and in there you can find the Stock Recovery
You can flash recovery through Fastboot using the following command:
fastboot flash recovery [name of the retrieved recovery].img (you need to place it in the fastboot folder.
2. If you have Stock Recovery, Go into Fastboot mode and flash the RUU (2.17).
Something resources:
RUU collection: http://forum.xda-developers.com/showthread.php?t=1543604
Goto Stock Guide: http://forum.xda-developers.com/showthread.php?t=1859714

[Q] Bricked One X (Black screen with silver htc logo)

I have searching for a solution here for last 2 days but couldn't find one
Problem :
My one x is displaying black screen with silver "htc" logo. It does not boot in bootloader or recovery. Although fastboot commands are still running on this blackscreen.
What I did
I successfully unlocked my one x and installed paranoiandroid but when I started using it my phone began to hang and the touch was disable.
Then I read the post for getting bavk to stock using RUU. I followed these step.
- checked my phone version using "fastboot getvar version-main"
- downloaded "RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed"
- unlocked the bootloader "fastboot oem lock"
- Ran the RUU exe file.
Now the RUU is giving an error the RUU is not correct but it is the same version which I get from "fastboot getvar version-main" and now my phone is only displaying the black screen with sliver "htc" logo.
I shall be grateful if someone can provide a solution to my problem. Thank you.

try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.

tomascus said:
try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply.
I have tried it. The command executes but the phone again boots in blackscreen with silver "htc" logo. It is not going in bootloader.

If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?

ckpv5 said:
If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?
Click to expand...
Click to collapse
Yes it is giving the same version and I have downloaded the exact RUU version still RUU fails to complete its setup stating "not correct RUU, download the correct file"

I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?

sherwaniusman said:
I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?
Click to expand...
Click to collapse
Good luck! :laugh:

tomascus said:
Good luck! :laugh:
Click to expand...
Click to collapse
No luck same error occurred.

Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium

serwan said:
Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image

I think you should reinstall the HBoot manually...
What CID do you have?
Is your Bootloader "relocked" ??

andyoso said:
I think you should reinstall the HBoot manually...
What CID do you have?
Click to expand...
Click to collapse
How to reinstall the Hboot?

sherwaniusman said:
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image
Click to expand...
Click to collapse
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium

sherwaniusman said:
How to reinstall the Hboot?
Click to expand...
Click to collapse
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command twice:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse

andyoso said:
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command:
Click to expand...
Click to collapse
Thank you. My cidread returns HTC_044. Also I have logged into bootloader screen again. I just ran the Unlock_bin file I received during rooting my device and now my phone isn't displaying the black screen and finally entered bootloader.
The problem I figured out was my bootloader was relocked and my RUU setup failed, so I had a custom rom installed with locked bootloader. That's why the phone was bricked I wan't entering bootloader.
Now I can access my recovery as well.

serwan said:
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You don't need to extract anything from the ruu, if you have the right ruu just lock the bootloader and leave the phone there ... Start the ruu from pc with admin rights.....

Im speakung from my experiance. I have face this problem before. RUU program cant install the rom. So i have to flash everything extracted from RUU first. Only after that the RUU can install the rom. But maybe im just got lucky though.
Sent from my HTC One X using xda premium

[Q] Error 191 when using RUU - Rom not supported

G'day Guys,
I am trying to root my desire HD. currently 2.3.5
I initially followed the HTCDEV method
For my phone which downloaded the RUU program. PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe
this is for Desire HD Vodaphone australia.
I ran the RUU successfully once. It supposedly upgraded the image from 2.12.178.2 to 3.13.0.0
apon rebooting into the fastboot screen as per the HTCDEV instructions when attempting to fastboot I recieved errors saying
"no image or wrong image" or something to that effect.
at this point I went back to the drawing board and tried the HOW TO ROOT WITHOUT HACK KIT thread (http://forum.xda-developers.com/showthread.php?t=2168500) method and script for unlocking the bootloader. which downloaded the same RUU program
apon running it this time it still wished to updrade from 2.12.178.2 to 3.13.0.0 and i recieved the error
ERROR [191]: Rom is not supported
I have searched several threads with this error however none of them seemed to have a solution ie.
http://forum.xda-developers.com/showthread.php?t=2264987
I cannot locate and temporary ROM zips as per this thread below.
http://forum.xda-developers.com/showthread.php?p=21231962
EDIT Just found and am re-naming the rom zip as PD98IMG.zip then copying it to sd card root folder.
will update thread with result. apologies again
Appologies for the first thread question and its length.
Any help would be much appreciated.
Thanks and Regards
Ben

So I renamed the rom.zip file copied it to the root folder of the SD card.
booted into fast boot. updated
it said "parsing bootloader complete"
however the phone still appears to be 3.12.178.2 ...
the next step
step 8
htcdev[dotcom]/bootloader/unlock-instructions/page-3
"fastboot oem get_identifier_token"
wont run as it sits there <waiting for device>
if I run the RUU again it still says need to update to 3.13 and that its error 191 invalid rom.
help guys

slickncghia said:
G'day Guys,
I am trying to root my desire HD. currently 2.3.5
I initially followed the HTCDEV method
For my phone which downloaded the RUU program. PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe
this is for Desire HD Vodaphone australia.
I ran the RUU successfully once. It supposedly upgraded the image from 2.12.178.2 to 3.13.0.0
apon rebooting into the fastboot screen as per the HTCDEV instructions when attempting to fastboot I recieved errors saying
"no image or wrong image" or something to that effect.
at this point I went back to the drawing board and tried the HOW TO ROOT WITHOUT HACK KIT thread (http://forum.xda-developers.com/showthread.php?t=2168500) method and script for unlocking the bootloader. which downloaded the same RUU program
apon running it this time it still wished to updrade from 2.12.178.2 to 3.13.0.0 and i recieved the error
ERROR [191]: Rom is not supported
I have searched several threads with this error however none of them seemed to have a solution ie.
http://forum.xda-developers.com/showthread.php?t=2264987
I cannot locate and temporary ROM zips as per this thread below.
http://forum.xda-developers.com/showthread.php?p=21231962
EDIT Just found and am re-naming the rom zip as PD98IMG.zip then copying it to sd card root folder.
will update thread with result. apologies again
Appologies for the first thread question and its length.
Any help would be much appreciated.
Thanks and Regards
Ben
Click to expand...
Click to collapse
The top part, the one where you say RUU, that's not a RUU, that just simply updates the HBOOT.
You need to follow this guide.

Steam. said:
The top part, the one where you say RUU, that's not a RUU, that just simply updates the HBOOT.
You need to follow this guide.
Click to expand...
Click to collapse
thanks, yeah i was following that guide.
part of that guide is the "unlock bootloader" portion. I believed thats what the RUU was doing... as those were the steps i was doing.
I was trying to unlock to bootloader. which the guide states you need to do IOT continue on to the ROM steps in the guide you linked.
has anyone had success unlocking the bootloader or any ideas for my issue
thanks for the response. makes sure im on the right path,
Cheers
Ben

slickncghia said:
thanks, yeah i was following that guide.
part of that guide is the "unlock bootloader" portion. I believed thats what the RUU was doing... as those were the steps i was doing.
I was trying to unlock to bootloader. which the guide states you need to do IOT continue on to the ROM steps in the guide you linked.
has anyone had success unlocking the bootloader or any ideas for my issue
thanks for the response. makes sure im on the right path,
Cheers
Ben
Click to expand...
Click to collapse
Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader.
Sent from my GT-N7100 using xda app-developers app

glevitan said:
Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Ok im ready to do this. got my CID... however it appears the Revskills goldcard generator is down and has been for a while
does anyone know of a current goldcard generator that is working.
EDIT:
ok its Alice down the rabbit hole at the moment.
I think I have created a gold card using this tool ... that you posted lol
http://forum.xda-developers.com/showthread.php?t=2288012
there are allot of threads asking for goldcards so hopefully this helps someone.
now i just have to work out how to ... Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader. lol

apologies for the n00bage.
now I have a gold card. just trying to work out the next step to find a RUU that will support hboot update on htcdev
can anyone point me to an appropriate RUU? Glevitan perhaps?
thanks all for the help so far its been great

FYI I completed step 1 from this site http://forum.gsmhosting.com/vbb/f66...-os-s-off-change-imei-cid-hxc-dongle-1548982/
1.root ur phone :for root u mus unlock boot loader with htcdev/bootloader
hboot 2.00.0029 support token key for unlock bl 2.00.0027 stok not support
u must update hboot to 2.00.0029:
download this rom copy to your c:\ drive so download this dhd update hboot by behtash.rar
and run hboot update by behtash.bat in normal mode ,waiting until flash hboot complete
ok u can now unlock bl with htcdev.com\bootloader
however it would not unlock on htcdev it just sat there saying [waiting for device]
I think my fastboot program may be the issue due to it being the same 69k version that this chap had an issue with
http://androidforums.com/cdma-evo-3d-all-things-root/476366-help-w-htcdev-waiting-device.html
downloading sdk
MY current stats are
hboot-2.00.0029
radio-26.14.04.28_m
android 2.3.5
htc sense 3.0
software version 3.12.178.2

slickncghia said:
apologies for the n00bage.
now I have a gold card. just trying to work out the next step to find a RUU that will support hboot update on htcdev
can anyone point me to an appropriate RUU? Glevitan perhaps?
thanks all for the help so far its been great
Click to expand...
Click to collapse
Find what build version and main you are running by using the command in fastboot USB:
fastboot getvar all
Delete the IMEI and paste the outcome
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

glevitan said:
Find what build version and main you are running by using the command in fastboot USB:
fastboot getvar all
Delete the IMEI and paste the outcome
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I was being a numpty and didnt have sdk installed. I have to crash tonight but will install it tomorrow. then try htcdev again,
if it dosent work i will do as suggested. if its something that simple I will feel a bit stupid. will keep you guys updated.
thanks again all for your help

Ok I have unlocked bootloader. I was being a bit of a numpty and not doing the "get identifier token" command whilst the phone was actually on fastboot... the htcdev instructions confused me.
I will keep this post open as I know i will have more problems as I go.
Thanks all for your help so far
do i have to
3. Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/show...t=rooted+stock )
copy the ROM zip file to your SD card.
as per http://forum.xda-developers.com/showthread.php?t=2221039
or can I go straight to download a newer rom. a 4.2 or something and continue on the process

Ok, where I am at.
I have flashed the stock rooted rom as per the guide.
it works fine and has root access.
I didnt go through the process for S-OFF from step 6 onwards as I got a little lost what i needed to do as I had already done some of the goldcard steps. either way.
I am currently unlocked and rooted. with 2.3.5 stock rooted rom.
I tried to install a cryogenmod rom and jellytime rom.
as per this page http://forum.xda-developers.com/showthread.php?t=1866122
I installed them from the cwm recovery then tried to "flashboot flash boot boot.img" with their respective boot.img.
both roms didnt progress past the htc boot screen they just black screened.
can anyone hint why these roms wouldnt load? is it an s-on issue? or am i lost with the boot.img or missing another step?
i have reloaded the stock rooted image using cwm and flashboot flash boot boot.img
Thanks all
Ben

The command is "fastboot," not flashboot." Are there any errors when you run it?

bananagranola said:
The command is "fastboot," not flashboot." Are there any errors when you run it?
Click to expand...
Click to collapse
Yeah fastboot was what I was using . Typo sorry. Still not working. Should they work whilst using this method?

slickncghia said:
Yeah fastboot was what I was using . Typo sorry. Still not working. Should they work whilst using this method?
Click to expand...
Click to collapse
Again, is there an error message?

bananagranola said:
Again, is there an error message?
Click to expand...
Click to collapse
Ah appologies I am blind today.
No error msgs. Boot.IMG is coppied over as it is when I do it with the rooted stock Rom.
Just when rebooting afterwards. The phone does its .HTC flash screen for like 30 secs then it goes to a black screen (phone on) indefinitely.
The process I am using is
1 zip Rom on sdcard.
2 cwm delete user data
3 cwm install zip image from sdcard which works
4 reboot
5 fastboot USB
6 from pc: fastboot flash boot boot.IMG (extracted from Rom zip)
Am I doing anything incorrectly or missing a step.
Rooted, unlocked bootloader s-on
Thanks all

Is the phone in fastboot? What ROM? What recovery version?

bananagranola said:
Is the phone in fastboot? What ROM? What recovery version?
Click to expand...
Click to collapse
The phone was in fastboot USB
The working Rom is the one listed shoved from the full root sticky..3.12.405.1 rooted by nitr00
The 2 Roms that failed were jellytime and cryogen. Either the current or most recent stable apparently
Recovery is cwm. It's a slightly older version I think though. It was the only one I could find at the time.
Maybe 2. Something. I'll reboot now and check. Could that be an issue?

Bootloader unlocked
Hboot 2.00.0029
Radio 26.14.04.28m
Cwm recovery v 2.5.1.2

Yay just tried with the latest version of CWM and it works... FFS why wouldnt I have used the current version.
anyway I am playing with 4.2.2 jelly time now.
Thanks so much every contributor. your replies helped me keep going.