Database Info

Help! I can't flash my beta Kaiser

Hi, I bought an unused Kaiser, but it's a beta testing model. It works fine, aside from a few small annoying hiccups. I tried to flash the rom using the instructions kindly provided on the Wiki. Hard SPL will not work. I get a connection error at the end everytime. I tried running the Factory Shipped ROM form HTC, but an error says that I can't flash using this. Has anyone come across this before? Any help would be greatly appreciated.

I didn't know this error but I think every body has get the unlock device using these files in attached.
I hope this will help you to solve this problem.
(Rename the files ".rar")
Ciao.

ribcage said:
Hi, I bought an unused Kaiser, but it's a beta testing model. It works fine, aside from a few small annoying hiccups. I tried to flash the rom using the instructions kindly provided on the Wiki. Hard SPL will not work. I get a connection error at the end everytime. I tried running the Factory Shipped ROM form HTC, but an error says that I can't flash using this. Has anyone come across this before? Any help would be greatly appreciated.
Click to expand...
Click to collapse
It makes sense to dump your beta SPL before you install hard-SPL
pmemdump 0x8c000000 0x40000 spl-beta.bin
(pmemdump is part of itsme's itsutils, do a search first)

I did a search for pmemdump, but nothing came up...

max.tytn said:
I didn't know this error but I think every body has get the unlock device using these files in attached.
I hope this will help you to solve this problem.
(Rename the files ".rar")
Ciao.
Click to expand...
Click to collapse
I tried the files, thanks for posting them. Still no joy. It just won't finish the sequence.

be careful...
Don't forget that you could ruin the device. Unless someone who knows what they're talking about says to do something, I would consider using the device as is or maybe asking HTC direct (even though that might be of zero help)

yi3o8 said:
Don't forget that you could ruin the device. Unless someone who knows what they're talking about says to do something, I would consider using the device as is or maybe asking HTC direct (even though that might be of zero help)
Click to expand...
Click to collapse
Wise advice.
I think it was POF who posted the info for the Hermes pre-production units. Maybe wait until he reads this thread. I won't say pm him because I expect he gets thousands of personal requests for help.
This link (for info only) shows how HERMES pre-production units were flashed - basically using the SD card method. It might be worth trying SD card flashing (link here for Kaiser) - but the instructions need you to be hardSPL first.
Let us know if it works out ok.

Many thanks for the helpful responses and the sound warnings. I have contacted HTC directly, but they weren't very helpful. They sent me detailed instructions on how to "soft" and "hard" reset the device. I'll take your advice and let the thread run for a while. The unit is functioning well, with only minor annoyances. I'll certainly post the outcome, and again, thanks.

ribcage said:
I did a search for pmemdump, but nothing came up...
Click to expand...
Click to collapse
download itsutils here

yes please dump this...strange you are having problems flashing since most preproduction units are superSPL and arent locked in any sort of way...who did you buy this from who said it was a beta version?

Doug2873 said:
yes please dump this...strange you are having problems flashing since most preproduction units are superSPL and arent locked in any sort of way...who did you buy this from who said it was a beta version?
Click to expand...
Click to collapse
I bought the unit on ebay. The seller said it was a beta, but that it functioned perfectly. When it boots up, the opening screen says "IU BUILD TEST ONLY" over the HTC logo. It also said BETA at the botom right of the home screen, but KarhU helped me to get rid of that with reg edit. The unit does work well, but it's slightly unstable and a few functions, like word completion, don't work at all.

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/

Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work

thanks for sharing!

appreciate this very much!

thanks flipzmode....always a chance this could come in handy at some point

THANKS! was worried about having a with Google phone until now

thanks flipz

Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)

Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.

This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!

Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.

posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.

someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)

fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today

Thanks!
this saved my phone. I was about to throw it away.

USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.

nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")

Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

Rogers! Downgrade your device if you're stuck!

WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.

Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.

wow dat was quick, so downgrade and follow the rooting process again is it ?

Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?

What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?

Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome

dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???

dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?

ok update failed

dammm... was hoping for a fix!

Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....

I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e

weird, I have lost all the signal ever since trying to flash the nbh file

copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers

alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.

copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?

Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.

I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.

Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.

Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.

[Q] Explain (not with a HOWTO!) Goldcard, Bootloader, SPL, RUU, CID to me

Ok, so I'm not all that new to this rooting thing, I've rooted several HTC Magics, a Nexus One, helped out on a Legend, rooted a Hero and managed to install Android on an HTC Tytn II.
I'm getting used to the different terms about rooting and I'll recite them for you so you know where I'm at.
My Question/Request for you all is to help me figuring out what all these words mean and how they correspond/correlate/work together.
=== Things I have understood almost completely ===
Root
As in Linux, gives a user or script the permission to write to otherwise protected partitions and file systems of the handset.
Recovery
A partition(?) that manages some tasks involved with the basic building blocks of the system, such as installing/flashing different partitions/parts of the handset. Also has the ability to wipe the data-partition as well as Dalvik-cache.
Bootloader/HBOOT/SPL
A partition(?) that fires up the basic buildingblocks on the handset. Such as recovery, OS, and whatnot. With Fastboot-commands it's possible to flash partitions, as long as the bootloader allows remote writing through command-line.
=== Things I've almost completely understood ===
CID
CarrierID. This is when a mobile phone network carrier "locks" the phone to a specific network. But this also means that the carrier hands out updates to the Android-system installed on the handset? And the only way of updating a factory-state handset is by getting hold of updates from the carrier?
RUU
ROM Update Utility. Used by HTC to update their manufactured handsets. There might be other manufacturers who use this abbreviation, but I've seen it used almost exclusively in regards to HTC. There are checks being made when trying to install a RUU-package on the handset. These are/could be(?)
* Current RUU version already installed (if the RUU-package that is being installed is older, the installation quits)
* Current CID (If the CID in the RUU doesn't match the CID on the handset, the installation quits)
=== Things that confuse me ===
Goldcard
This is a modified SD card that supposedly bypasses the CID/RUU-check. Now, this to me sounds like I can install any RUU no matter what version I currently have installed on my handset and no matter what CID my handset came with.
This also sounds to me that I can potentially install a Desire RUU on my HTC Magic, if it is true that the RUU/CID-check is bypassed by the goldcard.
This also sounds to me that the requirement for a newer RUU-version of the package I'm installing is bypassed. For instance, I will, if I use a goldcard, be able to install a RUU-package with the version 1.28 on a handset that currently have version 1.31 installed?
Reverting a root
Is it as easy as grabbing the latest official RUU-update from HTC:s website and install that? Does it contain all the partitions and system-files necessary to restore the handset to a factory-state? Or will there be complications because of the root and different custom-ROM:s and custom-recoveries that are on the handset?

Shameless bump. SOMEONE has to know this. Or this is such common knowledge that there is a wikipedia article and I missed it?
If I only get an answer to my Goldcard questions I'd be real thankful.

Sounds to me like you have a very good grasp of all these things. It's nice, but rare, to see people doing their own research and learning this much before posting questions!
There's nothing i can add really but to confirm that ,yes...flashing a stock ROM will revert changes although some devices can be picky with which stock ROM is best.
As an aside, have you considered doing development work yourself, perhaps ROM building? You're obviously capable, interested and 'have the right stuff'!

DirkGently1 said:
Sounds to me like you have a very good grasp of all these things. It's nice, but rare, to see people doing their own research and learning this much before posting questions!
Click to expand...
Click to collapse
Well, thank you. I'm slowly beginning to get used to doing as much research as I can get by with and provide what I know, or at least think I've been able to conclude, and then ask a question about it.
DirkGently1 said:
There's nothing i can add really but to confirm that ,yes...flashing a stock ROM will revert changes although some devices can be picky with which stock ROM is best.
Click to expand...
Click to collapse
When you say flashing a stock ROM, would this also apply for RUU-packages? As an example; If I have an HTC Hero and I manage to downgrade it through som root-method, will I be able to run an official HTC-provided RUU to get it back to a factory state?
The only way I have been able to return my Nexus One to a factory state is by the use of a PASSIMG.zip-file, but then I would have to make sure that I am using the stock recovery. One reason for my question is that I'd also like to know if it's possible to run an RUU-package on a rooted, and/or custom recovery-flashed and/or engineering SPL-flashed handset and have it returned to a factory state.
DirkGently1 said:
As an aside, have you considered doing development work yourself, perhaps ROM building? You're obviously capable, interested and 'have the right stuff'!
Click to expand...
Click to collapse
Well, sure, the thought has struck me once or twice. I'm currently in my last months of my education in becoming a Master in Software Engineering, but at the moment I'm into getting to know more about how Android works on different handsets and how the different parts are connected to each other. I will very soon dive into Android development as it's the only really interesting area for handsets/mobile communication, that doesn't have the price of a whole Apple Macintosh to even be able to begin programming for it.
I'm sure I will get an Apple suite later on, I like the diversities of different manufacturers but for the time being I'm price conscious.

Is there anyone who knows a thing or two about Goldcards?
One of my questions in the first post was about the CID/RUU-relation to the Goldcard.
I have read from one or maybe two people on random forums, stating that the Goldcard is _only_ needed when the handset is carrier-locked. I'm very interested in getting to know more about the Goldcard and when it is supposed to be used and/or required.
Because a lot of the times when dealing with rooting HTC handset it boils down to having a Goldcard or not. But at times I hear about methods where Goldcards aren't needed. But the statements differ from "You need a goldcard" to "You only need a Goldcard when your handset is CID-locked" to "You need a Goldcard to be able to flash an RUU that is older than the one you currently have on your handset." to "You need a Goldcard if you want to flash an RUU with a different CID" to "You don't need a Goldcard at all".
Somehow I think there are some kind of specific combinations, for instance something like this;
CID-locked handset => Needs a Goldcard to be able to root
RUU-version on the handset is new => Needs a Goldcard to be able to flash older RUU-version
RUU/CID-combination is X and Y => Needs a Goldcard to be able to flash an RUU that has the RUU/CID-combination A and B
...
...
There are times when some rooting methods do not require a Goldcard at all, but it seems to me they are pretty rare when compared to those who require a Goldcard.
Someone out there should have the whole story about this and I'm very interested to know how these things work and I'm also grateful for sharing this with me.

[Q] No OS installed, won't flash rom, mistakenly relocked...HELP!

I have scoured the internet for a solution, but my phone is from Hell. Every single thing I have ever done has ended in errors, ranging from trying to flash the rom zip and getting a "data length is too large" to errors while my phone did still have an OS and flashing through fastboot or double clicking in an exe would give me errors regarding the version or whatever other bs. I have been actively trying to fix this phone for well over a year! When I first started, it was still under warranty, and now it's just a paperweight that continues to waste days of my time at a time.
I am by no means a noob to electronics, but it seems I must be missing something I didn't learn, as I must be a noob in rooting/unrooting/flashing phones. I hope to God nobody suggests that I should have posted this in another thread, as I have searched all similar threads (all over the internet, different phones, any website that Google could find) and tried every single method anybody suggested. Most methods would be completely useless as I wouldn't meet the prerequisites, but I tried even those methods once I exhausted all serious methods.
I have officially gone mad and am about to say goodbye to all technology and go live in a Amish community for the rest of my life. I became so desperate and crazy that I managed to mess up my phone further than it was to begin with. PLEASE HELP! I am at your humble service, and I await any and all instruction.
A little background:
I got the phone from a family member once they cracked their screen, as I am much more of a hardware techie and I got the phone as a present to fix and use for myself. My family member is trigger happy and likes to root everything he could get his hands on. I am much happier with the stock versions of things as they give the best performance for my needs, not to mention the much less hassles and headaches with updates and reception and so on and so forth. I got the phone when it had 1.73.502.1 software on it. I wanted to upgrade to the 3.18.502.6 software version that was available, unroot the phone, and take everything back to dead stock. Since then, 5.18.502.1 has become available. (Side story about this: when double clicking the 5.18.502.6 RUU exe to go into my temp folder and extract the ROM zip, this version doesn't execute for some reason when downloaded from the "HTC OTA and RUU collection" thread (http://forum.xda-developers.com/showthread.php?t=2119610), and the previous version mentioned does execute and show up in my temp folder in Windows, but there are two roms (rom 1 and rom 2), and when extracting them, I get errors, so I had to download and extract 2.20.502.7, which executed and extracted without any problems)). I tried unlocking the bootloader through HTC's website (yes, I believe I relocked it about a year ago in a stupid move because I read that in order to execute an RUU you have to be relocked), but I guess AT&T is a big douche, so I had to superCID (cid 11111111) before doing so, but simply doing "fastboot oem writecid 11111111" wouldn't work, so I literally tried a million different tools I found until magically (literally, I don't know what happened or what I did), I got to superCID, in which case I unlocked with no problem. I then tried every method possible of updating, flashing, everything, but when things got to the actual rom zip part or executing RUU or basically the last steps, I would always be presented with errors and fails. In an angry move, I went to TWRP and erased everything I could get my hands on (I know, I messed up, kill me), and so I deleted the OS and whatever else was on the phone. Since then, I also managed to relock the bootloader (which I locked and unlocked multiple times with no problem and had the unlock code, so I figured I'm safe forever), and take my CID back to cws__001 (which I thought might be the cause of all of my errors, but found that now I can no longer unlock my bootloader).....
I now have an HTC One X from AT&T that is relocked, CID is cws__001,stock recovery, no operating system to boot into adb, and not able to flash anything on it to get into TWRP at least to try and adb sideload or some other things to take back the screw-ups I did since last night.
Info on bootloader:
TAMPERED
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Nov 26 2012, 18:37:14:-1
I apologize beforehand for even touching the phone's software and trying to mess with it and maybe learn a thing or two in the process. Again, I thank you greatly beforehand for all your input, and I hope to hear back soon!
Erik

You can run the 3.18 att ruu to fix the phone to the point of it booting. If you want to learn a few things (such as custom ROMs and the like) you can visit threads on how to root, unlock the bootloader, get supercid, and then s-off.
Sent from my One XL using XDA Premium 4 mobile app

Thanks for the prompt response
I tried what you suggested just now (downloaded the 3.18.502.6 RUU exe from the thread http://forum.xda-developers.com/showthread.php?t=2119610, went into fastboot, right-clicked the exe and chose to run as administrator), and I got "ERROR [158]: Image Error"
I had tried that numerous times in the past as well, with either the same error or various other errors, through fastboot and through the phone being on and fully operable.
On a side note: for some reason it's recognizing my current image version as 3.18.502.6, but there is no operating system on there now, and when there was, it was definitely 1.73.502.1
Any other suggestions?
edit: also, please don't tell me that I should have changed my CID to CWS__001 instead of cws__001....does it make a difference if the CID is lowercase or uppercase?

Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita

timmaaa said:
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
You're correct about me having rushed the process. Well, I didn't at first, but after the first few days, I began to just try anything I could get my hands on, and believe it or not, that was a year ago, so every once in a while I'll grab the phone and try searching some new things, but it's not like there are an infinite number of ways to go about things :\ Thanks for the help so far though, really
edit after seeing your edit: hahaha! yeah, you caught yourself perfectly! Also, in response to your question: I've tried flashing the unlock token through multiple different programs, but to no avail. As you said, I royally screwed myself in thinking that I could put back my CID (but my stupid self didn't put uppercase letters), and I thought I'd still be able to use my unlock token since I had gotten the code beforehand and it worked multiple times before, but I was mistaken

To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita

timmaaa said:
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
Click to expand...
Click to collapse
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time

Ruu while in fastboot mode.no?
Edit my bad just noticed the part about lower case cid
Sent from my One XL using xda app-developers app

EsoteRIcalfreaK said:
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Click to expand...
Click to collapse
Unfortunately for you there is no differing view. You've gotten the phone to a point where it cannot be resurrected via traditional means. Jtag is indeed your only option, and yes it's a repair service. They hook your motherboard up to a riffbox and push the partitions to it, you can even request things like s-off. There's a user here on XDA called zarboz who does jtag repairs, and I believe he's the cheapest you'll find. He's based out of Ohio I think. Contact him via PM for details.
Sent from my Evita

Great, I have an awesome paperweight that I made myself, and the person that I could talk to so that I could get help doesn't accept private messages from someone who has less than ten posts, hahaha
I'm so hoping that the head of HTC's development department somehow joins the forum and tells me that I just need to fastboot some crying smiley face symbol and the phone will start dancing for me until everything goes back to it's original factory settings...why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!

The RUU is HTC's version of software reset. The problem isn't a lack of reset program from the manufacturer, the problem is the fact that you changed the CID incorrectly.
Sent from my Evita

I can't believe uppercase and lowercase make a difference though
Also, I tried executing the RUU in multiple different ways, even when the OS was operable, in the last year, multiple times, with multiple different versions, but I was always presented with an error of some sort and the RUU setup would cancel and close. The first thing I tried after every exploit that I did was to run the RUU, so I really don't know what else I could have done differently to have gotten the RUU to run without errors, or else I wouldn't have gone this far and tried unorthodox measures to try and revive the poor guy

Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Sent from my Evita

EsoteRIcalfreaK said:
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
Click to expand...
Click to collapse
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
EsoteRIcalfreaK said:
I have scoured the internet for a solution, but my phone is from Hell.
Click to expand...
Click to collapse
EsoteRIcalfreaK said:
why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
Click to expand...
Click to collapse
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
EsoteRIcalfreaK said:
I can't believe uppercase and lowercase make a difference though
Click to expand...
Click to collapse
How is that so unbelievable? As timmaaa mentioned, case is often crucial when it comes to computers. Since when is syntax not important when typing computer commands?
For the CID in particular, its obviously all hinging on a handful of crucial characters. So it needs to be typed exactly right.

redpoint73 said:
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
Click to expand...
Click to collapse
adb works in recovery or while the phone is stuck at loading screen but not in bootloader. Ofcourse, without an OS there's nothing to grant su. Though, he MAY be able to rewrite his CID using the 3.18 method anyway since I imagine the recovery must have SU or equal permissions..
I am less inclined to want to help after all his whining though :/

exad said:
I am less inclined to want to help after all his whining though :/
Click to expand...
Click to collapse
timmaaa said:
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Click to expand...
Click to collapse
redpoint73 said:
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
Click to expand...
Click to collapse
Guys, guys, please do understand that I did many many hours of research before attempting anything. It wasn't until just recently that I began to just go plain crazy and just throw whatever I could get my hands on into commands and such (and that was all done in the matter of one frustrating night actually, so for almost two years I researched and learned things from mostly this board and tried different methods I found useful). You should see the bookmarks I have created on my browser (I deleted a bunch of useless ones recently, but I have 24 as of right now just explaining One X things)!
If you read closely (I know, I have written a lot, because I have seen people get completely flamed for not writing enough information), I mentioned that I have been trying to revive this phone for over a year now (two years this month). The reason I didn't ask for help earlier, which I wanted to do from day one, is for respect to exactly you guys...
1. I was about to make an account on here and post the very first day I got the phone, but after watching the introduction/noob video on YouTube for this website that explains the rules and what to do before EVER posting ANYthing, I decided to do a little more research and do my best to listen and learn from all the tutorials and great help you guys have given to others.
2. I wanted to make sure, as the video and as many of you mention on this forum, to try every avenue and method before coming for help. I did so precisely for the reason of not wanting to look as though I'm "whining". I might have exaggerated a bit in saying that I threw everything I found at the phone, because I did not just blindly do things without the proper research.
The OS I "accidentally" deleted in hoping to get rid of whatever software was on there that really was not changing or allowing me to RUU or anything. I thought that if I deleted it, it would be easier to put a fresh genuine stock copy on it. I was mistaken, and by the time I realized, I had done the damage to the phone. The biggest mistake that caused this irreversible damage was MY OWN unfortunate way of thought of thinking that uppercase and lowercase wouldn't make a difference (actually the truth is, I thought the original CID was lowercase, but seeing as how I had spent almost two years on this project, and I had had a very long day, I didn't double check to make sure, and I figured that I would be able to go back and change it worst case scenario...this my MY mistake, and I am by no means whining or complaining for MY OWN MISTAKE).
All that being said, please gentleman, if there is anything I could do to revive this phone and reverse my wrong-doings, I would appreciate it greatly and be forever grateful. I assure you, I will not perform a single step without confirming that I am doing the right thing. I am definitely wanting your help, and I definitely do seek to leave behind something that other people who make similar mistakes to mine can look back on for future reference.
Long story short, I messed up, it's my fault, I'm not complaining or whining, my Crapple and Samsuck comments were just to poke fun at those companies, and I would really appreciate it if anyone could help me in any shape way or form. Thank you beforehand
Erik

Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086

exad said:
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
Click to expand...
Click to collapse
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand

To be honest I think this was dubious at best, it was worth a try but I didn't hold much hope for it actually working. The only place it might have worked would have been in TWRP, even then your system was wiped so the structure required for the commands doesn't even exist in the partition. Someone else chime in here if I'm wrong, but I still believe jtag is the only option out of this.
Sent from my Evita

EsoteRIcalfreaK said:
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
Click to expand...
Click to collapse
You have stock recovery!? -_- I think timaaa is right then -_- I will flash stock recovery and test ADB just to be sure, just for you homeboy. I will post an update shortly.
---------- Post added at 03:21 PM ---------- Previous post was at 03:05 PM ----------
Yeah, sorry man, Jtag only.