Database Info

problems with flashing PG58IMG.zip

I just used htcdev.com to get s-off on my HTC Sensation then if i try to flash PG58IMG.zip I get "Model ID incorrect"

You weren't supposed to unlock that way u should have used revolutionary
Anyways u did go into bootloader to do this right?
Sent from my HTC Sensation Z710e using XDA Premium App

I'm having the same problem here. Model ID is incorrect error. I used HTCdev as well to unlock. But mine also still says S-on.
Sent from my HTC Sensation 4G using xda premium

If I'm correct htcdev won't actually give you full s-off. It's only a partial unlock. If possible try to unlock with revolutionary. I don't see why people use the htcdev when we've already done it.

What PG58IMG are you flashing? Full ROM or something else? More information required!!

use revolutionary to get s-off then flash PG58IMG in hboot

EddyOS said:
What PG58IMG are you flashing? Full ROM or something else? More information required!!
Click to expand...
Click to collapse
I used this PG58IMG provided here http://forum.xda-developers.com/showthread.php?t=1192300
Now when i try to use the revolutionary S-off method it says wrong device with my drivers and such. I'm lost.

Shall we try.... if you install the latest stock ruu and then try to use revolutionary, that might help as you'd flash the hboot which is in the ruu, thus revert back to the original condition of the phone for which the revolutionary tool is designed.
Give it a shot and post back
and install the relevant ruu for your device (unbranded/branded) and if it doesn't work try to flash it trough fastboot

freakzone said:
Shall we try.... if you install the latest stock ruu and then try to use revolutionary, that might help as you'd flash the hboot which is in the ruu, thus revert back to the original condition of the phone for which the revolutionary tool is designed.
Give it a shot and post back
and install the relevant ruu for your device (unbranded/branded) and if it doesn't work try to flash it trough fastboot
Click to expand...
Click to collapse
Tried doing SUPERCID. And i get his error and will not change my CID:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.094s]
finished. total time: 1.094s

Put the zip on ur sd card -go into fastboot... wanna update-yes. U want to update ur radio... right ?

chiligamba said:
Put the zip on ur sd card -go into fastboot... wanna update-yes. U want to update ur radio... right ?
Click to expand...
Click to collapse
Yup. Done that but it gives me a Model ID incorrect error once i try to update it.

Same problem with HTC S-off.

illuminarias said:
If I'm correct htcdev won't actually give you full s-off. It's only a partial unlock. If possible try to unlock with revolutionary. I don't see why people use the htcdev when we've already done it.
Click to expand...
Click to collapse
Perhaps because we don't want to send phone identifier information to revolutionary to get a beta key.

[SOLVED] Please help *Security Warning* in Hboot

Hi please could somebody help me, I have a Desire S which I got on contract from 02 with a 02 branded rom on there originally and hboot 0.98.0002.
I had S-off, 4ext recovery, upgraded to hboot 2.00.0002 and a custom rom installed.
I have flashed a offical RUU RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe
and now I am stuck in hboot and it says **security warning** hboot version 0.98.000
I tried to flash the above o2 RUU again but it says bootloader version error, So I tried RUU 1.28, 1.47 and 2.10 with a gold card in the phone but the same error all the time.
I have also extracted the rom.zip from each of these and put it onto the goldcard renamed to PG88IMG.zip but then this says MAIN VERSION OLDER and will not flash.
Now I am really stuck on what I need to do, do I need to flash a 0.98.0002 hboot? as at the momment I have 0.98.000, if so how can I do this?
I have lost 4ext recovery, and back to S-On.
If anyone has any ideas I would be really grateful.
Thank you in advance
Cheers
edit: I think the bootloader I currently have on the phone 0.98.000 is incorrect ? , it should be 0.98.0000 or 0.98.0002? . As the hboot is S-ON is there anyway I can flash a hboot through using adb, or does it have to be S-OFF, if so is there anyway I can S-OFF in bootloader or fastboot alone, as I can't do anything else.

I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.

amidabuddha said:
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
Click to expand...
Click to collapse
Hi thanks for your reply, I currently have 0.98.000 hboot on the phone now which is S-ON. My gold card seems to be working as it doesn't say any CID errors.
How can I tell if my device is bricked?
I can only get into hboot, and fastboot/stock recovery. The phone won't do anything else and I can't flash any rom as it says about the bootloader version, but on the bootloader it says **security warning** at the top. Is there anyway I can flash a newer hboot? or won't it let me as it is S-ON, if its S-ON will I be able to flash a hboot or even 4ext recovery to flash a rom?
If so how can I s-off just using bootloader and fastboot?
I thought goldcard is only to bypass the CID checks so you can flash a debranded RUU.

It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.

amidabuddha said:
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
Click to expand...
Click to collapse
Hi, I have done the fastboot commands you said and below are the numbers I got:
fastboot devices - serial number which came up is: HT15NTJ00403
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Thank you for your help with this

Try to put last rom.zip on sdcard with PG88IMG.zip name from version 2.10.401.8 RUU and maybe you will have new hboot 2.00.2002 and then have to unlock hboot from http://htcdev.com/.

first_damned said:
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Click to expand...
Click to collapse
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.

amidabuddha said:
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
Click to expand...
Click to collapse
Hi, I have tried RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe using the RUU on the laptop and tried extracting the rom.zip, renaming as PG88IMG.zip and flashing off sd card (goldcard), but the RUU said bootloader version error and flashing the PG88IMG.zip says main version older error.
There isn't a 2.10.401.4 version, but there is a
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed.exe
I would of thought the 2.10.401.8 should of worked?
also would I be able to flash a hboot being S-ON do you think?
I'm not sure how low my battery is also, If I plug it into the charger will it charge the phone on the bootloader do you know?
Thanks

All version info
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 11.10.401.4
INFOserialno: HT15NTJ00403
INFOimei: 356708041449842
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 3851mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!

Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.

amidabuddha said:
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
Click to expand...
Click to collapse
Hi there, I have tried adb devices but it doesn't come up with my device which is strange. Maybe because my device is S-ON?
Do you think if I took it to a mobile repair shop and had it jtagged to restore original software would do the trick?
thanks

Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.

amidabuddha said:
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
Click to expand...
Click to collapse
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?

first_damned said:
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
Click to expand...
Click to collapse
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.

amidabuddha said:
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
Click to expand...
Click to collapse
I can't get adb to see the device, fastboot will do though but won't flash hboot, it says remote signature fail.
Looks like im going to have to send the phone off to be J Tagged. I have found a shop that does this for £24.99 and they know there stuff.
But if anyone has anymore ideas please let me know.
Thank you amidabuddha for your help, I will keep you updated on any progress.
Simon

You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium

poppy8x said:
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?

first_damned said:
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
Click to expand...
Click to collapse
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium

poppy8x said:
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?

first_damned said:
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
Click to expand...
Click to collapse
Yeah. All worked. Look at my sig.
A month ago, i had "sercurity warning" too (i run RUU 1.48). Gold card coudn't do anything. And then i s-off by xtc-clip (in 5 mins)
Sry for my english bad.
Sent from my HTC Desire S using xda premium

[Q] Can't get S-OFF on T-Mobile NL Sensation

Hi people,
I have unlocked my Sensation's bootloader (through HTCDEV) and am keen to play with ICS (and other ROMs) on it. I have T-Mobile NL branded Sensation. The fastboot screen has the following information on it:
Code:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
I have tried quite a few things:
It seems the revolutionary.io tool does not work on my phone. It keeps telling me it failed to get root. I have tried in Windows (with the older drivers) and Linux (Ubuntu 11.10), neither works.
I have tried to follow this guide: "the-best-easiest-and-safest-way-to-root-and-s-off-the-htc-sensation-tutorial" (I can't post URLs)
However, it fails at the step installing Clockwork Recovery with an invalid CID error.
I have scoured the web, done more Google searches than you can shake a stick at and I'm still stuck.
The phone is most likely SIM locked, the CID is T-MOB003.
I also tried to just modify the secureflag with fastboot to no avail:
Code:
d:\temp\android>fastboot oem readsecureflag
...
(bootloader) secure_flag: 3
OKAY [ 0.008s]
finished. total time: 0.011s
d:\temp\android>fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.086s]
finished. total time: 1.087s
I'm all out of ideas but would love to know if anyone else managed to get it working on their HTC Sensation.
Thanks in advance,
Xander

When you say Revolutionary says it's not got root what exactly does it say?
EDIT: If you're unlocked just flash a new recovery using fastboot, it should now work
fastboot flash recovery <filename>.img

EddyOS said:
When you say Revolutionary says it's not got root what exactly does it say?
Click to expand...
Click to collapse
It says "Failed to get root ". Not terribly informative but it gives me the same error on Linux -and- Windows, so at least it's consistent.
Edit (I can only post one reply every 5 mins)
EddyOS said:
When you say Revolutionary says it's not got root what exactly does it say?
EDIT: If you're unlocked just flash a new recovery using fastboot, it should now work
fastboot flash recovery <filename>.img
Click to expand...
Click to collapse
Which recovery image should I use? This one?
recovery-clockwork-5.0.2.0-pyramid.img from clockworkmod.com/rommanager ?
Thanks in advance,
Xander

Same here, also a HTC Sensation T-mobile NL.
I think i have about tried everything too.
In the beginning i thought the tool that was published by HTC (HTCdev) would root the phone but that was too good to be true.
I've tried several ways to root my phone, tried revolutionary, HTC super tool, z4root, gingerbreak, superoneclick. They all about said the same.
For example when i used HTC super tool, and i choose option 4 (trying to set the device to S-OFF) i get the following message:
Code:
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.13-g1e13373
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module failed to load: Operation not permitted
Druk op een toets om door te gaan. . .
And when i try option 3 (perma root) i get the following message.
LINK: imageshack.us/photo/my-images/11/rootfailed.png/

Is this the guide I should follow to flash the new recovery onto the Sensation?
http://forum.xda-developers.com/showthread.php?t=1242942
The ROM mentioned there is an earlier version than the one on the Clockwork page: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-pyramid.img
Which would one would be best to use?
- Xander

I have the same problem.
I have had the OTA update from 1.45.xxx to 1.50.114.xx now on my phone did you get that update as well? I think that is the problem, and there are no RUU's as far as I can see the will work for the T-mob NL 003 CID.
I will follow your post hopefully some one will find the solution soon.

Andrew-HTC said:
I have the same problem.
I have had the OTA update from 1.45.xxx to 1.50.114.xx now on my phone did you get that update as well? I think that is the problem, and there are no RUU's as far as I can see the will work for the T-mob NL 003 CID.
I will follow your post hopefully some one will find the solution soon.
Click to expand...
Click to collapse
Me too going thru same problems...and followings ur post(Andrew HTC)......hope somebody gets a solution
Sent from my HTC Sensation Z710e using xda premium

gre8 buddy
gre8 buddy..really like your work..kepp it up

soulvayne said:
Same here, also a HTC Sensation T-mobile NL.
I think i have about tried everything too.
In the beginning i thought the tool that was published by HTC (HTCdev) would root the phone but that was too good to be true.
I've tried several ways to root my phone, tried revolutionary, HTC super tool, z4root, gingerbreak, superoneclick. They all about said the same.
For example when i used HTC super tool, and i choose option 4 (trying to set the device to S-OFF) i get the following message:
Code:
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.13-g1e13373
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module failed to load: Operation not permitted
Druk op een toets om door te gaan. . .
And when i try option 3 (perma root) i get the following message.
LINK: imageshack.us/photo/my-images/11/rootfailed.png/
Click to expand...
Click to collapse
try that htcsupertool from 1st and 2nd then 4th :/
Sent from my HTC Sensation 4G using XDA App

Still havent got the phone to S-off.
Aperantly the software that the dutch T-Mob sensations get is based on the EU HTC software but then T-Mob fill it with rubbish and encrypt it with there own security functions. thats why the version numbers come up as ( 1.50.114 ) rather than the standard 1.50.401 EU versions etc
The Dutch T-mob sensations are branded but not simlocked, at least mine isn't simlocked.
I now am weighting for the XDA sensation unbrick method to come alive ( noob frendly version ) perhaps there will be a work around for our specific problem via the unbrick methode.

Guys - it's not possible yet to get a proper S-Off when we are at bootloader 1.27, the HTCDEV only unlocks certain areas of the phone. It will allow you to root the phone, but as to my knowledge it wont allow you to install custom roms.
I've found this thread, where they claim that they can propperly S-OFF the 1.27 bootloader. So we just have to wait, and I really hate to wait, until that guide is up.

Oh cool! Here's hoping it appears soon
- Xander

HTC Sensation Tmobile can't S-Off
HTC Sensation 4G (pyramid-1.18.0000, Android: 2.3.4, ROM version: 1.50.531.1)
I have HTC sensation 4g Tmobile. I unlocked the bootloader using HTCDEV. I struggled to root. I used HTC all in one, KGS utility, easy unlock tool.
I was finally able to root using fastboot to install custom recovery and intall a signed version of super user.
I've then tried to obtain S-Off but revolutionary sstates it's unable to root, KGS states the same thing.
I used root checker on the market to determine whether I was rooted it said it was.
I basically want to S-Off then unlock the sim card to ise on another network.
help will be appreciated

S-OFF htc sensation
engines12 said:
HTC Sensation 4G (pyramid-1.18.0000, Android: 2.3.4, ROM version: 1.50.531.1)
I have HTC sensation 4g Tmobile. I unlocked the bootloader using HTCDEV. I struggled to root. I used HTC all in one, KGS utility, easy unlock tool.
I was finally able to root using fastboot to install custom recovery and intall a signed version of super user.
I've then tried to obtain S-Off but revolutionary sstates it's unable to root, KGS states the same thing.
I used root checker on the market to determine whether I was rooted it said it was.
I basically want to S-Off then unlock the sim card to ise on another network.
help will be appreciated
Click to expand...
Click to collapse
In the end i managed to get my phone S-OFF, i managed to do it with juopunut bear method.
It took me a while to get the wire-trick right but its worth it since i can about flash anything i want.
You can find the guide i used here: http://forum.xda-developers.com/showthread.php?t=1614617

soulvayne said:
In the end i managed to get my phone S-OFF, i managed to do it with juopunut bear method.
It took me a while to get the wire-trick right but its worth it since i can about flash anything i want.
You can find the guide i used here: http://forum.xda-developers.com/showthread.php?t=1614617
Click to expand...
Click to collapse
he has 1.18 hboot version(gb firmware)
he needs revolunionary.io method to S-OFF not juopunutbear method
engines12 did you try just to S-OFF with revolutionary?

Unable to s-off
rzr86 said:
he has 1.18 hboot version(gb firmware)
he needs revolunionary.io method to S-OFF not juopunutbear method
engines12 did you try just to S-OFF with revolutionary?
Click to expand...
Click to collapse
Yes. I get the error, failed to root.

Got that too. That is why i tried juopunutbear, but i have bootloader 1.27, i don't know if there is a way for juopunutbear to work on 1.18.
But if rzr86 says it will not work i'm not the one to disaggree with him because i don't have enough knowledge to confirm that.
I can only say it did work for me.

engines12 said:
Yes. I get the error, failed to root.
Click to expand...
Click to collapse
it is really strange
i can't think something else right now
do you want to go for jb S-OFF?
but i don't know if it works for your hboot version
another way is to upgrade officially or via ruu.exe
then you can use the jb S-OFF
but just to know it is a bit harder with jb S-OFF

rzr86 said:
it is really strange
i can't think something else right now
do you want to go for jb S-OFF?
but i don't know if it works for your hboot version
another way is to upgrade officially or via ruu.exe
then you can use the jb S-OFF
but just to know it is a bit harder with jb S-OFF
Click to expand...
Click to collapse
is there any way to perform S-off from the terminal emulator because the error I get is "access denied" anytime temp root is attempted.
Can I use the revolutionary tool with custom recovery? I have Clockworkmod Touch Recovery 5.8.0.9

engines12 said:
is there any way to perform S-off from the terminal emulator because the error I get is "access denied" anytime temp root is attempted.
Can I use the revolutionary tool with custom recovery? I have Clockworkmod Touch Recovery 5.8.0.9
Click to expand...
Click to collapse
you can't do S-OFF from terminal
and what do you mean by ''revolutionary tool with custom recovery''?

[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: