Database Info

DS Bricket by using the S-off to S-on Tutorial

i have go to S-On whit this tutorial
http://forum.xda-developers.com/showthread.php?t=1187231
after i reboot i can only in the bootloader an its say Security warning.
I can not flash a RUU .
The VF Ruu say bootloader version error, and the HTC Ruu say User ID Wrong.
wat can i do?? My device is a VF devices..
or iss the device absolutly Bricket?!
Bootloader Shows:
****Security Warning****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
Radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
edit: i think i need a RUU_Saga_Vodafone_UK_1.47. ROM
****....

Try again and again with that RUU.
It didn't worked first time for me either.
Or try other RUU.
I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release

You should go to fastboot and try RUU

thanks for your answers.
i try it again and again (in fastboot)
it say update from 1.47.161.2
to 1.32.161.1 than it stop into 104 Bootloader Version Error.
I use the VF UK 1.32.161.1
all HTC Europe RUU`s says USER ID Error
before i would go to stock i have installed de Virtuos unity 1.31.
and befor this the VF German 1.47...

Try other RUU's...It has to work, anyway the phone is not bricked....maybe you should try revolutionary to get it S-off again. Don't know if it works if you are in fastboot, but you can try.

I try all the RUU`s and all give me (Device ID ERROR, USER ID ERROR) the Vodafone RUU alone give me the Bootloader Version ERROR...
I Try this again and again and ever it give me this errors.
Can not understand that is not worked...
i think i must really wait for a Vodafone RUU Leak that have the version 1.47.
Revolutionary say ever "waiting for Device" i think it will not work into the Fastboot Mode
I am very happy wen any can help me to make the system run.

i found the debug files of the RUUs and cane see wat he do..
i check and can make Fastboot commands over cmd
like this : fastboot devices
than it give an output like:
SH16KTJ01149 fastboot
wen i use any adb commands it never found the device....
can we any make over the Fastboot commands for fixing my problem?!
Or can we any moddifing the RUUs that this accept my device?!
i have copy two debug messages of the Vodafone RUU and a other:
Code:
<T011153><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{95567211-FFFE-46A1-B012-975D1FD8FE2D}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T011153>
<T011237><DEBUG><OUT>sending 'zip' (268758 KB)... OKAY</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011237>
<T011318><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T011318>
or debug messages like this:
Code:
<T230252><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{FB1AC174-A654-4612-B610-902E97243E0E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T230252>
<T230335><DEBUG><OUT>sending 'zip' (254595 KB)... OKAY</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T230335>
<T230414><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
</DEBUG></T230414>
HTML:
<T011638><DEBUG><OUT>sending 'zip' (254865 KB)... OKAY</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011638>
<T011717><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T011717>

Stuck in bootloader after use the S-off to S-on tutorial
no one can help???
edit: i see that is the exact same problem in this treath : http://forum.xda-developers.com/showthread.php?t=1190050
should i extract the boot.img and recovery.img from the rom.zip (VF Ruu) and install it over Fastboot commands??
i see a topic about this, but it was another htc phone
http://forum.xda-developers.com/showthread.php?t=1168081
can this work ?!
or should iflash CWM over fastboot ?? can i acces than CWM on s-on hboot??
i have backups from my stock rom.

should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.

Silverbullet09 said:
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Click to expand...
Click to collapse
I'm afraid that I don't really know what is the best step for you to do next, so aren't going to offer any advice in case it's incorrect.
Don't buy an xtc either look into the pay as you go xtc option or find someone who owns one near where you live, and pay to use it, should be about a tenth the cost.
See a very old thread that I created regarding the xtc clip http://forum.xda-developers.com/showthread.php?t=1076937
Swyped from HTC Desire S using XDA Premium

Try to use steps 1 - 10 from this guide : http://forum.xda-developers.com/showthread.php?t=1190992

If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.

globatron said:
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
Click to expand...
Click to collapse
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded

@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.

Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
Very glad to hear it
Swyped from HTC Desire S using XDA Premium

Nomader0 said:
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
Click to expand...
Click to collapse
do not use this procedure to s-on your Phone wen it iss branded, and you never have a 1.47 RUU from your Provider.
Your Phone is not Bricked but it will Stock on the bootloader,
i think wen you make a GoldCard before you S-on with this methode you are able to install a 1.47 RUU wen this is avaibled for you.
(I am not Sure, i think this only)
The know way to fixed this Problem wen you will not have a GoldCard will tell you another. Thats not my Fame
I think the best iss all have to wait off a SAFE S-ON methode.
We have not the Vodafone UK RUU can install than its not leaked with Version 1.47.
We have install the HTC Europe RUU with this Versions number on my Phone.
A Super CID let you install all RUU Updates with Version 1.47.Never need a GoldCard for this, wen you have Super CID.
I Know the workaround for this but i will tested this before i post this thing her.
@ben_pyett

so if my phone is not branded=i am super CID?
and it is safe to s-on with this method?

no you must enter the super cid wen you are s-off ...
i think you can go with the tutorial but all HTC RUU Europe for unbranded Phones avaibled.

Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
How to you fixed it ?
my DS work only fastboot cmd
help me, plzz...

poppy8x:
In order to bypass CID errors while flashing a RUU you can try one of two methods:
- If you're still S-OFF, you can change your CID to a SuperCID using fastboot (many guides are available at the HTC Sensation forums). Remember to write down your original CID.
- If you're S-ON already, you can create a goldcard using this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ You can get the SD's CID from another Android phone, doesn't have to be yours. Insert the goldcard before flashing the RUU (and keep it in until the process ends), and you should be good to go.

unrooting desire s.

Probably been covered before, but I need help in returning my Desire S to stock asap and also in Laymans terms as I'm new to all this.
I managed to get S off and its running SAGA LBC Mod v0.5.3 Android 2.3.3, sense 2.1
I only have limited access to the internet today so any links would be appreciated as I need it done by tonight.
Thanks in advance.

If you have a 6.98.xxxx hboot
Change your hboot with this one
Download PG88IMG.zip, extract it and use Android Flasher to flash the exctracted hboot.img
The hboot version now should be 0.98.2000
Search in this thread for the proper RUU and install it.
If you have a custom ROM and no info about your original software version the solution is as follows:
Connect the device, enter the bootloader and type the following command in the cmd:
Code:
fastboot getvar version-main
This is the number of your original software.
If this number is higher than the one of your RUU and you cannot flash it, change the number with the version of your RUU (be careful - use the correct RUU for your brand/region!) with misc_version that can be found here - post #1, link from step 1.

Cheers for that. I'll be trying it soon when my daughter goes to bed. Only part that is confusing me is where is the CMD. Probably a total noob question, sorry.

megzilla said:
... where is the CMD. .
Click to expand...
Click to collapse
See the guide in my signature about adb and fastboot - then it will be clear. By the way you will have to follow it too (in order to use the fastboot getvar command)

[Q] HBoot 1.27.000, S-Off... How to install CWM

Hi guys,
I've got a Sensation here that has S-OFF and HBOOT 1.27.0000. From here, can I install CWM or 4EXT recovery? If I can, can someone tell me how or point to a guide?
Thanks
QB

qballds said:
Hi guys,
I've got a Sensation here that has S-OFF and HBOOT 1.27.0000. From here, can I install CWM or 4EXT recovery? If I can, can someone tell me how or point to a guide?
Thanks
QB
Click to expand...
Click to collapse
hi.. just download cmw apk from market and choose the version to be flash. then its download and automatically flash tje recovery. i recommend 4EXT recovery. its having so many features
Sent from my HTC Sensation 4G using XDA App

install rom maneger and let rom maneger install what u whant

Or search xda for the cwm thread and install via bootloader pmg58img file.
Sent from my HTC Pyramid using xda premium

I'm in the same boat as I followed EdyyOS's guide to install ICS OTA. So I have S-OFF and HBOOT 1.27.0000 but I'm not rooted or have CWM. I can't use Rom Manager as I don't have root. When I try to follow this guide http://forum.xda-developers.com/showthread.php?t=1192300 there seems to be something missing as I can't get the recovery to install the CWM files it links to.
Also on HBOOT it says in pink locked but I am S-Off.

I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!

Thanks again Eddy!
---------- Post added at 03:00 PM ---------- Previous post was at 02:48 PM ----------
I see what my problem was now, your android-info.tx files contained modelid: PG5813001. The ones from the guide had modelid: PG5813000. Kept giving me a model ID error.

Get 4Ext Recovery. It's got an amazing amount of features AND it's touch.

Install 4ext recovery control. The application is free and there is on the market. With this application it is very easy to flash 4ext touch recovery.

Conflict?
I have CMW and just installed 4ext. will they have conflict?

4EXT over writes CWM, so no

There will be no problem.

4EXT all the way
Sensational sent from my Sensation.

How to make S-Off with HBOOT 1.27.000?
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?

You can't, stick with your own thread

Try 4EXT recovery. It's so easy to use.

Tantrumxp said:
I have CMW and just installed 4ext. will they have conflict?
Click to expand...
Click to collapse
The CWM app and 4ext apps will not conflict. But you only can flash one of them into your recovery.
Sent from my HTC Sensation XE with Beats Audio using XDA Premium HD app

EddyOS said:
I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!
Click to expand...
Click to collapse
Hi,
I also have a Sensation, HBOOT 1.27.0000, S-OFF but with the pink "LOCKED" statement.
I try to flash the 4EXT recovery you provided, but I get an error message Invalid CID.
Any idea about what I should do?
Many thanks!
K

bertonegt said:
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
Click to expand...
Click to collapse
Well, you can't. You have to root and get it S-OFF before the upgrade to ICS.

EddyOS said:
I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!
Click to expand...
Click to collapse
Thank you EddyOS for the flashable recovery files. Do you have any containing stock recovery for the Sensation ?

[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

[Q] HTC SENSATION got completely stuck on boot (complicated)

correct RUU 3.32.161.11 in post #11
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!

An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation

AndroidSupporter318 said:
An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
Click to expand...
Click to collapse
Well you opened my eyes but still...

C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost

gyrtaz said:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost
http://forum.xda-developers.com/showthread.php?p=26541170
Click to expand...
Click to collapse
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)

ganeshp said:
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)
Click to expand...
Click to collapse
my current non-working version is 3.32.161.52
and the best i could find is 1.24.161...
i can't downgrade and can't put anything custom because i it is SON... so it is dead end for me.
is it possible to put some fake ROM by force (like copying files somewhere or smth...) even if it would not work but which would be seen as an "1.24.161..." when i would try to install it properly?
Just brain storming sorry if i am not telling anything clever...

It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation

AndroidSupporter318 said:
It should be this one: hotfile.com/dl/176652525/e4290a8/RUU_PYRAMID_ICS_Voda-Hutch_AU_3.32.862.13_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
Click to expand...
Click to collapse
i have checked these links you gave before and there was just gingerbread if i try to find exactly by uk wodafone
will try these too... thanks

AndroidSupporter318 said:
It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation
Click to expand...
Click to collapse
Didn't worked out...
How do you think if i unlock the bootloader again is it possible to delete the partition containing OS trough recovery and maybe than having a blank device i would be able to install any version of RUU..? Need some sort of other solution in this situation...

Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation

gyrtaz said:
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!
Click to expand...
Click to collapse
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"

AndroidSupporter318 said:
Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation
Click to expand...
Click to collapse
i think i am able to wipe something if i unlock it again but i have no idea what and what effects it is going to make if i do and if i am not going to delete too much (like HBOOT itself) and stuff like that...
is that way possible at all in my condition? is there any tutorials about doing so?
I just unlocked it again. i have some options..:
wipe data/factory reset
wipe cache
wipe catce + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is deleting something going to make me able of installing gingerbread ruu? (because in theory just this old rom is good to my device)
is there anything useful in this list?

If you do a full wipe that's not going to effect hboot but all your data and the installed rom itself. That means you will not have a usable rom flashed on your phone so it will automatically boot into bootloader. But try to download the ruu I linked and follow the steps. If it doesn't work then we can figure out something else.
Sent from your back garden! Don't look back!

matekaneve said:
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"
Click to expand...
Click to collapse
[RED]OH WOW MATE!!! YOU ARE MY HERO SINCE NOW! EVERYTHING WORKED JUST AS IT SHOULD[/RED]
anyway it is still interesting to me what can you delete with these functions of "4eXT" in the list and if my theory about deleting something and installing gingerbread is right? if yes what should i wipe or format?

When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!

matekaneve said:
When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!
Click to expand...
Click to collapse
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?

gyrtaz said:
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?
Click to expand...
Click to collapse
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app

matekaneve said:
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Come on... I am about learning stuff and knowing. Maybe some day helping someone else. You can tell someone who doesn't really care to not worry instead of telling a short proper answer... sorry i am not trying to be offensive but it was one of the "try using google" sort of answers and that was how i feel about it...
THANKS FOR ALL THE HELP YOU ALL :highfive: