1. Are you ready for the Galaxy S20? Here is everything we know so far!

well it happened to me today! BRICKED

Discussion in 'Android Devices' started by digdug1, Aug 30, 2011.

  1. digdug1

    digdug1 Android Expert
    Thread Starter

    so my phone was running along fine on shifth3ory 1.2. i decided to try the kangbang kernel from the store. i installed vipermod, dropped voltage by 100 then my phone froze. i thought ok my voltage is to low. pulled the battery booted into recovery,reinstalled the kernel tried to boot back up. white screen/black screen/white screen blah blah blah.

    enter panic mode:eek:

    i thought ok i will try to install a backup. i go into recovery try to flash my nandroid and it says files not found! phone reboots.
    now im thinking my recovery is broken. i flashed a new recovery in hboot. same problems:mad:
    i pull battery again boot back into recovery. i try to wipe my phone and in the system format process it reboots. once back into recovery, i try to just install the rom no wiping. reboot!:mad::(

    finally i gave up called cs and the tech guy asked me to get into hboot and tell him my version number:eek::eek:.i tell him that my phone wont stay booted long enough and he says ok (not very convincingly).

    long story short my new phone will arrive Thursday and i will have to root again:mad:

    so the question is, is it possible to get my phone back stock in my phones current state. or at least my hboot version?

  2. WormDoes

    WormDoes Android Expert

    Oh shit :eek:

    You can probably use the RUU.exe if worse comes to worse. I'm sure Scotty has it somewhere
  3. digdug1

    digdug1 Android Expert
    Thread Starter

    thats what i said:eek:
    six times at least...

    i need something that will flash quickly.
  4. digdug1

    digdug1 Android Expert
    Thread Starter

  5. Yeahha

    Yeahha Usually off topic

    I think you will be okay, take a look at this thread it looks like the OP had rooted using Revolutionary and the RUU.exe worked for him. I think the s-off perm hboot is just to prevent OTAs from making the phone go fubar
    digdug1 likes this.
  6. scotty85

    scotty85 Extreme Android User

    ok,are you telling us that your phone reboots in hboot as well?!

    if so this is a first.

    the other bricked phones,hboot is fine-will sit there all day long,it just bootloops in recovery and the normal boot.

    unless you have a unique situation you shuld have plenty of time to flash the old eng bootloader in fastboot,and the mr2 ruu in hboot.

    take some deap breaths,and boot to hboot... let it sit there a few minutes and then get back to us to verify if hboot is also looping,or its fine.
  7. digdug1

    digdug1 Android Expert
    Thread Starter

    lets hope so. downloading now.
  8. scotty85

    scotty85 Extreme Android User

    no,that guy was running the old eng 1.40.2000 hboot.

    sorry,but nothing is overwriting shadowmites hboot except the fastboot commands.
  9. scotty85

    scotty85 Extreme Android User

    sorry dig,its not going to overwrite your hboot. see my post above. let me know,ill help you with the fastboot commands if you need it.
  10. digdug1

    digdug1 Android Expert
    Thread Starter

    i havent seen how long it will stay in hboot to be honest. i have about 40% battery left.
  11. digdug1

    digdug1 Android Expert
    Thread Starter

    link to the commands?
  12. scotty85

    scotty85 Extreme Android User

    then we need to work fast. have you still got adb set up and running?
    got gtalk or an IM you wanna use?
  13. scotty85

    scotty85 Extreme Android User

    again,im not sure how long there will be a need for this,so for now its just going down here.

    if you have flashed the permanent patch s-off hboot from shadowmite on xda,or rooted with revolutionary, here is how you can return to stock if needed:

    origininal directions on xda here: Patched (hard)hboot 1.04 for s-off/eng/fastboot

    at this time i wouldnt reccomend replacing the perm s-off with anything other than our original s-off eng bootloader.

    *please note this guide requires ADB to be set up and working. you can use this video to help you:
    ANDROID SDK Tools (How-To Install) - YouTube

    1) hopefully you still have the unzipped exploits file from when you rooted. if not,redownload it from here. if it is enuff later in time that youre coming across this that the exploits file is no longer available,let me know i can get you the hbooteng.nb0 file.

    2) move the hbooteng.nb0 file from the exploits file to whatever folder you pushed files from when you rooted. in most cases this is tools or platform-tools in the android-sdk-windows folder. *note this guide assumes this file to be named exactly "hbooteng.nb0"

    3) check the md5, check the md5, check the md5 of this image in this folder,since this is the image youre going to flash. it must exactly match 6991368ee2deaf182048a3ed9d3c0fcb if it doesnt,redownload,try again. this is very important- just like when you rooted,you must be sure the bootloader file isnt corrupt. if you mess up your bootloader,nothing will boot,your phone will be bricked.

    4)read #3 again ;) hopefully ive gotten the point across :p

    5) now open an adb command window. change to the directory that your file is stored. in my case:
    Code (Text):
    1. cd c:\android-sdk-windows\flashables
    yours will prolly be different,for example:
    Code (Text):
    1. cd c:\android-sdk-windows\tools
    6)plug in your phone,make sure usb debugging is on,put it in charge only mode.

    Code (Text):
    1. adb devices
    and make sure its connected

    Code (Text):
    1. adb reboot bootloader
    to boot into fastboot. *do not push power to select hboot. fastboot is where you need to stay for this.

    Code (Text):
    1. fastboot devices
    to make sure its connected

    Code (Text):
    1. fastboot oem mw 8d08ac54 1 31302E30
    11) enter
    Code (Text):
    1. fastboot flash hboot hbooteng.nb0
    if you select bootloader at this point from the fastboot menu, youll still see the permanent s-off hboot,so select reboot with the volume rocker and power button and let the phone reboot. after it boots,you can adb reboot bootloader again,or power off, then power on/vol down and check that your pink "UNLOCKED" or "REVOLUTIONARY" is gone and you have the old 1.49.2000 bootloader.

    last and not least,heres what youll see when you do this(the red is my inputs)

    Code (Text):
    1. Microsoft Windows [Version 6.1.7601]
    2. Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    4. C:\Users\Scott>[COLOR="Red"]adb devices[/COLOR]
    5. List of devices attached
    6. HT126S005970    device
    9. C:\Users\Scott>[COLOR="red"]cd c:\android-sdk-windows\flashables[/COLOR]
    11. c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]
    13. c:\android-sdk-windows\flashables>[COLOR="red"]fastboot devices[/COLOR]
    14. HT126S005970    fastboot
    16. c:\android-sdk-windows\flashables>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
    17. ...
    18. OKAY [  0.006s]
    19. finished. total time: 0.006s
    21. c:\android-sdk-windows\flashables>[COLOR="red"]fastboot flash hboot hbooteng.nb0[/COLOR]
    22. sending 'hboot' (1024 KB)...
    23. OKAY [  0.183s]
    24. writing 'hboot'...
    25. OKAY [  0.219s]
    26. finished. total time: 0.403s
    28. c:\android-sdk-windows\flashables>
    once you have verified that youre on the original eng s-off,1.49.2000 hboot,you can flash a "back to stock" RUU if your choice. which one prolly depends on your needs.

    i *believe* that you can flash mr2 overtop of something without a SECURITY WARNING but ive never done it,so i cant reccomend doing this. if you want to try it,do so at your own risk.

    prolly the safest method would be simply to flash shipping firmware as directed here: simple un-root!

    this will give you 1.12.605.6 firmware with s-on and stock recovery. after you boot and sign in,you will shortly be badgered to OTA to current firmware(at this time MR2),wich i would prolly allow to happen,depending on your reasons for returning to stock.
  14. scotty85

    scotty85 Extreme Android User

    thats from the "how to" sticky.

    get the old eng hboot into your tools(or wherever directory) and get adb set up and working.

    power on into hboot.

    press power to select fastboot.


    Code (Text):
    1. fastboot devices

    Code (Text):
    1. fastboot oem mw 8d08ac54 1 31302E30

    Code (Text):
    1. fastboot flash hboot hbooteng.nb0
    press reboot. when it starts to loop,pull battery.

    then pull sd card,put mr2 PG05IMG on sd card and flsh that. 40% is prolly enuff(if not it doesnt matter youll have the 1.04.0000 s-on hboot,and your phone is allready a brick)
    dai uy b, Yeahha and Ibrick like this.
  15. digdug1

    digdug1 Android Expert
    Thread Starter

    good news is it will still charge.:)

    now that booted back into hboot it says my hboot version is 1.04.0000. so i may not have gotten around to flashing the new version. i do remember downloading it though.
  16. scotty85

    scotty85 Extreme Android User


    s-on? what did you flash to get that?

    does it say unlocked at the top?
  17. digdug1

    digdug1 Android Expert
    Thread Starter

    yea it says unlocked.
  18. scotty85

    scotty85 Extreme Android User

    ok,thats the permanent hboot. youll have to get adb setup,put the hbooteng.nbo into whatever directory you push files from and follow the directions from post #15. look at my session in post #14 so youll see how it looks.

    its no big deal to fastboot the old eng hboot in place,ive done it a couple times now :)
    dai uy b and digdug1 like this.
  19. digdug1

    digdug1 Android Expert
    Thread Starter

    do you have link to


    all i can find is the patched version.
  20. scotty85

    scotty85 Extreme Android User

    Yeahha and digdug1 like this.
  21. scotty85

    scotty85 Extreme Android User

    almost forgot,you will have to rename the image to hbooteng.nb0 so you wont have to change the name in the directions ;)
  22. Ibrick

    Ibrick Android Expert

    Sorry to hear bro..

    At least it looks like you'll be able to get it back to appearing stock, if not stock. I still haven't heard of VZW looking too much farther than inspecting the packaging, and making sure the phone turns on when it comes to a warranty claim.

    Hope all works out!
  23. Yeahha

    Yeahha Usually off topic

    That is about the same as I've heard but they may notice the "Unlocked" when going into hboot if that is the only thing you can do with the phone.

    Glad scotty got here :D he should be able to get it back to a returnable condition (see scotty when we aren't discussing kernels and the like you are a very valuable asset ;))

    Dig were you undervolting below what you would have as normal? Also did you have the set on boot option set on setCPU? The file not found error you had was that when trying to get into recovery or when in recovery and trying to get to a nandroid to restore? I'm asking because I am wondering if this corrupted part of your SD as well.
  24. digdug1

    digdug1 Android Expert
    Thread Starter

    crap. i cant get adb to recognize my phone while in hboot!

HTC Thunderbolt Forum

The HTC Thunderbolt release date was March 2011. Features and Specs include a 4.3" inch screen, 8MP camera, 768GB RAM, Snapdragon S2 processor, and 1400mAh battery.

March 2011
Release Date

Share This Page