Database Info

Have I bricked my Desire S? [SOLVED]

I believe I may have bricked my Desire S also.
I rooted my Desire S through the official HTC method. (I have since relocked)
I then attempted to flash a custom ROM.
The custom ROM (Reaper 2.2) got stuck in (what I believe to be a boot loop) so I attempted to revert to the backup I made - that failed.
I did manage to get CyanogenMod 7 working but with missing functionality
Now I could not get beyond the white HTC screen (or the Black screen with the circle/number pattern on Reaper)
My desire S originally was on Vodafone (Ireland)
Whem I try to load the error is:
SD Checking
Loading...[PG88DIAG.zip]
No image!
Loading...[PG88DIAG.nbh]
No image or wrong image!
Loding...[PG88IMG.zip]
No image!
Loading...[PG88IMG.nbh]
No image or wrong image!
My phone was on 2.3.5 and Sense 3.0
Other details I obtained:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.161.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei:xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I have spent hours upon hours trawling through forums, posts and guides but nothing has worked.
I have tried RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed.exe and got error [170]:device not detected and I have tried from the command line via fastboot....
I really need help here please.
OR is my Desire S totally bricked beyond repair

If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.

eyahl said:
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
Click to expand...
Click to collapse
this and bootloader need to be ****unlocked**** in order to boot custom rom, and ***re-locked*** when installing RUU

Thanks for the reply's guys.
I managed to get the RUU working this evening but the phone was still ***unlocked***... I got some error (didn't make note of it)
I will re-read both posts when I am not so tired and try the suggestions
Thanks again
(I will post my results)

Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom

GSR-James said:
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
Click to expand...
Click to collapse
Did you read what I wrote?? Do what I said or search forum about that if you need more information. It is definitely necessary, you won't succeed without flashing boot.img separately.
Sent by my fingers to your head.

I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
Yes, that's what I meant
Sent by my fingers to your head.

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
YEs that sounds about right, although the full command is
Code:
fastboot flash boot boot.img

Thank you both for the reply's.
I will try this when I sober up in the morning

Now that I am sober I want to thank eyahl, nenad_l and ben_pyett for your input.
I managed to get the rom working last night (drunk and all as I was )
I am now running a MIUI rom
Baseband version: 20.4801.30.0822U_3822.10.08.04_M
I need to ask a couple more questions if I may?
The interface is not what I am used to and don't particularly like it. It reminds me of the UI I had on my old Galaxy I9000. Is this as a result of my kernel version?
Kernel version: [email protected]#1 Thur Oct 6 14:48:57 BST 2011
My understanding of what I have done by flashing the boot.img is that my kernel is that of the rom from where the boot.img was taken and the MIUI rom sits atop - is this correct?
So if I extract a boot.img from a different rom and then flash I will have a different kernel version and subsequently return my UI to (SENSE) that I'm more familiar to?
Sorry for the n00b questions but I am only learning about this at the moment
Thanks guys

No problem, and your understanding is not really correct, the UI is determined by the ROM not the boot image (which is ultimately the kernel), so to get sense back you need to flash a sense ROM like Endy
Every time you flash a new ROM simply flash the associated boot
You shouldn't flash a boot from one ROM under another, it's not mix and match, well that's not completely true.
Swyped form ym Dersie S unsig XAD Permuim

Thanks Ben.
I will look for the 'Endy' rom you suggested.
Ok, so I dl the zip, extract the boot.img, write it from cmd and then flash the rom like normal?
I find it very frustrating to find roms.....almost every time I select a rom to dl I'm redirected to a bad link or to a referral to another referral etc....
If anyone has a source for roms please post it!

Best source for roms is the development section here at desire s xda. Just look through the threads, you will find good quality and stable roms. Endy=endymion ROM
You can look to the index thread, additionally zac made a torrent thread where you can find torrents for the most used roms
Sent by my fingers to your head.

Thanks eyahl
I have dl Endy and will try it now.
I'll have a look where you suggested
Thanks

You must wipe your device (all partitions except sd) prior to each ROM flash
Swyped form ym Dersie S unsig XAD Permuim

Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again

GSR-James said:
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
Click to expand...
Click to collapse
You're welcome
Yes, you can mark the thread solved
Sent by my fingers to your head.

Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!

GSR-James said:
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
Click to expand...
Click to collapse
Go to your first post, click EDIT, then on the edit panel, click on ADVANCED and then modify the topic of your thread by adding [SOLVED] in front of it.
You're done.

[Q] FAILED (remote: not allowed) need a little help

Hello!
Just got my hands on a desire S from someone who said they bricked it, i dont think it is though.
I can access fastboot/HBOOT but it doesnt seem to have a custom recovery installed, shows the stock recovery or download mode logo, the screen goes blank and vibrates 7 times.
Every time i try to flash anything through fastboot it gives me the error in the heading
FAILED (remote: not allowed)
The ROM just doesnt boot and shows T mobile logo indefinitely (must be a bootloop) but the phone doesnt have any Tmo logos on the body.
more details
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
I read about ENG S-off but i dont know what this phone has, maybe its just radio S-OFF cos its Tmo and doesnt have a recovery though i dont understand what the 7 vibrates mean either.
little help please?
even more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.110.3
(bootloader) serialno: HT15TTJ01262
(bootloader) imei: 356708041646975
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0e35ea5b
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

7 vibrations most likely mean overheating, and this can't be cured by any means.
The phone is S-OFF, but doesn't have Engineering HBOOT - so you can't use fastboot, it won't allow you (just what it says).
Your best bet is to try a stock RUU and see if it helps.

Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away

Tectas said:
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone

raheeljessa said:
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
Click to expand...
Click to collapse
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away

even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot

Tectas said:
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot

Ok then try it with a ruu, sry that i took your time for nothing

Tectas said:
Ok then try it with a ruu, sry that i took your time for nothing
Click to expand...
Click to collapse
how do i do that? sorry i seem to know nothing

Do you know from which regions your phone is?
Try in fastboot : fastboot getvar all, and Google your main version then download the appropriate file from this link
http://forum.xda-developers.com/showthread.php?t=1002506

Once you are sure you have the right RUU, you might have to make a goldcard to get rid of the CID error

The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.

Jack_R1 said:
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Click to expand...
Click to collapse
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way

raheeljessa said:
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
Click to expand...
Click to collapse
3 possibilities:
1. Let the ruu run without attached device till the only option is to close the program, search in your temp folder for the rom.zip, copy it to another folder, close the program, copy it to sd and try to flash it the same way you did before with the hboot (rename the rom.zip to PG88IMG.zip before you flash it)
2. Do the same like at 1. but create a goldcard before
3. Do the same I described before with hboot, but create a goldcard before
Swyped because PC is under full load or to far away

If the RUU installer hangs - your chances aren't too good.
If it hangs on "rebooting to bootloader" - boot to FASTBOOT manually and start RUU while in fastboot mode.
If it hangs updating - chances are you're another case of faulty eMMC.

gave the phone to some guy in the market. says he'll take 5£ to open it and check it out and let me know whats wrong.
the RUU rom.zip file when renamed to pg88img.zip or whatever does work as its the only zip file it detects in hboot mode,
it starts the update, heats up like an angry mountain and then sucks its battery off..
thanks you guys for all the help. I'll update you on what was the actual problem when this guy tells me so you know what these symptoms are for in future

Have you tried using the gold card? As it has already been stated that it should get rid of the wrong cid issue.
Sent from my HTC Desire S using XDA

Screen flashing white on boot image

So I was trying to install a custom rom (jelly bam 4.1) and when it hits the flash screen it'll flash white I'd say every second or so. Not to be discouraged, I looked through some threads and saw that since my hboot was 1.4 that I should first flash the boot.img and then reflash my phone. Well now in addition to the rom still flashing white every few seconds I cannot access the bootloader screen, or the recovery screen.. Can someone help me out? Or have I bricked my phone beyond repair?
Thanks

parcel621 said:
So I was trying to install a custom rom (jelly bam 4.1) and when it hits the flash screen it'll flash white I'd say every second or so. Not to be discouraged, I looked through some threads and saw that since my hboot was 1.4 that I should first flash the boot.img and then reflash my phone. Well now in addition to the rom still flashing white every few seconds I cannot access the bootloader screen, or the recovery screen.. Can someone help me out? Or have I bricked my phone beyond repair?
Thanks
Click to expand...
Click to collapse
Nevermind all.. I was able to get it into fastboot so i went ahead and recovered it... any ideas why this happened though? and what i could do to prevent it?
*edit*
So, I think I've yet again made things way worse... long story short.. I think I wipe the os system clean from my phone, with no backup.. I dont even know how to access my phone to put any more files on it so I can flash it back to its factory defaults or anything. I now highly doubt that there is much that i can do, but if anybody has any ideas I'd be more than happy to listen to them...

parcel621 said:
Nevermind all.. I was able to get it into fastboot so i went ahead and recovered it... any ideas why this happened though? and what i could do to prevent it?
*edit*
So, I think I've yet again made things way worse... long story short.. I think I wipe the os system clean from my phone, with no backup.. I dont even know how to access my phone to put any more files on it so I can flash it back to its factory defaults or anything. I now highly doubt that there is much that i can do, but if anybody has any ideas I'd be more than happy to listen to them...
Click to expand...
Click to collapse
Did you OTA update (jb update)
---------- Post added at 04:40 AM ---------- Previous post was at 04:38 AM ----------
parcel621 said:
*edit*
So, I think I've yet again made things way worse... long story short.. I think I wipe the os system clean from my phone, with no backup.. I dont even know how to access my phone to put any more files on it so I can flash it back to its factory defaults or anything. I now highly doubt that there is much that i can do, but if anybody has any ideas I'd be more than happy to listen to them...
Click to expand...
Click to collapse
Oh all you have to do is Flash another Custom Or actually Just download SuperUser .zip when you download it in recovery click mount put the .zip in your SD card and then install and click the folder .

parcel621 said:
Nevermind all.. I was able to get it into fastboot so i went ahead and recovered it... any ideas why this happened though? and what i could do to prevent it?
*edit*
So, I think I've yet again made things way worse... long story short.. I think I wipe the os system clean from my phone, with no backup.. I dont even know how to access my phone to put any more files on it so I can flash it back to its factory defaults or anything. I now highly doubt that there is much that i can do, but if anybody has any ideas I'd be more than happy to listen to them...
Click to expand...
Click to collapse
First off, Jellybam flashes white while booting for the first or 50th time. It's normal that it flashes white. Yes it's odd but it's normal.
You don't have a bricked phone since it turns on. If you can even enter recovery, you should be able to access your backups. If they aren't there, did you do a factory reset outside of recovery? If so, that would wipe your sd card. You may need to format it as well since it got corrupted.
You need to go into recovery and mount your sd card. From there you can load a custom rom on your sd card and I'd also stick flash gui app on there to make it even easier for the next time you flash.
Unmount sd card and and safely remove your phone.
Flash the boot img for Jellybam. Boot it up and let it flash, I've seen people say it flashed for almost 5 minutes before it took. Just be patient. When your rom is set up the way you like it, make a backup. Remember, you need to wipe all cache types, wipe system and do a factory reset INSIDE twrp. You'll be fine. If not, come back here and we will get you straight
Sent from my One X using Tapatalk 2

ronnyg12 said:
Did you OTA update (jb update)
---------- Post added at 04:40 AM ---------- Previous post was at 04:38 AM ----------
Oh all you have to do is Flash another Custom Or actually Just download SuperUser .zip when you download it in recovery click mount put the .zip in your SD card and then install and click the folder .
Click to expand...
Click to collapse
This phone doesn't have an sd card slot on it and my computer doesn't recognize the phone anymore so i dont have a way to put anything on it

parcel621 said:
This phone doesn't have an sd card slot on it and my computer doesn't recognize the phone anymore so i dont have a way to put anything on it
Click to expand...
Click to collapse
its cuz you WIPED YOUR SD CARD! its ok! all you have to do is plug in your phone USB to PC click mount and wait! it takes a while sometimes! then it will open. the foldder will be completely empty but its ok! put the .zip in the folder and click unmount, and then install it !

ronnyg12 said:
its cuz you WIPED YOUR SD CARD! its ok! all you have to do is plug in your phone USB to PC click mount and wait! it takes a while sometimes! then it will open. the foldder will be completely empty but its ok! put the .zip in the folder and click unmount, and then install it !
Click to expand...
Click to collapse
I'd like to thank you about a thousand times over... My phone is now working 100%.. You sire, are a god send! Thank you!

parcel621 said:
I'd like to thank you about a thousand times over... My phone is now working 100%.. You sire, are a god send! Thank you!
Click to expand...
Click to collapse
No problem if you have questions just PM me!

ronnyg12 said:
No problem if you have questions just PM me!
Click to expand...
Click to collapse
Hi ive have this same problem but left it flashing away for an hour. tried reflashing still the same. tried flasing telstra rom that does the same.
now i find the only roms that works so far are telstra 1.81 and 1.89 only wifi now doesnt work and neither does camera. im on hboot 1.14 any help would be really appreciated. thanks

i did the same thing when curious about bootloader factory reset, i just reformatted storage on a windows pc and then reflashed twrp n was able to copy roms back to sd card. scared the crap out of me being i only had phone a week when i screwed it up.

bazclose said:
Hi ive have this same problem but left it flashing away for an hour. tried reflashing still the same. tried flasing telstra rom that does the same.
now i find the only roms that works so far are telstra 1.81 and 1.89 only wifi now doesnt work and neither does camera. im on hboot 1.14 any help would be really appreciated. thanks
Click to expand...
Click to collapse
Sounds like you need to flash the boot img in fastboot
Sent from my One X using xda app-developers app

bazclose said:
Hi ive have this same problem but left it flashing away for an hour. tried reflashing still the same. tried flasing telstra rom that does the same.
now i find the only roms that works so far are telstra 1.81 and 1.89 only wifi now doesnt work and neither does camera. im on hboot 1.14 any help would be really appreciated. thanks
Click to expand...
Click to collapse
Connect your phone to your PC enter fastboot mode open command prompt from the SDK folder (platform tools) and type this. fastboot getvar all
Copy and paste all your info here, take out your serial number if you want.

ronnyg12 said:
Connect your phone to your PC enter fastboot mode open command prompt from the SDK folder (platform tools) and type this. fastboot getvar all
Copy and paste all your info here, take out your serial number if you want.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.20os.32.09.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.42.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4027mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
hope this helps. thanks

Edit out, your imei number!
WR
Injected from My ViperXL

WarRaven said:
Edit out, your imei number!
WR
Injected from My ViperXL
Click to expand...
Click to collapse
Too Late!! MUAAHAAHAHA
Sent from my SPH-L710 using Tapatalk 2

fixed it
18th.abn said:
Too Late!! MUAAHAAHAHA
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
It works now. All I had to do was flash boot image for that ROM as I was on hboot1.14.

Definitely one of those roms that has a funny way of booting first time, but yeah I get the flash too (well, i use to), so no concerns.

[HELP] HTC Sensation 4G Bricked?

Hi all! I have a bricked HTC Sensation 4G (T-Mobile) that I am trying to fix.
I need help with RUUing the HTC Sensation 4G. (Z710e)
I believe I have tried everything, all without luck, please help, TIA.
Heres the problem with the phone- It appears to be stuck in a bootloop, boots up to the white HTC screen, makes the HTC startup chime with Quietly Brilliant written under it, and then immediately reboots, and continuously does this over and over again.
Heres what I know about the phone
The Bootloader is Locked
The Phone is S-ON
The CID of the phone is HTC__621
Here's what I've tried
I have tried RUUing the phone with RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
since it is a T-Mobile HTC Sensation 4G. However I keep getting Error 130: Model ID error.
I also tried RUUing the phone manually using CMD, following the guide however this failed aswell, I kept getting "remote: 12 signature verify fail" at the end.
I also tried renaming extracting the rom.zip from the RUU, renaming that to PG58IMG.zip, placing that on my sd card and booting the phone into bootloader. However when I tried this it said checking PG158.img, but nothing happened, it just continued to boot up to the bootloader.
At this point I realized maybe that this RUU didn't match my CID, which was why it was failing. So I tried opening the ROM.zip file however it said it was corrupt in windows explorer. I then tried redownloading the RUU but it still kept saying ROM.zip was corrupt. I then opening ROM.zip with winrar and it opened up! I then opened android-info.text and saw that the cidnum for the RUU was T-MOB0101. I tried changing this to my CID (HTC__621) and then saving as instructed in this guide, however when I pressed on YES to update the files in the archive, winrar gives an error and says that the archive is corrupt, and does not update android-info.text.
I am not sure what else to try at this point, and I am stumped as to why none of the following methods I've tried worked. Is there something I am doing wrong? Is there anything I'm missing? Any help would be very gladly appreciated, as I am out of ideas.
Also worth noting, I've attached 2 pictures below as attachements to this post, (since I am new to xdadevelopers I cannot post direct links to images), one of the bootloader of the phone, including information such as my hboot version, radio version, etc. in case its needed.
I've also attached a picture below of what happens when I put the phone into HTC stock android recovery and press Factory Data Wipe/Reset. I get a bunch of errors, I'm not sure if this is related to anything but it doesn't look normal, so I attached a picture of it below.
Thanks in advance!

sebzter said:
Hi all! I have a bricked HTC Sensation 4G (T-Mobile) that I am trying to fix.
I need help with RUUing the HTC Sensation 4G. (Z710e)
I believe I have tried everything, all without luck, please help, TIA.
Heres the problem with the phone- It appears to be stuck in a bootloop, boots up to the white HTC screen, makes the HTC startup chime with Quietly Brilliant written under it, and then immediately reboots, and continuously does this over and over again.
Heres what I know about the phone
The Bootloader is Locked
The Phone is S-ON
The CID of the phone is HTC__621
Here's what I've tried
I have tried RUUing the phone with RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
since it is a T-Mobile HTC Sensation 4G. However I keep getting Error 130: Model ID error.
I also tried RUUing the phone manually using CMD, following the guide however this failed aswell, I kept getting "remote: 12 signature verify fail" at the end.
I also tried renaming extracting the rom.zip from the RUU, renaming that to PG58IMG.zip, placing that on my sd card and booting the phone into bootloader. However when I tried this it said checking PG158.img, but nothing happened, it just continued to boot up to the bootloader.
At this point I realized maybe that this RUU didn't match my CID, which was why it was failing. So I tried opening the ROM.zip file however it said it was corrupt in windows explorer. I then tried redownloading the RUU but it still kept saying ROM.zip was corrupt. I then opening ROM.zip with winrar and it opened up! I then opened android-info.text and saw that the cidnum for the RUU was T-MOB0101. I tried changing this to my CID (HTC__621) and then saving as instructed in this guide, however when I pressed on YES to update the files in the archive, winrar gives an error and says that the archive is corrupt, and does not update android-info.text.
I am not sure what else to try at this point, and I am stumped as to why none of the following methods I've tried worked. Is there something I am doing wrong? Is there anything I'm missing? Any help would be very gladly appreciated, as I am out of ideas.
Also worth noting, I've attached 2 pictures below as attachements to this post, (since I am new to xdadevelopers I cannot post direct links to images), one of the bootloader of the phone, including information such as my hboot version, radio version, etc. in case its needed.
I've also attached a picture below of what happens when I put the phone into HTC stock android recovery and press Factory Data Wipe/Reset. I get a bunch of errors, I'm not sure if this is related to anything but it doesn't look normal, so I attached a picture of it below.
Thanks in advance!
Click to expand...
Click to collapse
You can access bootloader so no problems here. Unlock bootloader through htcdev. In fastboot mode flash latest 4ext recovery, enable smartflash in settings, then flash a custom rom. You can also try Android Revolution HD rom if you prefer a stock look.

matekaneve said:
You can access bootloader so no problems here. Unlock bootloader through htcdev. In fastboot mode flash latest 4ext recovery, enable smartflash in settings, then flash a custom rom. You can also try Android Revolution HD rom if you prefer a stock look.
Click to expand...
Click to collapse
Thanks for the info! However I just tried unlocking the bootloader through htcdev but I keep getting an error at the end "Unlock token check failed". You can see this in the picture I attached below of the command prompt window. Any ideas? I tried resubmitting my unlock token on htcdev to make sure I didn't leave any extra spaces or anything but still got the same result. Thanks

sebzter said:
Thanks for the info! However I just tried unlocking the bootloader through htcdev but I keep getting an error at the end "Unlock token check failed". You can see this in the picture I attached below of the command prompt window. Any ideas? I tried resubmitting my unlock token on htcdev to make sure I didn't leave any extra spaces or anything but still got the same result. Thanks
Click to expand...
Click to collapse
Strange... Make sure you copy and paste right from the beginning to the end. You can also try to move your adb/fastboot folder somewhere else for example to the desktop and try resubmitting the token from there. (Might sound stupid but works sometimes). If not, you need to find the right RUU for your device and RUU it, then follow this guide for s-off: http://forum.xda-developers.com/showthread.php?p=26280760 there are some devices htcdev unlock doesn't work unfortunately... Otherwise I have no other idea, sorry. Somebody might be able to help.

matekaneve said:
Strange... Make sure you copy and paste right from the beginning to the end. You can also try to move your adb/fastboot folder somewhere else for example to the desktop and try resubmitting the token from there. (Might sound stupid but works sometimes). If not, you need to find the right RUU for your device and RUU it, then follow this guide for s-off: http://forum.xda-developers.com/showthread.php?p=26280760 there are some devices htcdev unlock doesn't work unfortunately... Otherwise I have no other idea, sorry. Somebody might be able to help.
Click to expand...
Click to collapse
Thanks again for your response, I just did it again this time with my fastboot folder on the desktop, however I still got the same error. How would I find the right RUU for my device? It is an american HTC Sensation 4G from T-Mobile with its CID: HTC__621. I haven't been able to find another RUU for it other than the one I used as previously mentioned in my original post. If anyone has the link to the right RUU I could use for this device, it would be really helpful. Thanks again.

sebzter said:
Thanks again for your response, I just did it again this time with my fastboot folder on the desktop, however I still got the same error. How would I find the right RUU for my device? It is an american HTC Sensation 4G from T-Mobile with its CID: HTC__621. I haven't been able to find another RUU for it other than the one I used as previously mentioned in my original post. If anyone has the link to the right RUU I could use for this device, it would be really helpful. Thanks again.
Click to expand...
Click to collapse
Could you write here the info you get for the command "fastboot getvar all"

matekaneve said:
Could you write here the info you get for the command "fastboot getvar all"
Click to expand...
Click to collapse
Yes, here it is
Code:
(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.709.6
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(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.562s

sebzter said:
Yes, here it is
Code:
(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.709.6
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(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.562s
Click to expand...
Click to collapse
Your firmware version (3.33.709.6) is an Asian one. Try downloading this ruu and run it: http://androidruu.com/getdownload.p...0U_11.24A.3504.31_M_release_266490_signed.exe
Edit: and delete your serial and imei number from your post!

matekaneve said:
Your firmware version (3.33.709.6) is an Asian one. Try downloading this ruu and run it: http://androidruu.com/getdownload.p...0U_11.24A.3504.31_M_release_266490_signed.exe
Edit: and delete your serial and imei number from your post!
Click to expand...
Click to collapse
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?

sebzter said:
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?
Click to expand...
Click to collapse
Well, I'm out of ideas now. At least the ruu worked. Try maybe the htcdev unlock again now. Get a new token and submit that. And go for the normal sensation option on htcdev site and NOT for the 4g

sebzter said:
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?
Click to expand...
Click to collapse
UPDATE!! I just got the phone to sorta bootup once! It booted up to a configuring android screen (in japanese) and then it shut right off, and started rebooting again. Why is the phone constantly and randomly rebooting like this? I've heard some people said it was the battery but the battery seemed to hold a fairly long charge in bootloader mode, so I don't see why this would be the issue. Anyways I will try an htcdev unlock now and see if that works, will update soon.

Bootloop - unable to get to recovery - maybe no OS?

Folks, 7 rooted devices over last 7 years, and I have usually been able to find a solution without having to start a new thread... however, this time... I better get an expert opinion.
Essentially, here are the facts... I was flashing a rom yesterday on my wife's m8, and the wifi would not work. I thought about it, and then figured it likely was that I had not updated to latest TWRP prior to flashing. So I restored an old backup, I think the one I made right after rooting, which was 1.5 yrs ago, maybe more. That flashed fine, except after many tries via many methods, I could not get TWRP updated, and in fiddling around, I clicked update software, which downloaded the Verizon kitkat update, and started installing it... that was a mistake, finger too fast notwithstanding... I did not need to do it at all, since I was going to flash something new anyway right after updating recovery. Anyway phone appeared to be stuck, I powered it off (Vol up + Power) and went into bootloader (Vol down while it powered up) to go back into recovery and start over. However, the phone went into a boot loop and has since given me much grief over the past few hours.
Output from getvar all is below. It appears to be missing the OS - which kind of makes sense, if I interrupted it midway through something. The phone neither boots, and refuses to enter recovery - even after flashing recovery using fastboot as well as the Hasoon All in One tool. I also cleared cache. I suspect the recovery is loading, but is hidden behind the boot loop screen (is that possible? not sure, just a guess) because the phone has haptic feedback where the TWRP buttons would be - FWIW.
What should my next steps be? Please advise...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: dottat was here
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: ###
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s

First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.

cntryby429 said:
First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.
Click to expand...
Click to collapse
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'

montropistic said:
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'
Click to expand...
Click to collapse
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk

dottat said:
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.

montropistic said:
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.
Click to expand...
Click to collapse
could be a bad download of the RUU

andybones said:
could be a bad download of the RUU
Click to expand...
Click to collapse
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?

montropistic said:
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?
Click to expand...
Click to collapse
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103

andybones said:
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?

montropistic said:
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?
Click to expand...
Click to collapse
Either way works the same - which one your more comfortable with.

andybones said:
Either way works the same - which one your more comfortable with.
Click to expand...
Click to collapse
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...

montropistic said:
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...
Click to expand...
Click to collapse
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK - Yeah - it is running very nice right now, Clean Rom loaded fine, and all systems seem ok. However, per your advice, I will run the RUU again. FWIW, I had grabbed the version with the patch.

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, so I finally got around to this. I ran the RUU again, and got a fail on Userdata, and finally the same message at the end, partition update failed - power to reboot.
I let the phone boot, and then ran the RUU again, by straightaway going back into bootloader. This time, no fails, everything went through as per spec.
Thanks for insisting on re RUU. Seems like something was off, and iterating over it cured it finally. You rock, dottat.