• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root My HTC One M8 is stuck on bootloader?

TylerToast

TylerToast

Newbie
Hello!
This is my first Android phone, I traded my iPhone 5s for it and im glad I did. I loved, well love my HTC.

When I received the phone it was already rooted and had a ROM on it. Finally after a long time I got the balls to try and install a new ROM, I was trying to do Android Revolution HD and now my phone is stuck on bootloader. I can go into recovery mode and everything else.

I don't know if this is was the issue but I put the ROM I was using on a 2-sided USB that had one side USB 3.0 and then a micro USB connection.

If anyone has any suggestions on how I can fix my phone I would appreciate it. I don't have an extra and this is the only one I have.
 
Yatezy said:
Have you tried wiping the cache and Dalvik cache in recovery?
Click to expand...
Yes. I have also tried using a different ROM as well.
It just takes me back to the bootloader screen with ***Tampered*** at the top as well as unlocked and the rest of everything.
 
Get the Mini-SDK here (not the full one in the first post) -

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Unzip it into c:\sdk-tools as directed.

Get the ARHD rom you flashed, open it, extract a file called boot.img and copy it to c:\sdk-tools - download it again if you have to.

Power up your phone while holding volume down - you'll see FASTBOOT highlighted on the phone. Plug it into your pc, it'll change to FASTBOOT USB.

You want to be plugged in to a USB 2 port if you can.

Open a command window on your pc.

http://pcsupport.about.com/od/commandlinereference/f/open-command-prompt.htm

Type the following command into the command window - mind the spaces in the commands -

cd \sdk-tools

Your prompt should now say C:\SDK-TOOLS

If it doesn't, post back.

If you unzipped the Mini-SDK as directed and minded the space after the cd, the command will be successful.

In that case, say -

fastboot flash boot boot.img

If you had the boot.img image there and the command correct, you'll get a command successful and an OK.

If so, now say -

fastboot reboot

Your first ARHD reboot may take from 5 minutes to a half hour to get going, depending on how you flashed it, probably closer to 5 or 10 minutes.

You'll see a dialog that it's updating apps after the first boot screens.

Unplug the phone, enjoy your new rom.

OK to give us screen shots for any issues along the way.

If you're using a Mac or Linux, that's no problem - the commands are almost the same, let me know and I'll give you the modified commands. Meanwhile, the Mini-SDK is good for Mac or Linux, set up the sdk-tools folder under your Home directory along with the boot.img because you won't have a C: in Mac or Linux.
 
Oh boy. My bad.

I just read you tried a different rom.

The pieces don't mix and match.

Get the boot.img from whatever rom you've flashed.

The procedure will be the same.

Either ARHD or the other M8 rom will be fine, but the boot.img has to match.
 
TylerToast said:
"Flashboot" is not noticed as a internal or external command"
Any ideas?
Click to expand...
I noticed that you surfed over to the Mini-SDK earlier, so can I assume that you downloaded it and unzipped it to C:\SDK-TOOLS?

If so, are you in the SDK-TOOLS folder in your command window?

Got there by saying -

cd \sdk-tools

With a space after the cd, and now the command prompt says -

C:\SDK-TOOLS >
 
I have already entered that command and it was successful.

After that was a success. I entered the next command you said to do it is saying it is not known as a external or internal command
 
upload_2015-2-23_0-15-12.png
 
I've done everything you told me to and am still having that issue.
Thanks for dealing with this and giving me the help to fix my phone. C:
 
TylerToast said:
I've done everything you told me to and am still having that issue.
Thanks for dealing with this and giving me the help to fix my phone. C:
Click to expand...
OK I think I see what happened.

In Windows Explorer is sdk-tools\sdk-tools empty?

Is it just in sdk-tools?

I bet it is.

Say -

cd ..

(spacebar after the cd, always)

And try again.
 
No.

Erase the sdk-tools folder inside the sdk-tools folder.

You got the file named sdk-tools.zip from the Mini-SDK link I gave you? It's at the bottom of the second post in the thread I linked.

Unzip it.

Copy the files out of it and place into sdk-tools folder.

When done, fastboot.exe and the other files will be in the same folder as boot.img

Shift right click on the folder containing fastboot.exe and the boot.img - choose from the drop down menu - Open command window here.

Then say

fastboot flash recovery boot.img
 
Im at school right now, ill let you know if this works around 3-4pm EST.
I think I understood what you meant, I did unzip the file I just did not unpack the contents into the folder that were in the Mini-SDK.zip So I will do that when I get home and see if that fixes the issue.
 
Im still having the issue of the fastboot not being a external or internal command. I have done everything you have told me to and re-extracted the contents of the file.
 
Good news. I just tweaked things a little bit and the command went threw successfully. What do I need to do after the command "fastboot flash recovery boot.img"
 
TylerToast said:
Im still having the issue of the fastboot not being a external or internal command. I have done everything you have told me to and re-extracted the contents of the file.
Click to expand...
OK.

Sorry that the instructions were too difficult - I know you've tried hard to follow the directions.

I'm tempted to try to explain it again but I don't know how you got so lost downloading a zip file and opening its contents.

Before I set about writing an installer that you can't find, try this -

Open Windows Explorer.

Go to C:

Search for fastboot.exe

It will find where you put the file and tell you what folder it is in.

Take a screen shot.
 
EarlyMon said:
Then say

fastboot flash recovery boot.img
Click to expand...

God.

I'd done this so many times. I got confused. :mad:

You had it fixed and rebooted.

Then you ran that.

Now your recovery is broken.

Go here - http://teamw.in/project/twrp2

Input your phone and choose by carrier type.

Get the img file, download and place into C:\sdk-tools

Then say:

fastboot flash recovery name-of-open-recovery-file

name-of-open-recovery-file is going to be openrecovery-VERSIONsomething.img

After that, you should be ok.
 
You must log in or register to reply here.
Back
Top Bottom