Database Info

[Q] Install Custom Rom without installing to SD?

As my post suggest I want to know if there is a way to install a custom rom on my Tmobile HTC ONE S without moving it to SD. I messed up and ended up deleting the current rom I had on it. I have unlocked the bootloader, and I previously had Zydroid v3.5. Currently I am able to use CWM on it but there is no data on the SD that I can use. Thanks you.

mgkamiolo said:
As my post suggest I want to know if there is a way to install a custom rom on my Tmobile HTC ONE S without moving it to SD. I messed up and ended up deleting the current rom I had on it. I have unlocked the bootloader, and I previously had Zydroid v3.5. Currently I am able to use CWM on it but there is no data on the SD that I can use. Thanks you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1667929

Yea, that's my way of doing it. It pushes it from your computer to your SD Card so you can flash it in CWM from there.
If you have no /data/ on your SD Card, that's ok. I did the same thing. Once you get a ROM installed and working, you'll be fine.

brwetz said:
Yea, that's my way of doing it. It pushes it from your computer to your SD Card so you can flash it in CWM from there.
If you have no /data/ on your SD Card, that's ok. I did the same thing. Once you get a ROM installed and working, you'll be fine.
Click to expand...
Click to collapse
I have spent the last 7 hours just trying to look through all threads to try to address this issue. Right now I am unable to send any zip file to my device through ADB. However by using the recovery tool in the ALL in One kit utility I can send a touch recovery .img file to my HTC One S. At first it shows error: could not find device but then the next line pushes that file with no issues.

mgkamiolo said:
I have spent the last 7 hours just trying to look through all threads to try to address this issue. Right now I am unable to send any zip file to my device through ADB. However by using the recovery tool in the ALL in One kit utility I can send a touch recovery .img file to my HTC One S. At first it shows error: could not find device but then the next line pushes that file with no issues.
Click to expand...
Click to collapse
Does ADB see your device?
what happen when you type in
Code:
adb devices

If this stuff is too complicated for u and u have messed up ya phone just run the ruu specific to ur phone and ull be back to normal but u will have to unlock flash and root again
Sent from my HTC One S using xda premium

Thanks for the replys. I acutally got ADB to work by using the mount feature in TWRP recovery tool. However now any custom rom I run will only crash and get stuck in continous boot cycle if I try to activate wifi. This whole issue started when my stock phone got an update two days ago, and it completely messed up my wifi. I should of waited and taken it to the T-mobile store but now its too late. I have unlocked, rooted and put a custom rom on it. I tried using the RUU file to go to 1.53 but i keep getting 155 unknown exception error. For now I will just have to use my phone without wifi till I have more time to look into this wifi issue.

U get the error cuz ur not using the right ruu for ur phone of ur Europe I can send u the ruu for ur phone
Sent from my HTC One S using xda premium

I am currently using RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
I have a Tmobile HTC ONE S phone, and when i had stock it was on 1.84 or so. I think I can't use 1.5 without modding some other files.

Tried using the 1.84 RUU?
Sent from my HTC One S using xda premium

Conflicting RUUs...try the 1.84 and (if you want) root it again afterwards. Glad you got adb working.

brwetz said:
Conflicting RUUs...try the 1.84 and (if you want) root it again afterwards. Glad you got adb working.
Click to expand...
Click to collapse
Unable to locate 1.84 RUU, but I heard that a user named "football" has it but requires a donation. The next best step I think is to try a rooted Nanorid of 1.84 that I found in
http://forum.xda-developers.com/showthread.php?t=1698861&page=4. Ill try this when I have more time. Right now using Zydroid 3.5 rom which works fine except for my wifi. Loading my wifi will crash my phone and put me in a crazy boot cycle.

Alright so I have use a 1.84 rooted backup and successfuly installed it on to my phone. However I still have my wifi issue, also my blue tooth does not work. I also loaded the boot.img file from the backup through fastboot but still having the same error.

I flashed different radios, tried nanoroid backup of 1.84, but wifi does not work. Wifi stopped working while I was still on stock rom. In the end I paid 20 bucks for tmobile to ship me a new phone, hopefully I wont have issues and I will stay on stock rom.

mgkamiolo said:
I flashed different radios, tried nanoroid backup of 1.84, but wifi does not work. Wifi stopped working while I was still on stock rom. In the end I paid 20 bucks for tmobile to ship me a new phone, hopefully I wont have issues and I will stay on stock rom.
Click to expand...
Click to collapse
When you sent it back you went back to RUU and locked bootloader, etc?

I haven't sent it back yet, I will be getting my new HTC ONE S in the mail in two days, and then I can ship my old phone back. Right now my phone is on a nanoroid back up of 1.84 stock rom with root. I tried going back to 1.53 but we dont have S-off so unable to do it. If i try to do that i get 155 unknown error in the RUU launcher. The t-mobile techs didnt know that my phone is rooted cause it basically is the stock rom. I have relocked the phone and I hope that the real techs dont notice that I unlocked the bootloader and it that its still rooted.

Im cancelling my order, some how my wifi works now. Yesterday I did a wifi radio install from europe, but it didnt seem to work. I also relocked the system and rebooted couple of times, this may have helped solve the issue as well.

HTC Thunderbolt Issues - Stuck at HTC Logo... Recovery not working, etc...

here is my issue.
2 weeks ago, i rooted my phone. all was well. flashed CWM Recovery 5.0.2.1 for my Thunderbolt. I made a backup just before i rooted so that in case ANYTHING went wrong, it would unroot me and fix any problems. So, here i am, backing up apps with Titanium Backup, and it backed up fine. The next thing i did was start to uninstall HTC Bloatware... I knew which ones were the ones i could remove, plus even if i removed the wrong one, i could just restore using my image backup. After removal, the phone instantly ran better. i had over 65% free memory space... This was all well and good, until i rebooted the phone. the instant i rebooted my phone, i was getting the flashing HTC Quietly Brilliant screen. i had done NOTHING to it to cause this. It would alternate from HTC splash to Thunderbolt animation.
So, knowing what was wrong, (UI not loading) i went to recover my image from CWM. that went fine. but things just got worse. After a successful recovery (according to CWM) i rebooted, but to my surprise, now its worse. its stuck at the HTC boot logo. ALL MANNER OF ROMS DO NOT WORK!!! recoveries, new OS, anything, all the same result. AT LEAST with the thunderstick full blown ROM, i can get back to the looping splash screen, but not any further. i DONT KNOW what is wrong but i am hoping one of you mad phone geniuses out there can get my phone working. i tried getting s-off with revolutionary, but it failed because the phone has to be booted up for it to work, and is something i obviously cant do at this point... relocking the phone made things worse too because i unlocked using the HTCdev method.
This is not a boot loop, as it doesnt loop. it just sits there. i have tried every available resource on this, and other sites. i must have read over 1,000 posts in the past week to try and gather what the devil happened to my phone... If its any help, i did accidently delete the settings storage APK file, but a restore should have fixed that. i want to lock up the phone to send it in for repair but i cant gain s-off to flash a new radio with the phone in its current state. i know how to do all if these things but the phone wont let me.

Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium

Does your computer recognize your device?
Sent from my ADR6400L using xda app-developers app

i am nearly pulling my hair out...
smtom said:
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...

cyberkeeper1 said:
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
Click to expand...
Click to collapse
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2

will this really work??!? lol
trter10 said:
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
Click to expand...
Click to collapse
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.

new problem... i think...
cyberkeeper1 said:
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
Click to expand...
Click to collapse
ok. so the download finished fine so far as i know, but now CWM says ITS bad too. i will try again but i cant seem to flash any stock rom no matter if its OTA or pre-OTA from CWM. is there a way to flash a rom from the PC via adb or something?

Ohh! They're not flashed through CWM. They're flashed through hboot. Just rename it to PG05IMG.zip and put on SD card and boot to hboot it will ask you to flash
Sent from my ADR6400L using Tapatalk 2

i will try that. previous hboot flashes always fail. it reads the archive, but never goes to "checking zip". it loads, checks, and then parses. i was successful with my evo shift earlier today, but that thing is ancient compared to my thunderbolt. With the Shift, i was able to gain root AND s-off with an old bootloader and i dont even need a new one.
i wanted to do the same with my bootloader in case another disaster hits because then i can flash whatever RUU i want with s-off. i will make sure the MD5 SUM matches before flashing. i forgot to do that anyhow.

Hboot flash failed. went through the motions of scanning it and it scanned the whole thing and then did nothing. it returned me to Boot Choices. Like Fastboot, recovery, etc... i tried twice. are you absolutely certain that is the shipping firmware that formats the entire phone, and not just updates it? i cant send it to verizon even though they know it was illegal to lock up my phone... Anyhow, i realy need this thing working and i have racked my brain enough to damage it already... lol. if it fails again i will try to redownload it. So far it loads and does NOT ask me to start the update. could be a version issue because it does not complain about anything else.

Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app

lemew said:
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
yes i have. i cannot do what it asks because it requires my phone to be functional to flash it using hboot. i need a signed copy of an older RUU. hboot doesnt do anything with it. its a valid copy, and i can see all the images and contents in windows and linux, but all i can get hboot to do is read it, then it doesnt ask me to update. i dont know what to do now.

I believe there is a ruu image without hoot download there.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
Try http://shipped-roms.com/index.php?category=android&model=Mecha
Sent from my ADR6400L using xda app-developers app

ok well i will literally try ALL of the signed images. i will see if hboot will update it.

If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app

How i fixed my tbolt stuck at the white HTC screen
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.

mpcapps said:
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
Click to expand...
Click to collapse
I have read that post you provided probably 100 times its not working for me. flashing a custom rom actually got me past the HTC white screen and into a splash screen loop (Open Mobile). Also, I havent even been able to use the REV tool because my phone is not recognized by it without it being fully functional. you have to be fully booted up for the REV tool to use adb and start the process. thats why i need a signed copy of an older ROM with hboot flashing capability so i can fully restore my phone. i am 100% sure its a corruption issue, but i am out of clues as to how to actually get it to flash over while being s-on. with the evo shift it worked perfectly. it only took me 20 minutes to root, s-off and flash a custom rom. this phone has been a thorn in my side ever since i accepted that STUPID FOTA... i regret not knowing before hand what that OTA was and what it prevented. Now i know, too little / too late.
without s-off, i cant unlock hboot to flash it, and the fastboot mw whatever command failed also because its locked tight.

lemew said:
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thats what i thought. is there a way to change out that eMMC, or remove it to format it manually? i mean based on the description, its technically external which implies removable.

Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app

lemew said:
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
too bad i cannot repartition it to allow for more RAM instead of app space. i dont care about app space because i have a 32gb card... lol. i just want that phone to be faster than what it is currently once i finally get it running.

bricked one x

So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX

tae_254 said:
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
so from mounting
im trying to install the Android Revolution HD 9.7.2 Ice Cream Sandwich
it allows me to choose settings, and such and start install.
after starting install, it goes through the files and such, but when it gets to /system/lib/ it just closes on itself, and goes back to twrp screen and recovery home. the rom never finishes installing. right now im gonna re-download the rom and see if that works.
if i cannot install the custom rom, how can i go back to stock exactly?
do i need to find the stock ruu?

fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?

hopefully you aren't using cwm anymore and flashed twrp for the evita.

chinaman_chong said:
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942

CleanROM on Viper XL
---------- Post added at 12:14 PM ---------- Previous post was at 12:13 PM ----------
chinaman_chong said:
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
CleanROM or Viper XL

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
Click to expand...
Click to collapse
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:

Crappyvate said:
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Click to expand...
Click to collapse
I didn't even have to use the search function. 2 are near the top of General. The remaining has slipped past the first page, but its still pretty high up there.
People who flash a ROM for the international version are simply neglecting to do any basic reading and learning before flashing things willy-nilly, that's my point.

thanks for the help guys. i flashed viper xl yesterday night right after, loving it thus far. i was just so used to the sense keyboard already, and hated the cramped jb keyboard, and this rom has simple little tweaks
i did read, but i guess not thoroughly enough. in hindsight, i wasnt aware that the one x was different than the xl, its fairly easy to miss that the other roms are not compatible with this phone. and is completely different alltogether.
if i had known that, i wouldnt have flashed cwm, and would not have need to post a help thread. all "solutions" i attempted on my own were based off readings of the hox, rather than the evita, once again causing more problems. it was easily enough fixed once i figured that bit of information out.
i am a noob, but this phone is not my first time rooting, so with my prior knowledge i felt i was more than ready to tackle this rom flashing, im sure plenty of others will make the same mistake as i did.
the other phones ive rooted and flashed had their one model of phone only, so all the roms available were compatible.
im just glad my phone is not bricked, and i now have root access

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Do not use CMW it causes lot of problems(not recommended for our device) . Use TWRP recovery instead
Sent from my HTC One XL using xda premium

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Click to expand...
Click to collapse
That and Superwipe. I remember that zip from other phones I used that rom on.
Sent from my HTC One XL

Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Subscribe to the OneXL forums and stay here till you recognize your community!
Sent from my HTC One XL using xda app-developers app

can't brick from it after 2.20

DvineLord said:
can't brick from it after 2.20
Click to expand...
Click to collapse
Good thing eh
Sent from my HTC One XL using xda app-developers app

InflatedTitan said:
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Click to expand...
Click to collapse
From what others are saying, the newer hboot that came with 2.20 is write protected. Hboot can't be overwritten by flashing a ROM for the international One X. ROM just fails to flash, and you get a recoverable condition like this one, as opposed to hard bricks on the older hboot.

Yea, at least there's one good thing that came with the dreaded update
Sent from my HTC One XL using xda app-developers app

How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help

h1m said:
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
Click to expand...
Click to collapse
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu

omario8484 said:
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
Click to expand...
Click to collapse
Where do i get the ruu file? I can't mount my sdcard

Did I brick my Inspire 4G?

I'm sure I haven't bricked this phone, because in the process of rooting it, it will eventually say it's S-OFF. But after getting to that point, I can choose Recovery in CWM and when it gets to the white screen with the green HTC logo, after about 4 seconds, it will fade to black. This has happened to 2 phones I've rooted. Luckily mine worked like a charm, but after the last 2...I'm afraid to root another one. Does this sound like a bad memory card, or maybe it's not a gold card? I've searched around and couldn't find an answer, so maybe someone here at XDA has experienced this problem and has an answer.
TIA

t4duzan said:
I'm sure I haven't bricked this phone, because in the process of rooting it, it will eventually say it's S-OFF. But after getting to that point, I can choose Recovery in CWM and when it gets to the white screen with the green HTC logo, after about 4 seconds, it will fade to black. This has happened to 2 phones I've rooted. Luckily mine worked like a charm, but after the last 2...I'm afraid to root another one. Does this sound like a bad memory card, or maybe it's not a gold card? I've searched around and couldn't find an answer, so maybe someone here at XDA has experienced this problem and has an answer.
TIA
Click to expand...
Click to collapse
I quite don't get that....you can choose recovery in CWM?? what does that is supposed to mean? CWM is a custom recovery. I guess that you are probably refering to hboot. Anyway, if you are S-OFF, then you might not have a recovery installed, so flash a new one (use the guide in my signature or look for post # 7 in the Ace Think Tank in the general section of the Desire HD forum)
Make sure first that you are S-OFF for certain, if you are not, then you won't be able to flash anything at all. Then, try re running the Hack Kit again from the white splash screen as the manual tells you to.

glevitan said:
I quite don't get that....you can choose recovery in CWM?? what does that is supposed to mean? CWM is a custom recovery. I guess that you are probably refering to hboot. Anyway, if you are S-OFF, then you might not have a recovery installed, so flash a new one (use the guide in my signature or look for post # 7 in the Ace Think Tank in the general section of the Desire HD forum)
Make sure first that you are S-OFF for certain, if you are not, then you won't be able to flash anything at all. Then, try re running the Hack Kit again from the white splash screen as the manual tells you to.
Click to expand...
Click to collapse
Yes, I guess I did mean hboot. In the process of Recovery is when it will fail and there is a ROM loaded for it to recover from on the SD card. Is it possibly because it is looking for the clockworkmod/backup folder and there is not one? I just realized that maybe I can copy a backup from my phone (we have the same exact phone) and place in there if it's possible. I don't have access to the phone now, as it is a friends. Also, if it fades out at the white HTC logo and just gets hung up, there is no way to re-run the Hack Kit is there?
Thanks for the help glevitan, as you've helped me before and I HAVE downloaded your Ultimate Hack Guide and keep it on my phone for reference.

t4duzan said:
Yes, I guess I did mean hboot. In the process of Recovery is when it will fail and there is a ROM loaded for it to recover from on the SD card. Is it possibly because it is looking for the clockworkmod/backup folder and there is not one? I just realized that maybe I can copy a backup from my phone (we have the same exact phone) and place in there if it's possible. I don't have access to the phone now, as it is a friends. Also, if it fades out at the white HTC logo and just gets hung up, there is no way to re-run the Hack Kit is there?
Thanks for the help glevitan, as you've helped me before and I HAVE downloaded your Ultimate Hack Guide and keep it on my phone for reference.
Click to expand...
Click to collapse
Just a question, are you sure that the phone is S-OFF? or has an unlocked bootlaoder? In either way you can flash recovery again from fastboot and then a custom rom again.
If you need help, I can lend you a hand via teamviewer..just let me know. :good:

glevitan said:
Just a question, are you sure that the phone is S-OFF? or has an unlocked bootlaoder? In either way you can flash recovery again from fastboot and then a custom rom again.
If you need help, I can lend you a hand via teamviewer..just let me know. :good:
Click to expand...
Click to collapse
I'm going by after work to pick up the phone and will work on it this weekend. Thanks for the offer of help too. I'll post back with how this turns out.

t4duzan said:
I'm going by after work to pick up the phone and will work on it this weekend. Thanks for the offer of help too. I'll post back with how this turns out.
Click to expand...
Click to collapse
ok. Good luck!

Ok glevitan, I believe the problem might be in the PD98IMG.zip that's on the root of my SD card. I noticed when the phone booted into hboot, it would display that the image file was wrong, or something to that effect and then would force an update, which would load the HTC spashscreen and then ultimately fade out. I figured it had a bad PD98IMG.zip file, so I found the original aahk-13012012.zip and extracted the PD98IMG.zip from there and overwrote the one in the root. It didn't work. A different story...I noticed on my Inspire 4G (working correctly, but hboot had same error, even though I could load recovery from there) that it wasn't finding the correct image either. I copied over the PD98IMG.zip onto my phone and now both phones are now fading out on the HTC splashscreen after about 4 seconds. This tells me that it's in the SD card, right? If so, any suggestions? Both phones were rooted using this version of aahk.
Edit: Also, with this new PD98IMG.zip image, hboot will go into the process of parsing for
[1] boot
[2] recovery
[3] radio_v2
Once this is done, I push Power to reboot and that's when I get the failure in the HTC splashscreen.
Edit: I noticed in the PD98IMG.zip there was no md5 file, so I stuck one in there and got my phone working (which is not the one with the original issue started in this thread) and was able to restore a nandroid backup. I put this same SD card in the original damaged phone and it didn't restore like mine did. I still think it's an SD card issue causing the HTC splashscreen fadeout, but don't know where to go know.
Also, my PD98IMG.zip only has a recovery.img and a recovery.md5 file in it. I noticed that the original aahk PD98IMG.zip has those along with a boot.img and a radio.img. Should those be in the PD98IMG.zip? I know this post was edited twice and is very jumbled, so if you can make sense of it and offer solutions, much obliged.

t4duzan said:
Ok glevitan, I believe the problem might be in the PD98IMG.zip that's on the root of my SD card. I noticed when the phone booted into hboot, it would display that the image file was wrong, or something to that effect and then would force an update, which would load the HTC spashscreen and then ultimately fade out. I figured it had a bad PD98IMG.zip file, so I found the original aahk-13012012.zip and extracted the PD98IMG.zip from there and overwrote the one in the root. It didn't work. A different story...I noticed on my Inspire 4G (working correctly, but hboot had same error, even though I could load recovery from there) that it wasn't finding the correct image either. I copied over the PD98IMG.zip onto my phone and now both phones are now fading out on the HTC splashscreen after about 4 seconds. This tells me that it's in the SD card, right? If so, any suggestions? Both phones were rooted using this version of aahk.
Edit: Also, with this new PD98IMG.zip image, hboot will go into the process of parsing for
[1] boot
[2] recovery
[3] radio_v2
Once this is done, I push Power to reboot and that's when I get the failure in the HTC splashscreen.
Edit: I noticed in the PD98IMG.zip there was no md5 file, so I stuck one in there and got my phone working (which is not the one with the original issue started in this thread) and was able to restore a nandroid backup. I put this same SD card in the original damaged phone and it didn't restore like mine did. I still think it's an SD card issue causing the HTC splashscreen fadeout, but don't know where to go know.
Also, my PD98IMG.zip only has a recovery.img and a recovery.md5 file in it. I noticed that the original aahk PD98IMG.zip has those along with a boot.img and a radio.img. Should those be in the PD98IMG.zip? I know this post was edited twice and is very jumbled, so if you can make sense of it and offer solutions, much obliged.
Click to expand...
Click to collapse
Ok, I quite don't get much...sorry, but that version of the Hack Kit is old, so use the lastest one: http://tau.shadowchild.nl/attn1/?p=74
But again, I don't still get if the phone is S-OFF or not. If you are S-OFF there is no need to do all that process. Even, you can flash a RUU without using the PD98IMG way if you suspect that the sdcard is messed.
You can flash it over fastboot.... Anyway, you will have to flash this RUU (which is the gingerbread update 2.3.3 version of ATT. the lastest one, if you are not S-OFF will make things a bit harder for you to run the hack kit later): http://https://dl.dropbox.com/u/30674730/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
Put the phone in fastboot usb (when in hboot, plug the phone and it should read fastboot usb in red, if not, just press power button to toggle to fastboot). Then, just run that .exe file and it should flash...

glevitan said:
Ok, I quite don't get much...sorry, but that version of the Hack Kit is old, so use the lastest one: http://tau.shadowchild.nl/attn1/?p=74
But again, I don't still get if the phone is S-OFF or not. If you are S-OFF there is no need to do all that process. Even, you can flash a RUU without using the PD98IMG way if you suspect that the sdcard is messed.
You can flash it over fastboot.... Anyway, you will have to flash this RUU (which is the gingerbread update 2.3.3 version of ATT. the lastest one, if you are not S-OFF will make things a bit harder for you to run the hack kit later): http://https://dl.dropbox.com/u/30674730/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
Put the phone in fastboot usb (when in hboot, plug the phone and it should read fastboot usb in red, if not, just press power button to toggle to fastboot). Then, just run that .exe file and it should flash...
Click to expand...
Click to collapse
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.

t4duzan said:
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.
Click to expand...
Click to collapse
I was having a similar problem, I'm not too sure if it relates to what your experiencing. But I was trying to gain s-off my hboot was in fact unlocked but was still s-on. I was reading around and flashed a few boot.img with fast boot. I had that problem where htc screen would show then fade to black, and then stay black.
What I did was (I had installed recovery pretty early on) I did a factory reset in recovery then went to restore. Prior to this thank god I had transfered my nandroids to the pc b4 flashing new boot.img(s) then flashed the boot.img from the nandroid I just restored. All was well back into stock. I then found the insecure boot.img to use for aahk, flashed that in fastboot and relocked hboot. Reran aahk in linux. Got me to S-OFF with unlock.
If you need a fairly stock nandroid I can provide one.

t4duzan said:
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.
Click to expand...
Click to collapse
Ok, you need to reflash the RUU I posted above....you just need to flash that from fastboot usb. If you can't do it, Then you need to flash it manually. Just let me know and I can lend you a hand over teamviewer. When you get the phone back, then you run the hack kit.

glevitan said:
Ok, you need to reflash the RUU I posted above....you just need to flash that from fastboot usb. If you can't do it, Then you need to flash it manually. Just let me know and I can lend you a hand over teamviewer. When you get the phone back, then you run the hack kit.
Click to expand...
Click to collapse
glevitan, you're awesome. I restored the phone by running the RUU executable and reran the aahk and am now fully rooted. Both times I got the black screen on this phone previously was on the same PC, but this time I ran aahk on my PC and it ran correctly. I sincerely appreciate your help in helping me to achieve root for this phone. Hopefully this thread helps someone in the future.

Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app

jimmyport said:
Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
What have you tried? AAHK is the only real option. There is a very clear guide over at the Ace Think Tank post #7, linked in my signature.

jimmyport said:
Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Besides what bananagranola said, you need to know that video tutorials suck. They skip important details and that, will probably get you stuck. Read the guide adviced, and the hack kit site (got the link in the Ace Think Tank Thread)...that is all you need to know.

I have tryed the Aahk. My problem is when it ask me to downgrade ruu an all that. All my phone dose when I run the aahk I push 1 an then it ask too downgrade so i put y then something about the ruu an I put y then it says pushing the 9 something file. ( sorry I'm not home on my computer ) so I'm not 100% on what it is saying. But then my phone boots to Hboot dose its thank. Then says bad image. I have done this a lot of times with the aahk. I even tock the s-on off an on. Is there a way that someone can jump into my computer an do this?
Sent from my SGH-I777 using xda app-developers app
---------- Post added at 10:11 AM ---------- Previous post was at 10:03 AM ----------
I wish they would do a video an not skip anything at all. That would be really nice. I fill like there is stuff I'm missing. Dose anyone know off there heads what all needs too be downloade? I have the aahk an drivers. I did everything I been reading the fing manual. I have a ROM an gapps ready too go. Just need too root the phone so I can run the rom.
Sent from my SGH-I777 using xda app-developers app

jimmyport said:
I have tryed the Aahk. My problem is when it ask me to downgrade ruu an all that. All my phone dose when I run the aahk I push 1 an then it ask too downgrade so i put y then something about the ruu an I put y then it says pushing the 9 something file. ( sorry I'm not home on my computer ) so I'm not 100% on what it is saying. But then my phone boots to Hboot dose its thank. Then says bad image. I have done this a lot of times with the aahk. I even tock the s-on off an on. Is there a way that someone can jump into my computer an do this?
Sent from my SGH-I777 using xda app-developers app
---------- Post added at 10:11 AM ---------- Previous post was at 10:03 AM ----------
I wish they would do a video an not skip anything at all. That would be really nice. I fill like there is stuff I'm missing. Dose anyone know off there heads what all needs too be downloade? I have the aahk an drivers. I did everything I been reading the fing manual. I have a ROM an gapps ready too go. Just need too root the phone so I can run the rom.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Try using a different sdcard. If the RUU image is not being read, that is probably due to a bad sdcard. It is corrupted to work as a goldcard but fine for usual day use.

I have. I have had 4 of them now. Two 2 gigs one 36gig an one 8 gig. New I paid for them an a new USB cored fast data cable for the phone.
Sent from my SGH-I777 using xda app-developers app

jimmyport said:
I have. I have had 4 of them now. Two 2 gigs one 36gig an one 8 gig. New I paid for them an a new USB cored fast data cable for the phone.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
2gb is enough...don't use another cable but the oem one that came with the phone. Anyway, that seems to be a sdcard issue. Try with another one and then report back.

I will go buy one more. But I Dont thank its that. An why not use a fast data cored for my phone?
Sent from my SGH-I777 using xda app-developers app

[Q] AT&T HTC One X Soft Brick. Tried everything I could find. Suggestions?

So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita

timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.

I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita

Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.

Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita

roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?

timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.

No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita

roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.

I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.

Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?

Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?

For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.