Develop Bugs

Can't pass HTC screen

Guys i have a question regarding the htc splash screen. I rooted twice today just to test a few things.
When i rooted for the first time i used windows 7 + hboot drivers from unrevoked3 site and flashed/rooted my device (stock rom (froyo)). Everything worked fine but when i run clockwork recovery mode and select the backup option i get something strange.
My device is backing up and it says it's done, when i select the reboot option my device get stuck at the splash screen and reboots, hangs, reboots, hangs, reboots etc. I need to pull the batteries off to get back in recovery mode. This time i select restore and select the backup i created before all this happend. Now it's passing the htc splash screen.
Because i thought i got problems with the windows drivers i decided to root with linux, so i installed the official ruu update over my rooted rom and root it under linux to make sure i am a bit saver.
Now when i do a backup and reboot again i get the same thing ? it hangs at the splash screen. Is the unrevoked recovery tool bugged (clockworkmod) ??? because when i restore with the backup i created it is passing the htc splash screen again.
I don't understand.
(Sorry for my bad English)
PS: I used this rom to root. http://forum.xda-developers.com/showthread.php?t=828519

As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone..nt sure though..wait for a reply from someone who is experienced..i hav been using android since past 3 months only
Sent from my HTC Desire using Tapatalk

What you could try is this.
Use unrevoked again, but in unrevoked select a alternative recovery image.
Then load this image http://forum.xda-developers.com/showthread.php?t=839621
This is the amon-ra recovery. And for the record, you can root with unrevoked as many times as you want
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes

Oo..i thght it is similiar to jail breaking tht needs to be done onl once...lolzz
Sent from my HTC Desire using Tapatalk

lordvoldemort said:
As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone
Click to expand...
Click to collapse
You really didnt read well didnt you ? it already happend the first time i rooted . Secondly, if i root and install a official ruu update over it everything will get wiped and cleaned....so there would be no problems when i decide to root.
Lennyz1988 said:
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes
Click to expand...
Click to collapse
Yeah i am sure....after backup the phone showed me the menu screen that i could select options such as rebooting the phone. When i reboot after backup it doesnt get passed the splash screen and reboots (and those steps gets repeated). If i don't use recover....my phone is dead

- Flash a stock ruu (rom)
- Then root again and use amon ra.

Lennyz1988 said:
- Flash a stock ruu (rom)
- Then root again and use amon ra.
Click to expand...
Click to collapse
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.

MichelN said:
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.
Click to expand...
Click to collapse
This seems to be a documented problem with Unrevoked. The first reboot after rooting and backing up Nandroid seems to hang the system for some, and restoring the Nandroid fixes it. After restoring the Nandroid (as you did) there should be no further problems. And since you did that, your problem should have been fixed. And since you restored to a rooted copy, why did you have to try again with Linux? Your problem was already fixed by the Nandroid Restore..

unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead

EddyOS said:
unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead
Click to expand...
Click to collapse
Thought the 1st Nandroid Restore fixes it..Does Clockwork mod still pose probs?

Clockwork Mod is the issue - flash AmonRA from the start and you won't have this issue (or I never have anyway, use AmonRA as you can partition SD cards in it)

I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...

protuger said:
I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...
Click to expand...
Click to collapse
I didn't have 2 black lines, mine rebooted after it couldnt pass HTC splash...i needed to remove battery or it keeps rebooting.
What i did with clockworkmod is restore (the backup you created before rebooting)....this should fix the problem. If this is not the case then i don't know because i never rooted before. You should ask a expert.
Anyway because i needed to restore anytime i posted this topic, people said i should use AmonRA. So to do this i installed the latest official ruu (posted by EddyOS) (to make sure everything is clean and good again). Then i used linux to make sure it is saver.
When you downloaded the unrevoked3 tool open it and don't plug you phone yet, go to options and select custom recovery. Now select the AmonRA (latest version i used) to flash with unrevoked3. Now plug in your phone and relax.
The only thing i am scared off is to flash hboot to go s-off.

Actually the cause of this problem was when i have tried the method for s-off...sad...

When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.

protuger said:
When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.
Click to expand...
Click to collapse
Try flashing true Linux. Download Ubuntu and this way you can boot your pc in linux.

Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.

protuger said:
Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.
Click to expand...
Click to collapse
You need root rights in ubuntu, use google to find it

thanks hope google stops my sleepless nights...

Stuck on boot screen! Help!

Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible

Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<

enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.

Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?

I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.

Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.

Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.

Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?

sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.

Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5

Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.

as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo

Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help

erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?

encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.

sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?

oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X

encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?

Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what

Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.

[Q] Bootloop help

I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!

Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?

oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!

whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.

HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App

I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App

Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.

HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App

Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App

Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!

Desire boot loops and I can't get into recovery

I've been happily running CM7 for the past year and yesterday while I was browsing the phone suddenly turned off and starts bootlooping, I then tried to get into recovery to flash one of my backups but I couldn't get into recovery anymore. I can get into the bootloader (vol down, back and power key) but if I select recovery from the menu it starts bootlooping again. I was hoping someone knows what's going on.
I used revolutionary to root the phone, had clockworkmod recovery installed (don't think it was the latest version, haven't updated it since I've installed it a year ago) and was running CM7.2 (latests stable version).
I also apologise in advance because you guys must be sick of people asking what to do with a 'bricked' phone but I'm still hoping someone can help me.

You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders

nlooooo said:
You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.

the catfishman said:
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.
Click to expand...
Click to collapse
Not sure what link you said is dead, they all work. I meant on this one "Before Crying for Bricked Device - How Nexus One and HTC Work ".
All you need is recovery.img download it from here:
http://www.clockworkmod.com/rommanager/
and flash it via fastboot.

Both your ROM and recovery are bootlooping. But importantly your bootloader is fine and therefore you can easily recover. First get your recovery in order by flashing recovery from fastboot. Thereafter when you are able to get into recovery flash your ROM in the normal manner or restore your nandroid.

Thank you both! I flashed the recovery.img and could get into the recovery mode again! it's restoring my last back up as we speak, so hopefully it's working again.

If it all work go here:
www.4ext.net
and get rid of that buggy cwm recovery.

Well.. today it started bootlooping again in the same way as described in the first post and now the method I used yesterday to fix it doesn't work anymore. If I flash a new recovery.img now and subsequently try to go into the recovery mode it starts bootlooping again... so now I'm wondering if I should just flash the RUU via pc to at least get my phone working again... do you guys think that would work?
edit: can I even run the RUU in fastboot usb?

RUU is the solution if all else fails. But only use 2.3 Android RUU. And remember to downgrade hboot first.
Before you get into that I would try :-
- Flash a different recovery and try to get into recovery. But this time dont restore your nandroid. Flash a ROM afresh.
- Remove your sdcard and try to get into recovery. Wild guess !
- Also try formatting your system, sdext etc partitions as given in Bortaks thread.

I tried flashing a different recovery (amon ra) but that also didn't work, when I tried to get into recovery mode it got stuck on the HTC boot screen (with some weird extra lines through the image).
I will try to remove the sd card.
Another weird observation, the phone doesn't seem to be charging anymore, at least... the led doesn't turn on when it's plugged in.. it get's weirder and weirder.

like handy says full wipe, wipe/factory reset, wipe dalvik and format all partitions except sdcard then do a clean install of a different rom. restoring the nandroid, u could just be restoring the problem.
edit: just read ur post bout charging, looks like HW not rom or recovery problems
Sent from my HTC Desire

yeah but the weird thing is that this started this morning, I charged it last night (when all of this stuff was already happening).

Run 2.3 ruu as fast as you can, you're on a good way to hboot or radio brick.
:banghead: constuction material guaranteed...
Sent from my HTC Desire using Flashes and Thunders

Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.

the catfishman said:
Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.
Click to expand...
Click to collapse
You can easily go s-off and root now just go here:
www.revolutionary.io
And the rest is history...
Sent from my HTC Desire using Flashes and Thunders

yeah, I will probably do that in a few weeks, I just moved to another country 2 days ago so I kinda need a functional phone these weeks... aand.. thanks for the help guys

[Q] can't boot into CM , can't update bootloader

I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance

You're in the wrong forum, this is the HTC One XL/at&t One X forum. I'll ask for this to be moved to the correct device forum for you.
Sent from my Evita

your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904

nogotaclue said:
your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
omg, i feel so stupid that i did this.. thank you very much! i now flashed TWRP and it worked, I'm waiting till the battery charges and i'll install CM again, but looks like it gonna work this time.
thanks again, that link was really helpful.:good:

Ok, don't forget to use the right cm, not the version you used previously
Sent from my HTC One X using XDA Premium 4 mobile app

xulube said:
I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance
Click to expand...
Click to collapse
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.

okhughes said:
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.
Click to expand...
Click to collapse
he doesn't need to start from scratch, he knows how to do it. the problem was he was in the wrong forum. did you even read the thread?