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

[T-Mobile] *booting directly into the bootloader???*

Discussion in 'Android Devices' started by Duo Maxx3, Dec 17, 2013.

  1. Duo Maxx3

    Duo Maxx3 Newbie
    Thread Starter

    Hello everyone. I will make this short and sweet.

    I will make note that I have a stock phone. It's locked, never tried to unlock the bootloader or root the phone...

    -Phone randomly rebooted
    -reboot took Alot longer than usual
    -after reboot all Google apps force closed
    -phone rebooted again, rebooted directly into bootloader.
    -Every time I attempted to reboot the phone it booted directly into the bootloader
    -every time I cut off the phone to charge it, it will cut on automatically, directly into bootloader.

    Any help will be greatly appreciated.

    1. Download the Forums for Android™ app!


  2. Brian706

    Brian706 I like turtles!

    My only suggestion would be to try a factory reset from the bootloader to get up and running again. Failing that, try to hunt down an RUU to use.

    It sucks because you'll lose your data, so maybe see if someone else has any less extreme suggestions first??
    Duo Maxx3 and scotty85 like this.
  3. Duo Maxx3

    Duo Maxx3 Newbie
    Thread Starter

    I tried a factory data reset from the bootloader, but the phone cut off and rebooted back into the bootloader. o_O

    I'm not worried about the data. Especially considering that anyway around the issue now would end up reseting the phone anyway.

    I'm thinking I'm going to have to atleast unlock the bootloader(or atleast attempt to) and install a custom recovery, flash a rom to get it back. My only thing about that is the battery life. I have no clue what it was before the phone started to act up, and it won't stay of and charge. If it's plugged into power, it will automatically boot up into the bootloader.
    scotty85 likes this.
  4. marctronixx


    Moving to rooting forum to move the discussion to the next level..
    Duo Maxx3 and scotty85 like this.
  5. Brian706

    Brian706 I like turtles!

    Can I get the bootloader information from you? Can you type out what it says?

    Also if you can get into fastboot do a fastboot getvar all if possible.

    Let me know if you need further instructions for that.
    Duo Maxx3 and scotty85 like this.
  6. scotty85

    scotty85 Extreme Android User

    hate to say this,but a stock phone doesnt usually stop working due to a prollem that a simple rom flash will fix. if youve never modded your phone or messed with anything,its likely you have some sort of hardware failure,unless youve left some other recent event out of your description of what happened. ;)

    we can certainly try and unlock and flash a rom,but i wouldnt get my hopes up too much for that fixing it. your phone will still be s on,and there are alot of limitations on what can be done to fix it.

    if you have any chance of a warranty replacement,that is a better option,and i would do so now,while the bootloader is locked and not relocked,as being relocked could easily let them refuse your warranty claim.
    Duo Maxx3 and Brian706 like this.
  7. scotty85

    scotty85 Extreme Android User

    here are some directions for the getvar all:
    first download and install these drivers: revolutionary drivers (mirror)

    then,download this small file:

    -unzip it,and place the unzipped folder onto the root of your C drive(not inside a folder)

    -open a cmd window(with win 7,click start bubble,type "command" or "cmd" in hte search box)

    -now change to your mini-adb directory(assuming you didnt chagne the name). type in the black cmd window that opened on your PC:
    cd c:\mini-adb

    -pull the battery in your phone for a few seconds. hold volume down,then power. hold them both until you see the white/colored writing hboot screen

    -select "fastboot" from the hboot menu with the vol rocker/power button

    -in your cmd window type:
    fastboot devices

    it should output your phones serial number. if so youre good to go. if not,youre apparently having a driver issue. i usually recomend these drivers from Revolutionary: modified htc drivers download and install the drivers(you should just have to run that file). afterwards,unplug your phone,plug it back in. make sure its in fastboot. as soon as you get a result from "fastboot devices" your ready to procede to the next step.

    -in your cmd window,type(or copy/paste,is much easier):
    fastboot getvar all

    -copy the info that outputs here. right click in your cmd window,click mark,highlight it all in white. hit enter. paste the info here. it will help us know which ruu for you to run. :)

    while you are at it,let us know the hboot info.

    luckily,there are t mobile ruus,so its possible that running one of them may get you up and running if you do have some sort of software issue.

    ruu is also a better option than unlocking and installing a custom rom at this point.
    Brian706 and Duo Maxx3 like this.
  8. Duo Maxx3

    Duo Maxx3 Newbie
    Thread Starter

    Currently the bootloader reads like this:

    *** TAMPERED ***
    *** LOCKED ***
    *** Security Warning ***
    Jun 21 2013, 20:19:45:-1

    Then below that is the usual fastboot, recovery and other options..

    Everything listed above in the previous post is what I know. The sad part about all of this is that this phone is the replacement for my first one(cracked screen to all hell) and now I'm back to using the cracked one.
    scotty85 likes this.
  9. scotty85

    scotty85 Extreme Android User

    Ahhh. Well, the bad news is that someone at some point has rooted it and messed with your replacement phone. The good news is that an ruu should probably fix you right up. We just need the results of the fastboot getvar all to see what ruu to run. :)
    Brian706 and Duo Maxx3 like this.
  10. Duo Maxx3

    Duo Maxx3 Newbie
    Thread Starter

    So you're saying that the phone I got from Asurion is probably refurnished, and that at some point this in its past life it was rooted, and Asurion either didn't catch it or attempted to patch it up?
  11. Duo Maxx3

    Duo Maxx3 Newbie
    Thread Starter

    I can't do getvar because the phone is stuck at the bootloader. I can't access anything but the bootloader, no recovery, no fastboot, nothing. Just the bootloader.
  12. scotty85

    scotty85 Extreme Android User


    I am fairly sure that asurion did not try and patch the phone. There really is not much(any) of a refurb process for the phones received and sent back out.

    While it is possible that something natural happened to the phone that caused it to set its flags and become stuck in this mode , the more likely scenario is that it has been rooted in the past.
    Brian706 likes this.
  13. scotty85

    scotty85 Extreme Android User

    You can do the getvar all in this mode. You can still switch between hboot and fastboot

    Your options at this point are:
    - send the phone back
    - unlock the bootloader
    - run an ruu
    Brian706 likes this.
  14. scotty85

    scotty85 Extreme Android User

    if you want to run an ruu without the getvar all,this is the latest,to my knowledge(i dont run t mo software on my t mo device :eek:): Shipped ROMs

    this is a .exe that is run on your pc. youll need to make sure that you have the phone in fastboot(youll see fastboot usb on the screen) and then run the utility as administrator if your version of windows permits that. if youre on windows 8,and/or are using usb 3.0,you may have issue,so run on an older machine,if possible.

    good luck,holler if you have questions. im off to work,but ill try and watch :)
    Brian706 likes this.
  15. scotty85

    scotty85 Extreme Android User

    any luck?? :thinking:

HTC One M7 Forum

The HTC One M7 release date was March 2013. Features and Specs include a 4.7" inch screen, 4MP camera, 2GB RAM, Snapdragon 600 processor, and 2300mAh battery.

March 2013
Release Date

Share This Page