yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] jezash:
Hi,

Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".

I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.

Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.

With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.

I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)

Could anyone advise if there's a way I can get my phone back?

Bootloader text as folows:

*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34

Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

But if I choose Recovery, it just reboots to Bootloader.

Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
[HTC Sensation] malybru:
Hi,

I am not sure where exactly you want to end up.

But if you wanted to get an ICS ROM on your phone,try THIS THREAD

:)
[HTC Sensation] jezash:
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.

Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.

I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.

The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?

Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.

When I tried to flash the 4EXT recovery, I got an error message:

sending 'recovery' (6116 KB)... OKAY [ 1.507s]

writing 'recovery'... INFOsignature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.298s

Does this mean that the unlock hasn't actually worked then?
[HTC Sensation] malybru:
Hi,

Have you got the necessary drivers installed to use ADB.

Try using THIS TOOLKIT

It has the drivers,and an unlock section.

:)
[HTC Sensation] ganeshp:
first of all confirm your CID

fastboot getvar cid command will give you cid

if its supercid (unlikely) or any other which has ICS ROM for it ..then you are lucky

other wise try the HTCdev method again...no need to get the unlock_code again

just use the one you got previously ...then reboot and see..hopefully it works :)
[HTC Sensation] jezash:
hi, thanks for various suggestions.

have tried the HTCDEV method a couple of times without success. I never see the Confirmation Screen shown in step 13 on the HTCDEV bootloader unlock procedure.

Definitely have the HTC drivers installed, have previously used adb successfully from this PC. Plugged in my old HD2 (running Android) and adb devices finds it ok.

Checked my CID as suggested, it's T-MOB005.

Tried downloading the toolkit suggested by malybru and didn't get any further - I think it just does the same thing (runs the HTCDEV unlock process).

One thing that's odd. I tried flashing 4EXT Recovery from command prompt. A "loading" bar showed up on the right side of the screen of the phone like it was working, but then I get the "signature verify fail" shown above.

I guess I can't use Revolutionary S-OFF as I can't boot to Android.

What can I do? Should I try this: http://xdaforums.com/showthread.php?t=1469296 - Edit - actually it seems like that still needs the HTC DEV unlock to work ... which seems to be my problem :-(
[HTC Sensation] jezash:
have tried the HTCDEV unlock method quite a few times now. In the command prompt it appears to work successfully, but I never get the Android-like confirmation screen (I think this must be because my phone will not currently boot to Android).

As I think I need to unlock before I can flash anything else, I am stuck. :-(

Does anyone have a suggestion for another way to unlock it?
[HTC Sensation] jezash:
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
[HTC Sensation] ganeshp:
Can you pop in the irc? We can do some last tries before you send it for repairs

Sent from my pyramid.. Through blazing fast sonic waves
[HTC Sensation] jezash:
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.

thanks for your reply.
[HTC Sensation] ganeshp:
EDIT:based on these values ..seems like something can be done..remember ..this is all to avoid extra money to get it repaired :D

can you post some more details?

fastboot getvar all (except IMEI and SERIAL NO )
[HTC Sensation] jezash:
Hi Ganesh,

Thanks for your reply. Here are the details from my phone:

C:\adb>fastboot getvar all

INFOversion: 0.5

INFOversion-bootloader: 1.27.0000

INFOversion-baseband: 11.22.3504.07_M

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main: 1.34.206.1

INFOserialno:

INFOimei:

INFOproduct: pyramid

INFOplatform: HBOOT-8260

INFOmodelid: PG5813000

INFOcidnum: T-MOB005

INFObattery-status: good

INFObattery-voltage: 4032mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: 617f0a98

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.480s

Cheers
[HTC Sensation] ganeshp:
now that we know that the stock rom flashed .(before brick)

get the 1.50 RUU and try to RUN it

how you do that

phone in fastboot ...connect it to pc and run the RUU.exe

if it still dint worked

then extract the rom.zip form RUU

http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/

then keep the rom.zip in adb folder and flash it manually

manual flash steps

1.fastboot erase cache (if its failing ...ignore it)

2.fastboot oem rebootRUU (black screen with silver HTC)

3.fastboot flash zip rom.zip (pastebin the output if failed)

4.fastboot reboot-bootloader (check the bootloader there ..changed or not )
[HTC Sensation] jezash:
hi ganesh,

latest rom available that i can find (for t-mo uk) is 1.34. That ok?

cheers

EDIT: ok, so trying to run the RUU, it looks like it's going ok, starts sending the ROM to the phone, and then aborts with a ERROR [155]: UNKNOWN ERROR.

Will try the manual steps you gave.
[HTC Sensation] ganeshp:
yes try that first if it fails (both ways )

get the updated RUU

from football ^

and use that and repeat the rom flash again
[HTC Sensation] jezash:
hi ganesh,

ok, here's what came back when i tried to flash manually.

C:\adb>fastboot flash zip rom.zip

sending 'zip' (381007 KB)... OKAY [ 51.085s]

writing 'zip'... INFOadopting the signature contained in this image...

INFOsignature checking...

INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOchecking custom ID...

INFOchecking main version...

INFOchecking hboot version...

FAILED (remote: 44 hboot version check fail)

finished. total time: 103.934s

EDIT:

when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!

will contact football again as you suggested.

2nd EDIT:

my bootloader displays HBOOT-1.27.0000 ... isn't the problem still that even 1.50 has an older HBOOT than this, and hence the rom flash fails?
[HTC Sensation] ganeshp:
yeah thats expected ...can you try one more thing ..can you just remove the hboot.nb0 file from the rom.zip (have a copy of it somewhere safe ..so that you can add later when required)

EDIT: also you need to edit the android-info.txt file ..change the HBOOT inside with te one you have i.e. 1.27.0000 then make the zip again then try flashing it sorry my bad there wont be HBOOT in the android-info.txt ..just cidnum ,modelid etc etc

then do the flash of rom.zip again
[HTC Sensation] jezash:
weird. I couldn't find that file in the rom.

the contents are as shown here

EDIT - oh, duh, the longer file name that ends as you said. sorry. will try now.
[HTC Sensation] jezash:
ok, tried this. unzipped, removed the hboot_Pyramid_8x60_1.17.0011_20110602_signedbyaa.nb0 file, rezipped. followed the four manual flash steps that you suggested, and got the following message in cmd:

C:\adb>fastboot flash zip rom.zip

sending 'zip' (375099 KB)... OKAY [ 50.217s]

writing 'zip'... INFOsignature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 100.357s
[HTC Sensation] jezash:
Football can get me a TMO-UK RUU 1.50. There is a cost, apparently. Hence wondering if there's a reason why 1.50 should work when 1.34 doesn't, give - if i understand correctly - that neither is HBOOT 1.27.
[HTC Sensation] ganeshp:
yes RUU 1.50 wont do any good either ..wait for an answer from dexter then

the thing is during unbricking you used the wrong HBOOT to flash..you should have flashed 1.18 one or 1.17 one

but cant blame you ..as you thought the stock rom flash failed initially (befor unbrick) so you asumed you have AHD 6.5.5 :(

such a bad luck ..but wait ..i dont think ICS Roll out will be that late also dexter might find a working solution before that

the current only and definite solution is to run the ICS RUU of vodaphone UK
[HTC Sensation] jezash:
might have a 3.32-RUU-shaped solution thanks to football... watch this space. would be a *big* relief.
[HTC Sensation] ganeshp:
Wow that's good :D

Sent from my pyramid.. Through blazing fast sonic waves
[HTC Sensation] jezash:
got my phone back. massive relief. HUGE thanks to football for the RUU, dexter for the unbrick, but most of all to ganesh who gave me more time and help than i had any conceivable right to expect. truly humbled once again by the willingness of xda's experts to give their time to help the rest of us. THANK YOU.
[HTC Sensation] neothechosenone:
i'm facing the same problem as mentioned in the 1st post.

i had a custom rom installed and i was facing many fcs and random reboots. Then i thought "hey just going back to stock" so... i searched for a rom, flashed it via recovery, and since then i got nothing.

No android, no recovery, just the Bootloader and fastboot are still working.

Okay. Then i searched 'round a bit and thought it would be easy but whenever i tried to Flash an PG58xxx.img/zip i get errors :(

(bootloader) zip header checking...
FAILED (remote: 32 header error)

(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)

or even

(bootloader) checking main version...
FAILED (remote: 43 main version check fail)

Well then... since i tried everything what i found rount the net, i'm quite exhausted by looking for a solution, and i hope that you could help me :(

Ah and here is my fastboot getvar all

./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) serialno: *************
(bootloader) imei: *************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
[HTC Sensation] ganeshp:
well your case is simpler :)

just get the EUROPE UNBRANDED RUU here ..and connect the phone from bootloader to PC (phone should read fastboot usb after this ) ..and just double cilck the RUU ..let it finish ..once done reboot enjoy :D
[HTC Sensation] neothechosenone:
well.... Signature Verify Fail
[HTC Sensation] ganeshp:
what realy ?? :eek:

do this ..extract the ROM.zip from the RUU ..using this thread (section #4 ->4.1 only)

then inside rom.zip extract the android-info.txt and post the contents of it here
[HTC Sensation] neothechosenone:
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 3.33.401.6
hbootpreupdate:12
DelCache:1
[HTC Sensation] ganeshp:
wow the RUU is matching and its throwing signature failure

do this ..copy the ROM.zip to adb/fastboot folder

then these commands one by one

fastboot erase cache (if failed ignore it)

fastboot oem rebootRUU (black screen with silver HTC )

fastboot flash zip ROM.zip (if failed at any point ..dont kill it if stuck and immediately post the error/output it gave here)

fastboot reboot (try rebooting if the above command flash properly ..at the end it says OKAY if flashed properly )
[HTC Sensation] neothechosenone:
well, already did that, but even there Signature verify failed
[HTC Sensation] neothechosenone:
Okay. Did a few other things...

Changing CID to different value. tried flashing corresponding FW + CWM/4ext/stock Recovery. But nothing worked.... (even recovery keeps rebooting)

it's quite disgusting :'(
[HTC Sensation] timaloud:
Similar problem ?

Hey!

I have the same issue, phone turns on directly to bootloader and i cannot see it as adb device. I've been trying to follow this thread and follow the intructions but i can't seem to make it work.

I the rom.zip to the sd card (after renaming it) and it seemed to work at fist but then failed in the parser stage. so after that i tried to do it directly from fastboot but then i get this error :

C:\Android>fastboot flash zip rom.zip

sending 'zip' (441916 KB)...

OKAY [ 58.642s]

writing 'zip'...

(bootloader) adopting the signature contained in this image...

(bootloader) signature checking...

FAILED (remote: not allowed)

finished. total time: 119.096s

Please help?

here is my phone getvar all:

C:\Android>fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.27.0000

(bootloader) version-baseband: N/A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.32.531.14

(bootloader) serialno: SH18TT513298

(bootloader) imei: 355066049715420

(bootloader) product: pyramid

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PG5810000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 3988mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 617f0a98

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.550s

The only thing that came up different when i followed the instructions it that when i typed the "

C:\Android>fastboot oem rebootRUU" command the device rebooted but went back to white bootloader screen, not the htc screen you mentioned.

And the second time i tried i got this error : C:\Android>fastboot oem rebootRUU

...

(bootloader) [SD_HW_ERR] read data fail in CMD18

(bootloader) [SD_HW_ERR] SD: Read data fail..

(bootloader) [ERR] partition_read_emmc(732): error 2

(bootloader) Start Verify: 3

(bootloader) [SD_HW_ERR] read data fail in CMD18

(bootloader) [SD_HW_ERR] SD: Read data fail..

(bootloader) [ERR] partition_read_emmc(732): error 2

(bootloader) Start Verify: 3

(bootloader) erase sector 130560 ~ 131071 (512)

(bootloader) emmc_erase(1852): sd_write_sector failed!

OKAY [ 0.075s]

finished. total time: 0.075s

Please i've tried so many different things on this. It's been 2 days now of reading threads and trying things out that haven't worked. I know i have no right to expect help but it would be greatly appreciated. cheers
[HTC Sensation] ganeshp:
The sdcard you have is broke or you don't have sdcard it seems..

Try another sdcard and flash the ruu again

Edit: also it seems emmc got corrupted or have bad blocks in which case you have hardware error..

When you ran the ruu directly.. By double clicking the exe did it worked?
[HTC Sensation] timaloud:
In your debt

Thank you so much for answering, you're truly cool!

I'm not sure what an emmc is....bad blocks on the phone memory ??? . I'll try with a different sd card then.

And trying to run the RUU.exe is the first thing i was trying cause it seemed like the simplest but i kept getting error 171, i tried older versions and the one i have on the device right now "supposedly" :D
[HTC Sensation] ganeshp:
Emmc is the internal memory of the phone (the 4gb one)

Btw only one ruu will work for you that is

TMOUS ICS RUU (3.32.531.14 one) rest of ruu's you can ignore them

Run that ruu and tell me if you got any error
[HTC Sensation] timaloud:
error message

Ok so i tried from a different sd card and this is what i get:

After checking zip it says do you wish to install update ?

vol up for yes and i press that and then i get

Parsing...[SD ZIP]

[1] BOOTLOADER -Fail-FU

[2] BOOT -Fail-FU

all the way to

[15]RADIO_CUST -Fail-FU

Partion update fail!

Update Fail!
[HTC Sensation] ganeshp:
Hardware fault it is

The internal memory is corrupted.. Fail-PU error means gone :(
[HTC Sensation] timaloud:
conclusion

Ok, well at least now i understand why i haven't been able to work around it. Ganeshp, i'm really greatful for your help, i'm suprised that there are people such as you who would take your time to help out noobs such as myself. :D

Can the internal memory be purchased and replaced ? And if so is it worth it ?
[HTC Sensation] akashavel:
Hi mate.

If u r s.on then do this steps.

Unlock and flash 4ext recovery and flash superuser zip and if you had taken a nand backup then look for boot.img and flash that boot.img using fastboot command. Also try restoring the nand backup from recovery.

I had same issue with evo4g+.

Thanks.
[HTC Sensation] ganeshp:
Bit worth it imo.. As the repair costs is almost as much as used sensation cost.. But give it a shot... May be JTAGing the device might work which might cost around 40-50$ but you need to find a local repair guy yourself who has the jtag device

Edit:

Also if you can unlock the bootloader and flash 4EXT recovery as the other guy said.. We could try something by ourself.. I once solved one guy Fail-PU error but chances are slim
[HTC Sensation] timaloud:
Hey akashavel,

Thank you for your input, I tried flashing 4ext recovery before, but i'm not sure i did it right cause i don't think it worked, do you know of a thread that could walk me through it ? Oh and is superuser a different method ? I'm sorry, im not so familiar with all of this. Thanks for your patience.

---------- Post added at 10:52 PM ---------- Previous post was at 10:46 PM ----------

Uhr, i have to wait 5 min before posting! Sorry :D

I see, i guess i'll look around and see. For example if i bought the same phone for cheap with a broken screen, could the memory be taken out and exchanged ?
[HTC Sensation] blackwing182:
just send the one you have for gtag, dont spend money on other phones to try fixing the one you have, like i said, fix the one is briked, it happens the same to my ex-sensation, eMMC brik, and i fixed it with gtag
[HTC Sensation] timaloud:
Ok, thanks a lot, i will look into it!

But if there's a chance even if it's slim i'll take it, how do i go about flashing 4ex recovery on it? please can someone give me a walk-through ?
[HTC Sensation] akashavel:
Hi Mate,

Pls chek this link (post#31).

http://xdaforums.com/showthread.php?t=1307336&page=4

You can get the superuser zip from second link.(extract the adb folder and you will find it there)

flash it after doing 4ext recovery.

for 4ext recovery: you get the same in adb folder its an image .

rename recovery_4EXT_1.0.0.5 RC5V1.0.img to recovery_4EXT_1.0.0.5_RC5V1.0.img in adb folder

and flash that image.

once your done. Unlocked / recovery installed and superuser zip . *su-2.3.6.3-EFGH-fixed-unsigned.zip

then if you had taken a nand backup look for boot.img and flash via fastboot command.

cmd: fastboot flash boot boot.img and reboot.

also try restoring the nand backup in recovery.

Note: pls chek on page 6 of the above link ..i had a bricking experience .you can read and refer.

i posted a screenshot on page 7.

thanks
[HTC Sensation] timaloud:
tried it

Hey thanks again for your help everyone, i tried the 4EXT but im getting this:

C:\Folder>fastboot flash recovery recovery_4EXT_1.0.0.5_RC5V1.0.img

sending 'recovery' (6756 KB)...

OKAY [ 2.220s]

writing 'recovery'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 3.933s

I'm guessing it's because my emmc is bad no ?
[HTC Sensation] ganeshp:
no first you need to unlock the bootloader then only you can flash a recovery

for unlocking ..check this http://htcdev.com/bootloader
[HTC Sensation] timaloud:
more explenation

Ok, thank you.

Hey but when i tried this method in the command window it said unlocked, but when the phone reboots it's still says locked.

I hate to keep bothering you, but maybe if you could walk me through the procedure again i can see where i'm going wrong. I have the unlock_code that i received from HTCdev by email so i can try again from there.

Take care!

This is why i get when i flash the token:

C:\Android>fastboot flash unlocktoken Unlock_code.bin

sending 'unlocktoken' (0 KB)...

OKAY [ 0.161s]

writing 'unlocktoken'...

(bootloader) unlock token check successfully

OKAY [ 0.013s]

finished. total time: 0.181s

I've tried it a couple more times and now i get this:

C:\Android>fastboot recovery recovery_4EXT_1.0.0.5_RC5V1.0.img

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache

-s <serial number> specify device serial number

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address

-n <page size> specify the nand page size. default:

2048

HELP PLEASE!

Sorry for being such an amateur.
[HTC Sensation] ganeshp:
the Unlock_code flashed fine ..but the bootloader not showing Unlocked means ..you are out of chances :(

try one last time

flash the token again

fastboot flash unlocktoken Unlock_code.bin

then reboot the bootloader using this command

fastboot reboot-bootloader

if after this the top of bootloader saying LOCKED means ..no more ways to do anyhting im afraid :( (actually when having Fail-PU errors its highly impossible to unlock the bootloader and flash a custom rom ..but lets hope that we are in the 0.00000001% people who got lucky )