Database Info

Gold Card

Hey guys,
I have been trying for ages to get a goldcard to work for the Sensation. I have managed to create a goldcard, but sadly, when trying to flash via fastboot (using RUU) and off the SD card, it doesn't work.
This leads me to think: Have HTC someone disabled the spoofing of CIDs from gold cards? Like I said, the gold card is created properly, the only thing I can think of, is that HTC disabled it? Or could it just be the SD card that is causing it to not work?
I am not a huge expert on this, can anyone else help?

madindehead said:
Hey guys,
I have been trying for ages to get a goldcard to work for the Sensation. I have managed to create a goldcard, but sadly, when trying to flash via fastboot (using RUU) and off the SD card, it doesn't work.
This leads me to think: Have HTC someone disabled the spoofing of CIDs from gold cards? Like I said, the gold card is created properly, the only thing I can think of, is that HTC disabled it? Or could it just be the SD card that is causing it to not work?
I am not a huge expert on this, can anyone else help?
Click to expand...
Click to collapse
nice your trying, will keep my eye on you

capychimp said:
nice your trying, will keep my eye on you
Click to expand...
Click to collapse
Haha thanks capy
I have 4 SD cards which I am testing out. Using bootloader method with PG58IMG.zip (Sensation ROM name in zip via bootloader) and via RUU (fastboot commands and then running the RUU, commands found here
Let's see how it goes. But I am worried that HTC did disable it somehow Is that possible?

i have no idea, but now i have a big intrest as i can get it here now, but if i cannot cook for it, then why by it but would be nice cooking for it along with dhd

I believe goldcard doesn't really help on most modern devices from htc...

pulser_g2 said:
I believe goldcard doesn't really help on most modern devices from htc...
Click to expand...
Click to collapse
I thought it worked on the Incredible S? Certainly worked on the DHD. I didn't ever use one, but I know people have done it (seen it in threads regarding debranding)

Information courtesy of jagaroth via a PM to me:
Sorry to PM but I can't post on a dev section without 10 posts and won't spam other subjects when hacking the desire is what I'm interested in. Feel free to repost if you think anything below is interesting (or will save others time).
Ok, I have at least 2 working gold cards and none of the HTC generic Roms will flash.
Thought I would try flashing my networks ROM (just testing fastboot PG58IMG.zip) & while that passed sig check it failed to install.
So next thing to try was using the RUU.exe and againg a fail. Seems you can't downgrade your existing ROM. I have 1.27.161.1 & the RUU is 1.24.161.1.
With downgrading Roms out for now (even with a gold card) a bit more digging is needed to un-brand and caution in upgrading since going back if an exploit is discovered will be tricky.
There does seem to be a weakness that may enable gingerbreak style root. Data can be pushed to data/local/tmp , chmod used and code executed there. A small chink in the armour.
Much faffing around in adb shell and examining logcat data awaits. Feels very strange having a tethered phone when I've got used to wifi adb!
Click to expand...
Click to collapse
So yeah, seems goldcard is out Such a shame
I hate HTC right now. At least a nice little goldcard would mean I could dump this Vodafone crap, and get proper Sensation Rosie here (the transparent one).
Update: I tried to run the HTC 1.27 shipped RUU (not the 1.24 RUU) and I got a different error. It was a signature error, not a CID error. What could this mean exactly? Not an expert.

madindehead said:
Information courtesy of jagaroth via a PM to me:
So yeah, seems goldcard is out Such a shame
I hate HTC right now. At least a nice little goldcard would mean I could dump this Vodafone crap, and get proper Sensation Rosie here (the transparent one).
Update: I tried to run the HTC 1.27 shipped RUU (not the 1.24 RUU) and I got a different error. It was a signature error, not a CID error. What could this mean exactly? Not an expert.
Click to expand...
Click to collapse
Goldcard's don't allow downgrading on their own. You have to change the ROM version identifier in misc to a lower version - in addition to using a Goldcard if you have a carrier CID and are downgrading to stock - if you want to do that. As far as upgrading/unbranding, I can't say why the sig check is failing as I don't have the phone and I'm not an expert. These instructions work for making a Goldcard for the DHD:
http://androidforums.com/desire-hd-...ding-1-32-405-6-1-84-720-3-a.html#post2657079

dazweeja said:
Goldcard's don't allow downgrading on their own. You have to change the ROM version identifier in misc to a lower version - in addition to using a Goldcard if you have a carrier CID and are downgrading to stock - if you want to do that. As far as upgrading/unbranding, I can't say why the sig check is failing as I don't have the phone and I'm not an expert. These instructions work for making a Goldcard for the DHD:
http://androidforums.com/desire-hd-...ding-1-32-405-6-1-84-720-3-a.html#post2657079
Click to expand...
Click to collapse
So, where is the misc that you can change the version number in to downgrade then?

madindehead said:
So, where is the misc that you can change the version number in to downgrade then?
Click to expand...
Click to collapse
It's the partition on the phone where things like CID, ROM version and other variables are stored. You need at least temp root to write to it so we're not in a position to do this yet.
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/

dazweeja said:
It's the partition on the phone where things like CID, ROM version and other variables are stored. You need at least temp root to write to it so we're not in a position to do this yet.
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
Click to expand...
Click to collapse
Damn ok. Thanks for that. Then I will stop with trying to get 1.24 to install. 1.27 gives me a signature error, not a CID error, so not sure what that is (going from Vodafone 1.27 to HTC 1.27).
I guess I will pack it in until we get temp root. And since GingerBreak doesn't work, I don't know how we can get temp root. Really need a proper dev to get the device and start work on it, as I wouldn't know where to start looking, unless people can give me pointers?

If we find a dev willing to work on it we should have a whip round so they can buy a sensation. I saw they did this on an attrix thread if I remember right and they had the money in donations within a couple of days.
Sent from my Desire HD using XDA Premium App

kingguff said:
If we find a dev willing to work on it we should have a whip round so they can buy a sensation. I saw they did this on an attrix thread if I remember right and they had the money in donations within a couple of days.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Not a bad idea.
TO begin with, temp root would be a massive bonus. First allowing rooted apps to at least run, and then work can begin on the actual bootloader.

Yes it was the attrix thread, they got 700$ to a dev in China and he is making progress by the sound of it.
Sent from my Desire HD using XDA Premium App

I cannot find it now. I'll have a look when i get home
Sent from my Desire HD using XDA Premium App

well i tried everything i know related to goldcards and no dice. my sensation has 1.27 base and i was trying to update to 1.28. no matter how many cards i made (yes they were correctly made) i come done to this:
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)

The best is to speak with AlphaRev team...........

I only flashed the stock asia rom again,and felt a bit faster than before..

same
Same thing here
I have made a gold card, and i am getting the Country ID (CID) error.

RADLOUNI said:
Same thing here
I have made a gold card, and i am getting the Country ID (CID) error.
Click to expand...
Click to collapse
The same..I tried to flash O2 1.34 ROM, but it said CID incorrect

easier way to get engineering S-off?

hey i've installed a couple of roms on my phone then installed that stock att radio over one, it was great, nearly doubled my battery live and reception was excellent, but after trying miui and doing a nandroid restore of my old rom when i try to flash the radio again it tells me "FAILED remote: not allowed"
i see this tutorial here but im wondering if theres a gui one click for it and how come its not included with the S-off and rooting business?
http://www.addictivetips.com/mobile/how-to-gain-s-off-radio-and-engineering-on-htc-desire-hd/

thatg said:
hey i've installed a couple of roms on my phone then installed that stock att radio over one, it was great, nearly doubled my battery live and reception was excellent, but after trying miui and doing a nandroid restore of my old rom when i try to flash the radio again it tells me "FAILED remote: not allowed"
i see this tutorial here but im wondering if theres a gui one click for it and how come its not included with the S-off and rooting business?
http://www.addictivetips.com/mobile/how-to-gain-s-off-radio-and-engineering-on-htc-desire-hd/
Click to expand...
Click to collapse
look here --> http://forum.xda-developers.com/showthread.php?t=855403

Doo Doo said:
look here --> http://forum.xda-developers.com/showthread.php?t=855403
Click to expand...
Click to collapse
this will give me not just eng s-off but engineering s-off? i already have S-off but need engineering to have total control of the radio

thatg said:
this will give me not just eng s-off but engineering s-off? i already have S-off but need engineering to have total control of the radio
Click to expand...
Click to collapse
eng s-off is engineering s-off.
First thing if you aren't compiling a kernel and trying to run it then you should not eng s-off your phone there are other methods. (go to our dev section and look for the radio thread)
Second if you didn't know (could figure out) eng s-off is the engineering hboot then, you probably shouldn't try to mess with that level of the phone ... no?

mudknot2005 said:
eng s-off is engineering s-off.
First thing if you aren't compiling a kernel and trying to run it then you should not eng s-off your phone there are other methods. (go to our dev section and look for the radio thread)
Second if you didn't know (could figure out) eng s-off is the engineering hboot then, you probably shouldn't try to mess with that level of the phone ... no?
Click to expand...
Click to collapse
+1
Eng s-Off is completely unnecessary for the only level of radio control most of us mortals need... Flashing different radios.
This eng s-Off radio method, in all it's obsolete glory, sure has legs...
I'm sure it doesn't help matters that it still appears to be the "official" method over on the desire hd radio thread. There sure isn't any post here in the inspire sections that continue to endorse this method.

ok just tried this, when using the visionary app it didnt reboot when i tried permaroot so i rebooted it myself, then when using S-off one click it tells my my bootloader is corrupt
edit: computer had bad drivers worked with my other one thanks yall!!

[** Status 7 Fix **][31 July] For T-Mobile users whos roms will not install

If you are one of the few that have the Tmobile Sensation with hboot ending .0008 you are probably having a hard time installing most roms. This is the problem i had and found a fix.
Method 1
Just Update to Clockwork Mod 4.0.1.4 attached at bottom
Then Wipe and Flash.
Mine was not that easy to do i had to go with Method 2 but on the bright side frees me up to do anything Rom, RUU or Radio i want.
Method 2
1. S-off your device
2. Super CID your Device - Found on same page as S-off instructions
3. Install RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed
4. Install CMW 4.0.1.4 -PG58IMG Below-
5. Install your choice of Roms on your Tmo Device.
Thanks again to all that helped get us where we are and if someone would like to rewrite this with a little more or better layout feel free.
FiZiX

Is this a known issue with all of them? I have a tmo sensation with this hboot but haven't had problems yet flashing any roms but have only flashed two so far, do I need to do this? Thanks
Sent from my HTC Sensation 4G using XDA App

Thanks very much
Sent from my greatest Sensation 4G

ebatr8 said:
Is this a known issue with all of them? I have a tmo sensation with this hboot but haven't had problems yet flashing any roms but have only flashed two so far, do I need to do this? Thanks
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
From what i understand no. There are a few different Tmo models and not all are affected. This is a tool if you are one of the unluck few.

"The ROM update utility cannot update your Android Phone".
"MODELID_ERROR"

For those of you with custom roms are you showing any loss of data speeds over T-mo's network with the "euro" radios?

Pinepig said:
For those of you with custom roms are you showing any loss of data speeds over T-mo's network with the "euro" radios?
Click to expand...
Click to collapse
Not me. However I still have terrible signal quality compared to over phones.

mikeDCMDVA said:
"The ROM update utility cannot update your Android Phone".
"MODELID_ERROR"
Click to expand...
Click to collapse
Did you super cid your phone. The cid should be 11111111 AFAIK for this to work.

mikeDCMDVA said:
"The ROM update utility cannot update your Android Phone".
"MODELID_ERROR"
Click to expand...
Click to collapse
Sorry i gave link for the wrong super CID link. That does not work. Follow the super CID instructions on the S-off Insturctions page. should be one that tells you about fast reboot and changing cid to 11111111

^^^^^
Yeah, much easier LOL

The ROM flashed anyway...lol, problem must have been my CWM version...now I can wipe data without the phone shutting off, w00t w00t

or you can just toggle script asserts in cwr

so i just want to be sure i understand this.... if i root and install any rom besides a rooted tmobile US rom , then i will need supercid in order for the radio to work correct?

Flashing the new recovery worked just fine for me. Thanks man.

[Q] T-Mobile UK - Sensation Rom Dump?

Hi folks,
I've got a T-Mobile branded Sensation, no idea how long they will take to get the 2.3.4 update out, probably months.
I want to S-OFF, Super CID etc and flash something else or just use a Euro RUU.
Problem is, for warranty purposes, I need to back up my current rom or obtain the T-Mobile RUU.
Is there anyway I can dump this rom first?
I've checked the big list of roms for the Sensation, lots of US ones there but nothing for T-Mobile Uk.
Thanks

Backup stock ROM:
1. S-OFF
2. Install CWM
3. Backup with CWM
Job Done!
Restore stock ROM:
1. Restore backup
2. Flash stock recovery
3. Flash stock HBOOT
4. Run S-ON command via adb
Obviously the ROM you restore will have all your personal data so a hard reset after making sure it boots up would be wise to go back to a 100% 'out the box' state

i,m uploading the official TMO uk 1.34 RUU now link to follow
link
http://dl.dropbox.com/u/38694724/RU...0U_10.51.9007.27_M3_release_196473_signed.exe

Where'd you get that?

west2cool said:
i,m uploading the official TMO uk 1.34 RUU now link to follow
Click to expand...
Click to collapse
That's excellent, cheers!!! Definately UK?

It would have to be as the T-Mobile US ones are 1.27/1.29

EddyOS said:
It would have to be as the T-Mobile US ones are 1.27/1.29
Click to expand...
Click to collapse
Would make life alot easier if it is the real deal.

Very true but I'd still backup your ROM as it stands anyway before flashing anything new

EddyOS said:
Where'd you get that?
Click to expand...
Click to collapse
got it off a chinese website, i was hunting around

One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.

Arthur Hucksake said:
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Click to expand...
Click to collapse
link in my first post, dont forget thank

Thanks dude.
If this is the real deal, legit one, then we're onto a winner.

I got a "communications were interrupted" error when using Revolutionary.
Rebooted with vol down, it's showing me as SHIP S-OFF
Ok to assume that it's all ok anyway?

I had this too, run it 3 times and eventually it will say it's done. I did report this on their feedback on the website as well

When I boot up with vol down, it is showing Revolutionary at the top and S-OFF.
Copied the PG58IMG 4.0.1.4 updated over, went into HBoot and it flashed.
Reboot, deleted the PG58IMG off the SD card.
Reboot, back into the bootloader screen and it's allowed me to run clockwork, so now done a full back up which has just finished.
All I want to do next is install the stock European 2.3.4 rom (RUU_Pyramid_HTC_Europe_1.45.401.2), so I assume the next step is to change CID?
Thing is, I want to be able to use future OTA updates with this rom. Am I right in saying that whatever ID I set it to is what updates I will get?
Cheers

Yeah, change CID to HTC__001 and then you're completely unbranded. OTA's should also go through without issue too

Awesome. Job done. CiD change, installed the european rom and i'm now 2.3.4
Bootloader is showing ***locked*** but I aint worried about that.

That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)

EddyOS said:
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
Click to expand...
Click to collapse
I don't understand why it still says S-OFF at the top. lol

Because it does, but it's not technically S-OFF - I tried to flash a different HBOOT and it didn't work until I re-ran Revo

[Q] HTC Sensation totally stock in boot loop

Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.

theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya

AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).

astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.

astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.

AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.

If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.

astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb

rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible

Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work

Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it

rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.

I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io

Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?

HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.

theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++