Database Info

remove supercid??

Back when i first got my phone i did the supercid mod on my phone, everytime i flash a rom i have to do other things just because of it (larger mms, install wifi calling patch etc etc) my girlfriends sensation on the other hand is NOT supercid and she never has to do any of the additional patches i have to do.
So is there any way i can reverse the supercid mod on my phone?

Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"

_HTC_DHD_ said:
Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"
Click to expand...
Click to collapse
how do i know what my original cid would be?

Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on

I AM M07S said:
Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on
Click to expand...
Click to collapse
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.

illuminarias said:
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.
Click to expand...
Click to collapse
Oh well I'm sorry but last time I did this it gave me my original and I know this because I have changed it to SuperCID and last night infact I was playing with the adb commands and it gave me my original CID unless of course it has gone back to the original which in that case i am really sorry for being a noob to the android xda community (but im only 17)

If you are on T-Mobile US, then the CID is T-MOB010.
Sent from my HTC Sensation Coredroid 2.7

Try this...
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.

cgjjaf said:
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.
Click to expand...
Click to collapse
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?

I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?

raul602 said:
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?
Click to expand...
Click to collapse
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
bakili said:
I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?
Click to expand...
Click to collapse
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..

civicvx94 said:
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..
Click to expand...
Click to collapse
First of all, thank you very much for your response, I really didn't know exactly what it was till you explained it, THe reason i want to revert back to stock is simply because there are certain things that never seem to work on my phone that always work perfectly on my girlfriends phone, first one being WIFI(never gets installed and second being small mms pics, the ONLY difference between her and my phone is that i am superCID and she is not, i can get the patches and fix it but i don't really need supercid now that i understand it.
Seriously though, thank you!

No problem at all, glad to help! Hope you get things figured out..

Change CID after Unbrick

Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1

jcarrz1 said:
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
Click to expand...
Click to collapse
Hmm that's a rough situation you are in.. If you can't find the ruu that would be a problem..
First try contacting football.. For ics ruu of bell.. (football provides most of the ruu's.. He is the OP of pyramid shipped rom collections thread present in sensation development section)
Try changing Cid to a well know one
Like this.. What you do is
First reboot to bootloader
fastboot oem writecid HTC__001 (supercid won't work.. So stick with this for now)
Then remove battery..
Then reinsert it. Power on to bootloader
And check Cid
fastboot getvar cid
If this worked.. Great. Find a Europe ruu and flash it
Last .. Try htc-dev unlock.. If luckily you..got unlocked bootloader..
Flash custom rom..Then SOFF..Then change back Cid..Then flash the old ruu of your Cid..Then SON
To get a working rom
Sent from my pyramid.. Through blazing fast sonic waves

For future reference; S-ON is the last thing you do when sending the phone back. RUU needs to happen before that.
The situation you're in, you're going to have to HTC Dev unlock your bootloader, and fastboot flash system and boot, possibly install a firmware PG58IMG as well... hopefully that will be enough to get the phone booting. Then you'll want to S-OFF and flash the RUU (this will also set you back to ***LOCKED***), then you can S-ON.

You guys are so helpful. I will try this.
My utmost thanks,
jcarrz1

Is HTC dev unlock reversible, and does it void my warranty even if I reverse it? does it leave any trace/can they tell?

Getting S-OFF removes all trace of it.

Rusty! said:
Getting S-OFF removes all trace of it.
Click to expand...
Click to collapse
And then getting S-ON again will be like stock configuration?

No, going S-OFF changes ***UNLOCKED*** back to ***LOCKED***

jcarrz1 said:
And then getting S-ON again will be like stock configuration?
Click to expand...
Click to collapse
yep...
if you use juopunutbear soff after HTC-dev unlock ..you will get locked/juopunutbear bootloader (instead of relocked )
then RUU (to make everything stock..and to prevent wrong SON brick) and SON again ..will be complete stock

Again, I am amazed by your helpfulness.
Thanks guys! you run the general section
jcarrz1

I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?

jcarrz1 said:
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
Click to expand...
Click to collapse
ohk for firmware flash you can use this
copy the firmware zip (PG58IMG.zip) to the adb/fastboot folder
open command prompt from adb/fastboot
then these commands one by one
fastboot erase cache
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed while flashing in the middle ..be careful)
fastboot reboot-bootloader
that would flash the firmware

[Q] Phone won't boot up normally and cannot flash RUU

Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred

fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )

ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred

A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred

fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID

Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred

fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place

dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred

fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred

fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery

ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work

rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred

wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary

ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.

fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )

ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.

fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom

Please Help Me Not Brick My One S

Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
There is not compatible RUU for my one s so heres the steps I'm going to do ....
1) SuperCID My Phone Using This Tutorial
http://androidforums.com/one-s-all-things-root/690970-guide-supercid.html
2) Then Proceed With S-OFF using this tutorial
http://m.youtube.com/watch?v=fTp5uwURKdg
3) Relock Bootloader Using Hasoon2000's All in one toolkit and flash stock recovery (I Need Stock Recovery Image For Htc one s S4 Processor) I Will use this tutorial for steps 3/4
http://m.youtube.com/watch?v=SZuAjz4PIjU
4) Run The RUU (will I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ?)
I Also Need A RUU Which Is On JellyBean Not ICS
5)Unlock Bootloader and Root
Please can ou Anwser These Questions Please <3
ill I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ? I am currently branded to three uk
And can someone link me to stock recovery Image for htc one s S4 Processor
Is There Any JellyBean RUU if So Please Link me to them and tell me if I can use them after I have done SuperCID and s off
And let me know if there any problems in my method I am going to use
Thanks One S Community

Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.

rootrider said:
Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.
Click to expand...
Click to collapse
What should I change my CID to and will I be unbranded ? And can I use the ruu you provided the latest one .and I don't understand what you mean with the OTA Updates. I'm branded to three UK and for 8. Change T-MOB010 to 11111111 and save the file as mmcblk0p4MOD. Would I just find H3G and change it to 11111111

You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app

Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
k1llacanon said:
You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.

I'm going to run the ruu you provided me with will I have any problems with that and what should I change my CID To? Also I'm going to flash stock recovery and lock bootloader so there no probs

rootrider said:
Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.
Click to expand...
Click to collapse
Sorry for being a pain it's just I don't want to brick my phone and could you explain this as I don't understand it
view plaincopy to clipboardprint?
adb pull /sdcard/mmcblk0p4
and hit enter.
NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 or 00000214 and you should see "T-MOB010" with your IMEI number after it.
NOTE: "T-MOB010" is the T-Mobile US version, depending on your carrier this will change, but it will still precede your IMEI. See the link at the end of this post for a list of other CID's.
MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type
view plaincopy to clipboardprint?
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
Shall I note the file size so if it. Example.txt(4642kb). I would note the file size and I would just change my CID to HTC__001 ?
And don't I need to get the fast boot files and softbin3 and stuff but the site doesn't provide me with anything could you link me to them ? I have literally no clue
And in HxD. editor will mine look like this http://dl.xda-developers.com/attach...3a77c716b8/51864687/1/0/8/2/7/9/0/hexedit.jpg
Wouldn't I change my CID To H3G__001 but I want to be unbranded

For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3

ryanshew said:
For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple

Zaman-The-Man said:
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple
Click to expand...
Click to collapse
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or this link)
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps

usaff22 said:
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps
Click to expand...
Click to collapse
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS

Zaman-The-Man said:
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS
Click to expand...
Click to collapse
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)

usaff22 said:
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)
Click to expand...
Click to collapse
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?

Zaman-The-Man said:
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?
Click to expand...
Click to collapse
you shouldn't need to

usaff22 said:
you shouldn't need to
Click to expand...
Click to collapse
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks

Zaman-The-Man said:
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks
Click to expand...
Click to collapse
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2

usaff22 said:
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Alright so
1) Do SuperCID : 11111111
2) S - OFF
3 Do ' fastboot oem writecid HTC__001 '
4) Flash Stock Recovery
5) Run RUU
looks like I'm sorted
But can I ask what shall If my device doesn't match this PJ4010000.zip ?

You can forget step 4. It's not needed with S-off.
Verstuurd van mijn HTC One S met Tapatalk

Zaman-The-Man said:
Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Click to expand...
Click to collapse
Hi, I basically did the same thing as the OP. Deleted my backups by accident by choosing Factory Reset instead of Recovery. I think I am in an even worse position as I thought I had the right RUU as one point and needed to relock the bootloader. My bootloader screen looks like this at the moment.
------------------------------
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Can anyone tell me if this is a lost cause? Thanks.
This is the RUU I used -
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip.
Does anyone know if this is definitely the wrong one?

To all: Guys, no need to use S-Off for RUU. I DON'T KNOW WHO THE F*** CREATED THE PROCESS OF S-OFFING FOR RUUs AS WHEN I RESTORE STOCK LAST YEAR, IT WAS A SIMPLE BOOTLOADER RELOCK, AND RUU WE GO. IF WE S-OFFED, WE S-ON USING ONE-TOUCH STUFF.
To folaxstar: Well, you got as far as him. However, you got the COMPLETELY WRONG RUU. Technically, IT'S NOT AN RUU AT ALL. It is a Android 4.1 Sense 4.5/+ update for European unlocked HTC One S.
Do a "fastboot getvar cid" without the quotes (of course). You should get a CID that looks like the following: T-MOB010(T-Mobile US, as an example, it might not match what you got). Someone could determine the correct RUU.

[Q] Phone stuck in a boot loop, plus other problems

My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid

rzr86 said:
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
Click to expand...
Click to collapse
Thanks rzr86
I looked into the thread you suggested. For my region and CID, I was not able to get the RUU from the thread. What I could get was this - an OTA zip file that matches my software version exactly (3.33.720.106) from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
How do I proceed further with this zip file, since I don't have an executable RUU file?
I am hoping you can be of help -)
(The zip file contains -- META-INF, patch, system, firmware.zip, fotaBoot, version.txt)

Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom

Itsakash said:
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Click to expand...
Click to collapse
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?

jiteshgawali said:
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
Click to expand...
Click to collapse
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:

Itsakash said:
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Click to expand...
Click to collapse
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it

jiteshgawali said:
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
Click to expand...
Click to collapse
@ganeshp's one click root doesn't require htc dev unlock (meaning no prequisite permanent root; the guide has steps for temproot).
You just need one boot.
Do this: get the boot.img of your current (stock rom) and type fastboot boot boot.img.

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
I know its a long shot, but you should try doing a factory-reset from the bootloader, just in case it works.
Otherwise run an RUU from the bootloader.

firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?

It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106

rzr86 said:
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
Click to expand...
Click to collapse
Nope
Not necessary to boot into os for s off

Itsakash said:
Nope
Not necessary to boot into os for s off
Click to expand...
Click to collapse
It would help if you can tell me how to do this or direct me to any specific guide

jiteshgawali said:
I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
Click to expand...
Click to collapse
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u

jiteshgawali said:
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
Click to expand...
Click to collapse
For stock rom go http://forum.xda-developers.com/showthread.php?t=1923629.
Get the rom and extract boot.img.
Then use the earlier command I posted.

Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app

rzr86 said:
secondly Far_SighT the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
I said fastboot boot boot.im instead of fastboot flash boot booti.img as the previous one boots the rom with with the new image but doesn't attempt to write that to the boot partition. Hence it might get him a much needed boot to s-off.

jiteshgawali said:
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
Click to expand...
Click to collapse
as you stated your current is 3.33.720.106 so the OTA update is unnecessary
do as ganeshp suggested
Itsakash said:
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
Click to expand...
Click to collapse
both S-OFF guides say that stock rom is required in order to follow the S-OFF procedure

ganeshp said:
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?

jiteshgawali said:
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
Click to expand...
Click to collapse
Great now just download the HTC wwe ruu and install it... I'll link it up in a second.. Watch this space
Here is the link
http://htc.vi8.info/Sensation-XE/RU...0U-11.24A.3504.31-M-release-281004-signed.exe
Sent from my HTC Sensation 4G using XDA Premium 4 mobile app