[UNBRICK] HTC Unbricking Project

Did this work?

  • Total voters
    537
Search This thread
By:
Advanced…
Kohr-Ah

Kohr-Ah

Senior Member
Jan 21, 2011
3,159
2,447
Chicago
AngryB said:
Is it possible back bootloader to LOCK on hboot 1.27 S_ON after htcdev UNLOCK... need for warranty back?
Click to expand...
Click to collapse

The problem with HTC Unlock is one of the ways they can tell if you did it or not is your CID will respond with blank when the getvar command is performed.

I dont know if there is a way to get it relocked and programmed with a CID without the ability to do a oem writecid command.
 
  • Like
Reactions: AngryB
Hawke84

Hawke84

Senior Member
Jan 14, 2010
3,330
1,189
Worthing, UK
AngryB said:
Is it possible back bootloader to LOCK on hboot 1.27 S_ON after htcdev UNLOCK... need for warranty back?
Click to expand...
Click to collapse

kinda the wrong forum but i'll answer anyway.
if your device is S-on then no, you'll need to S-off your device (currently cant on your hboot) otherwise if your S-off you should be able to follow the S-on guide and reflash an RUU with locked bootloader and hboot etc.
hope this helps

Sent from my Transformer Prime TF201 using XDA Premium HD app
 
  • Like
Reactions: AngryB
A

AngryB

Senior Member
Feb 22, 2012
357
34
trkaaa said:
  • originally it shows " Locked "
  • after you unlock it shows " unlocked "
  • after lock it back , it shows " Relocked " , it will not display " locked " anymore
Click to expand...
Click to collapse

sooooo...I lost my warranty forever :(



I am very sad now ... I have a sensation that can not be s-off, I have a sensation that is not even a year old with no warranties, and for all that I'm wrong.. :(((((
 
Hawke84

Hawke84

Senior Member
Jan 14, 2010
3,330
1,189
Worthing, UK
AngryB said:
sooooo...I lost my warranty forever :(



I am very sad now ... I have a sensation that can not be s-off, I have a sensation that is not even a year old with no warranties, and for all that I'm wrong.. :(((((
Click to expand...
Click to collapse

yeah unlocking via htcdev they keep track of your serial number. its in all the info you have to accept before doing it

Sent from my Transformer Prime TF201 using XDA Premium HD app
 
T

trkaaa

Senior Member
Feb 13, 2010
924
895
AngryB said:
sooooo...I lost my warranty forever :(



I am very sad now ... I have a sensation that can not be s-off, I have a sensation that is not even a year old with no warranties, and for all that I'm wrong.. :(((((
Click to expand...
Click to collapse

  • when you unlock using htc dev , your serial number or IMEI is registered by them
  • i don't know if use super tool to lock , it would gave you lock or relock
  • i read once in htc dev that unlock boot loader may ( not will ) void your warranty
  • in another place in the same site , that this will void your warranty
  • this was a very long time ago , and i don't recall now where ( at what action you do ) they choose may or will
  • in my openion , that indicates that it up to them to decide if the defect is due to unlocking the bootloader or it is a defect due to htc
  • ( example dust under screen ) has nothing to do with unlocking bootloader , so here the word "may void your warranty " comes i guess
  • if for example some thing go wrong with hardware due to kernel you installed ( kernel affects the hardware ) after unlocking bootloader , then this brings the word " this will void your warranty "
  • so , please go to htc dev site and read carefully where they use the word " may or will "
  • i don't know if use super tool to unlock bootloader , it would take you to htc dev to register your device there or not ?
 
  • Like
Reactions: AngryB
A

AngryB

Senior Member
Feb 22, 2012
357
34
trkaaa said:
  • when you unlock using htc dev , your serial number or IMEI is registered by them
  • i don't know if use super tool to lock , it would gave you lock or relock
  • i read once in htc dev that unlock boot loader may ( not will ) void your warranty
  • in another place in the same site , that this will void your warranty
  • this was a very long time ago , and i don't recall now where ( at what action you do ) they choose may or will
  • in my openion , that indicates that it up to them to decide if the defect is due to unlocking the bootloader or it is a defect due to htc
  • ( example dust under screen ) has nothing to do with unlocking bootloader , so here the word "may void your warranty " comes i guess
  • if for example some thing go wrong with hardware due to kernel you installed ( kernel affects the hardware ) after unlocking bootloader , then this brings the word " this will void your warranty "
  • so , please go to htc dev site and read carefully where they use the word " may or will "
  • i don't know if use super tool to unlock bootloader , it would take you to htc dev to register your device there or not ?
Click to expand...
Click to collapse


wauu...Thank you very much for lengthy response, you are rock :)

All I did was I went to page www.htcdev.com and followed tutorial ''unlock tutorial'' nothing else:)
 
M

masands

Senior Member
Apr 15, 2010
78
4
Hawke84 said:
depends if they bother to do any checks or if they just JTAG it to reflash or replace the mainboard. If you say it was during an OTA update you might get lucky... up to you if u want to risk it. if they find its user caused damage they might charge you for it...
Click to expand...
Click to collapse

Hmmm ok. But here in Australia HTC contracts Vodafone to repair it (and Vodafone actually contracts someone else). So the guys that do the actual repairing, are not just HTC specialists. They also repair Samsung, Nokia etc.

So what do you think the chances are those guys will probably detect it?
 
S

selectodude

Senior Member
Apr 7, 2010
69
14
Los Angeles, CA
masands said:
Hmmm ok. But here in Australia HTC contracts Vodafone to repair it (and Vodafone actually contracts someone else). So the guys that do the actual repairing, are not just HTC specialists. They also repair Samsung, Nokia etc.

So what do you think the chances are those guys will probably detect it?
Click to expand...
Click to collapse

I've sent multiple S-OFF'd HTC phones in for warranty repair without issue. All have been unrelated hardware issues.

However, if you brick your phone, or have software issues, I have a feeling they'll send you back an unrepaired phone.
 
M

masands

Senior Member
Apr 15, 2010
78
4
selectodude said:
I've sent multiple S-OFF'd HTC phones in for warranty repair without issue. All have been unrelated hardware issues.

However, if you brick your phone, or have software issues, I have a feeling they'll send you back an unrepaired phone.
Click to expand...
Click to collapse

Well according to Vodafone repair tracking service this is what I have got:

1) "Device in transit to service centre"
2) "Assessing your device for repair"
3) "We are waiting for parts to complete the repair of your device"

So I think it may have gotten through...*fingers crossed*
 
J

justsahid

Senior Member
Jun 19, 2011
115
6
Guys,

I have one htc sensation with hboot 1.23.0000 S-on and unlocked bootloader
Am able to install any recovery like cwm or extTouch

Have been trying to install with no success have tried multiple ics roms none of them worked,
only rom worked was realstockexperience with android 2.3.3 in which browser doesn't work

Can anybody suggest which rom can work for me

Sent from my Desire HD using XDA
 
dexter93

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,607
2,341
justsahid said:
Guys,

I have one htc sensation with hboot 1.23.0000 S-on and unlocked bootloader
Am able to install any recovery like cwm or extTouch

Have been trying to install with no success have tried multiple ics roms none of them worked,
only rom worked was realstockexperience with android 2.3.3 in which browser doesn't work

Can anybody suggest which rom can work for me

Sent from my Desire HD using XDA
Click to expand...
Click to collapse

Get a ruu with the 1.23 hboot in and flash it, or ask one of the rom chefs that may have such a build on their archive or wait for JuopunutBear. These are your options

Sent from my HTC Sensation using XDA
 
  • Like
Reactions: Kohr-Ah
dexter93

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,607
2,341
pirlano said:
@dexter93: just sent you a little donation :) thank you man!!!
Click to expand...
Click to collapse

Thank you pirlano.. much appreciated :)

@Lyoth: didn't have a chance to take a look at it yet, I'll let you know.. but it doesn't look pretty bad.. should be easily fixed

Sent from my HTC Sensation using XDA
 
Last edited:
Hawke84

Hawke84

Senior Member
Jan 14, 2010
3,330
1,189
Worthing, UK
dexter93 said:
Thank you pirlano.. much appreciated :)

@Lyoth: didn't have a chance to take a look at it yet, I'll let you know.. but it doesn't look pretty bad.. should be easily fixed

Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse

I had a quick look but don't know what a good one looks like. Seems.to be lots of writing timeout?

Sent from my HTC Sensation XE with Beats Audio using xda premium
 
L

lyoth

Member
Feb 13, 2011
41
5
Hawke84 said:
I had a quick look but don't know what a good one looks like. Seems.to be lots of writing timeout?

Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
It is basicly these line
<T005800><DEBUG><OUT>INFO[RUU]UZ,tp,0</OUT>
</DEBUG></T005800>
<T005801><DEBUG><OUT>INFO[RUU]UZ,tp,100</OUT>
</DEBUG></T005801>
<T005801><DEBUG><OUT>INFO[RUU]WP,tp,0</OUT>
</DEBUG></T005801>
<T005813><DEBUG><OUT>INFOstart unzip_and_update_partition: 3</OUT>
</DEBUG></T005813>
<T005813><DEBUG><OUT>INFOstart unzip_and_update_partition: 4</OUT>
</DEBUG></T005813>
<T005813><DEBUG><OUT>INFOstart unzip_and_update_partition: err= 6</OUT>
</DEBUG></T005813>
<T005813><DEBUG><OUT>INFOstart image[radio] unzipping & flushing...</OUT>
Click to expand...
Click to collapse
the err=6 should be err=0, I have no idea what tp is. there is no tp.img in the rom.zip
 
L

lasersword

Member
Feb 24, 2009
31
4
Hi Guys, thanks for your great effort, but one question is ,is there any 'All-in-one' thread or topic include the all required steps and software links as a full tutorial？ thanks
 
M

masands

Senior Member
Apr 15, 2010
78
4
Called HTC/Vodafone repair and they said they are replacing my mainboard because of a "technical issue" :cool:

So happy :D

So what happens when they replace the "mainboard"? Does it wipe all traces of "modification"?
 
You must log in or register to reply here.

Similar threads

mike1986.
[ROM] Android Revolution HD 7.3 | ICS | High Quality & Performance | Legendary
Replies
81K
Views
16M
Ulumia
Ulumia
m0narx
[ROM][Sense 4.1][05.06] Team Venom presents: ViperS 2.0.3 - welcome to the future
Replies
26K
Views
5M
O
OBLIVION007
bruce2728
[ROM][CM10][Kang][Pyramid][4.1.2][04 Oct]
Replies
22K
Views
5M
P
Proxymist
V6-Maniac
[ROM] [29 Sept] ELEGANCIA™ | Sense 3.6 | 4.0 |► ◄| Sense 4.1 | 8.0.0 |EQS,APM,HUB|
Replies
28K
Views
4M
M
materijalmen
shnizlon
[ROM][Sense 4.0][FINISHED] OrDroid 9.0.0 | EQS | APM | Tweaks | Fast & Stable
Replies
17K
Views
3M
dodge67
dodge67

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 167
    dexter93
    dexter93
    We are proud to announce that the Sensation is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.

    Unbrick-proj-Sensation.jpg

    ​

    Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it

    The "core" of the unbricking project dev team:
    MOVZX
    RussianBear
    Fuses
    Dexter93
    Testing stuff and irc support:
    globatron
    Deceptivechaos
    dburgd84
    Snake_skw
    Other stuff:
    dmcb123
    xIndirect
    Hawke84    ​

    Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
    View
    82
    dexter93
    dexter93
    Prerequisites
    • a linux box/live cd with automount disabled and without unity
    • the appropriate package for the device
    • the latest RUU for your device
    • a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
    • a usb cable
    • some basic linux experience
    • patience

    DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

    Instructions​
    Detailed video on the process. Thanks kgs1992


    1. Boot the linux box and download the appropriate package for the device.
      WARNING: IT IS DEVICE SPECIFIC. DO NOT USE THE XE VERSION ON A 4G/ORIGINAL SENSATION AND VICE VERSA
    2. Extract the package in the home directory
    3. Open up a terminal
    4. Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
    5. Detect the device using the script provided. Type this in the terminal
      Code: 
      ./brickdetect.sh
      You should get something like sdX. We are interested on that "X"
    6. Unplug the usb cable from the device
    7. Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
      Code: 
      sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
      Replace the "X" with the letter the script gave you
    8. Follow the on-screen instructions from emmc_recover
    9. Hexdump the b_hboot to check the hboot version
      Code: 
      hexdump -C b_hboot.img |less
      The output should be like this:
      Code: 
      00000000  05 00 00 00 03 00 00 00  00 00 00 00 00 00 10 40  |...............@|
00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |...........@....|
00000020  d8 fc 1f 40 00 00 00 00  12 00 00 ea 31 2e 31 37  |...@........[B]1.17[/B]|
00000030  2e 31 31 31 31 00 00 00  38 32 36 30 20 53 50 4c  |.1111...8260 SPL|
00000040  00 00 00 00 00 f0 20 e3  53 48 49 50 00 00 00 00  |...... .SHIP....|
00000050  00 f0 20 e3 00 f0 20 e3  48 42 4f 4f 54 2d 38 32  |.. ... .HBOOT-82|
00000060  36 30 00 00 00 f0 20 e3  39 32 65 35 33 37 31 30  |60.... .92e53710|
      This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.17
    10. If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
    11. Unplug the device
    12. Check again it is the right version, because if you do a mistake here, you won't be able to go back
      You can only flash the same version as the one in the device.


      !!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
    13. Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.17, 1.18, 1.19, 1.20, 1.23, 1.27) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
      Code: 
      sudo ./emmc_recover --flash pyrV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
    14. Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
      Code: 
      511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied
    15. Unplug the device, put SIM, microSD card and battery in and power on
    16. Congratulations, the device is unbricked.
    17. FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.

    Notes on the procedure:​

    • If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
    • The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
    • Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
    • USB3 ports do not work properly. Please plug the device in a USB2 port
    • The liveCD provided has autoount enabled. please disable it
    • How to disable automount on ubuntu
      Code: 
      gsettings set org.gnome.desktop.media-handling automount false


    Downloads

    For Sensation and Sensation 4G:
    32bit version MD5: 859cf1c8f4cc96a9c911ecf696579e6f
    64bit version MD5: d160e90234999a0f8e5ed632d3a2bb4e

    For Sensation XE:
    32bit version MD5: dec2309cc06dbc01398a4a49f8ae13cf
    64bit version MD5: de677136626fe2e096f0a7f48e438978


    Don't have a linux distro installed on your pc? We highly recommend this livecd
    ​
    View
    18
    F
    Fuses
    It is unbelievable how many writesecureflag bricked devices there are in this world!!

    I write this little tool to help people to unbrick those phones. It also helps unbrick those phones that can be in emmc_mode only few seconds. It uses dd to flash images into device.

    In this guide I will assume that hboot is causing that brick and hboot is at /dev/sdb12 when emmc_mode enabled phone is connected.

    What you need:
    1) Bricked sensation :D
    2) Linux, If you want to use windows you have to wait that somebody makes emmc_mode stable. If you don't have Linux installed, some Live-cd should be fine.
    3) signed hboot from original rom you are using
    4) This little tool called emmc_recover
    5) Figure out what will be correct device node when phone is in emmc_mode
    It is usually /dev/sda /dev/sdb /dev/sdc etc.

    With this tool you can reflash any partition you want. SO BE CAREFUL.

    There are few options in this tool:
    Code: 
    emmc_recovery 0.1 usage:
emmc_recovery [OPTIONS]
	-h | --help: display this help
	-b | --backup
	-f | --flash
	-d | --device

    How to use it (You have to root):
    1) First BACKUP partition
    Code: 
    ./emmc_recover --backup backupfile.img --device /dev/sdb12
    This will backup current sensation hboot into file backupfile.img.

    2) Check that this really is correct partition
    Code: 
    hexdump -C backupfile.img |less
    It should be something like this for hboot
    Code: 
    00000000  05 00 00 00 03 00 00 00  00 00 00 00 00 00 10 40  |...............@|
00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |...........@....|
00000020  d8 fc 1f 40 00 00 00 00  12 00 00 ea 31 2e 31 38  |...@........1.18|
00000030  2e 30 30 30 30 00 00 00  38 32 36 30 20 53 50 4c  |.0000...8260 SPL|
00000040  00 00 00 00 00 f0 20 e3  53 48 49 50 00 00 00 00  |...... .SHIP....|
00000050  00 f0 20 e3 00 f0 20 e3  48 42 4f 4f 54 2d 38 32  |.. ... .HBOOT-82|
00000060  36 30 00 00 00 f0 20 e3  39 64 32 34 31 32 33 66  |60.... .9d24123f|
    3) If backup was successfull, flash new hboot
    Code: 
    ./emmc_recover --flash hboot_xxxx.xxx.xx.xx.xx.nb0 --device /dev/sdb12
    4) Done.

    Below are usual output from tool:
    Code: 
    emmc_recovery 0.1
Messing up with device /dev/sdb12, ARE YOU SURE? (CTRL+C if not)

Flashing image file is hboot_xxxx.xxx.xx.xx.xx.nb0
Device is /dev/sdb12

Press ENTER if everything is correct, CTRL+C if not

Connect device into emmc partition mode NOW
Waiting device /dev/sdb12.......
Foundit!
512+0 records in
512+0 records out
1048576 bytes (1.0 MB) copied, 0.740003 s, 1.4 MB/s
Return code is 0

    Connect device into computer when you see line.
    Code: 
    Waiting device /dev/sdb12.......

    Not before!!

    NOTE: There may be bugs present....
    View
    11
    R
    RussianBear
    awesome!

    any people that know chinese, we need your help:

    a chinese forum where a member posted a guide on how to de-brick a phone (zte u960) from qhsusb_mode:

    http://bbs.malshenzu.com/read-htm-tid-38591-page-1.html

    http://bbs.malshenzu.com/read-htm-tid-41957-page-1.html ( Sales MultiDL tool guide)

    they use an additional tool (Sales MultiDL) that backs up alot of .mbn and .img files that we don't have (yet), so i'm not sure if we can pull those files out of the phone manually, or what?

    80_4747_74ac8bc91c00562.jpg


    translation per untrueparadox:

    1. choose program mode
    2. select the .hex and .mbn files from the included package
    3. load the .xml included in the package
    ____ the path to xml file will show here
    4. after selecting everything, click download to revive the brick

    the files they used to flash:

    80_4747_6a6329c38cb962f.jpg




    anyone knows Chinese (google chrome translator is ok for basic understanding, but nothing more than that)? :)
    i did pm the op of those threads to see what he thinks.
    View
    11
    MOVZX
    MOVZX
    Oh my God...

    Dude... Looks like I have my God besides Me... And my heart is now crying (really)...

    MY PHONE IS NOW ON!! IT COULD BE TURNED ON AGAIN!!


    Thanks God! I really need a beer, I'm going to go now for a celebration...

    PS: I will write tutorials to resurrect the bootloader as soon as possible...


    Thanks XDA Dev... And now I'm sure we'll be able too so ressurrect any phone with MSM8260/MSM8660 including EVO 3D...
    View

New posts