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

Root HTC One (M8) Boot Loop

The good news is from there you can take the Lollipop OTA right off the bat and have the latest firmware so your options will be wide open after you unlock again, TWRP, and go looking for a custom rom.

Avoid what got you here - there's no RUU to save you at the present if you do the Lollipop update, as I assume that will include even newer firmware than the RUU linked above.
 
EarlyMon said:
I think you're out of options.

Here's the 4.4.4 AT&T RUU directly from HTC -

http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe

You'll have to be locked, sorry I can't remember if it's -

fastboot oem relock

Or

fastboot oem lock

The wrong one will fail harmlessly.

Make sure you have a healthy charge. I'd recommend better than 50% at least.
Click to expand...

Okay. Could you just send me a link to a good guide or something for the rest of the process?
 
Amazing! Although I wasn't able to take the route I wanted to, I am satisfied that I know there is a route to get my phone back. I will be doing more research before attempting a ROM flash again. Thanks so much once again. I will leave the RUU downloading. It's 2:30 AM here in FL, and I need sleep haha. I will keep you posted.
 
The Utility connected to my phone and tried to update the ROM, however an error message came up, saying that I have to get the correct RUU for my phone.
 
I suspect that it's complaining because your baseband is 1.16.21331931.LA11G

The third slot for AT&T tends to be 3218 (I *think* because that's strictly by memory, and also 502), I was hoping that as a later update it would fix that too.

I'll have to check around.

Did you at some point put any file named update.zip on your SD card and try to boot into FASTBOOT mode with it?
 
Last edited:
EarlyMon said:
I suspect that it's complaining because your baseband is 1.16.21331931.LA11G

The third slot for AT&T tends to be 3218, I was hoping that as a later update it would fix that too.

I'll have to check around.

Did you at some point put any file named update.zip on your SD card and try to boot into FASTBOOT mode with it?
Click to expand...

no, i did not.
 
EarlyMon said:
http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe

Matches your firmware exactly.

If successful, take every OTA until at Lollipop.

You can then go ahead, unlock again, latest TWRP, and so forth.

Don't reattempt what got you here, no RUU exists to save you after you update.

From Lollipop via OTA and process above, you can roll with the latest ViperOneM8.
Click to expand...

I downloaded the RUU, and tried running it. Same error shows up.

I also noticed when turning off the phone through TWRP, it says "NO OS installed! Are you sure you wish to power off?".

I swipe to power off, then it says "Your device does not appear to be rooted. Install SuperSU now? This will root your device."

I swipe to install, and it just powers off.
 
dil_s13 said:
I downloaded the RUU, and tried running it. Same error shows up.

I also noticed when turning off the phone through TWRP, it says "NO OS installed! Are you sure you wish to power off?".

I swipe to power off, then it says "Your device does not appear to be rooted. Install SuperSU now? This will root your device."

I swipe to install, and it just powers off.
Click to expand...
Yeah - the TWRP auto SuperSU install is cool but intended (I think) for virgin root situations, so I want to not use it moving forward.

Plus I have a hard time believing that the new RUU doesn't match. :D

But let me explain the deal.

The phone factory software is a collection of packages - no different from the rooting world. You got your recovery install, the rom install, the radio install, the whole enchilada.

If you had the separate pieces, you could install them in the correct order using fastboot and do it by hand.

And the point is important and I'm finally getting to it -

That is *exactly* what the RUU exe is doing - plus - important error checking.

Now the way it does that is elegantly simple - inside that exe is each package and the exe is like - let's say - part secret zip file.

So early on, it extracts the hidden packages to a temporary folder, along with a private copy of fastboot that HTC trusts (usually they call it htc-fastboot) and just runs the fastboot installs from the gui you see.

What I think happened (and what I hope happened) is that when the first RUU error'd out, it left the mismatched pieces behind and is confused.

If true, we do some spring cleaning and the new RUU I posted will work.

First, let's look in the last place I knew about.

Get Windows Explorer open.

In the nav bar at top, showing your location - click there - it should change to C:\blah-blah-blah.

Erase it.

Put in %TEMP% and press return.

Look around for things like rom, recovery, firmware, htc-fastboot.

If you see any delete the contents of the whole folder (it's just temporary garbage).

In fact - delete the contents of that folder anyway - and be sure Explorer is set to show you hidden and system files (at least for now).

If you don't see any as I suspect, search your whole computer, including hidden folders for files named as I suggested.

When found, delete the contents of that temporary folder.

Don't delete the temporary folders, just the contents.

Then try today's RUU again.
 
EarlyMon said:
Yeah - the TWRP auto SuperSU install is cool but intended (I think) for virgin root situations, so I want to not use it moving forward.

Plus I have a hard time believing that the new RUU doesn't match. :D

But let me explain the deal.

The phone factory software is a collection of packages - no different from the rooting world. You got your recovery install, the rom install, the radio install, the whole enchilada.

If you had the separate pieces, you could install them in the correct order using fastboot and do it by hand.

And the point is important and I'm finally getting to it -

That is *exactly* what the RUU exe is doing - plus - important error checking.

Now the way it does that is elegantly simple - inside that exe is each package and the exe is like - let's say - part secret zip file.

So early on, it extracts the hidden packages to a temporary folder, along with a private copy of fastboot that HTC trusts (usually they call it htc-fastboot) and just runs the fastboot installs from the gui you see.

What I think happened (and what I hope happened) is that when the first RUU error'd out, it left the mismatched pieces behind and is confused.

If true, we do some spring cleaning and the new RUU I posted will work.

First, let's look in the last place I knew about.

Get Windows Explorer open.

In the nav bar at top, showing your location - click there - it should change to C:\blah-blah-blah.

Erase it.

Put in %TEMP% and press return.

Look around for things like rom, recovery, firmware, htc-fastboot.

If you see any delete the contents of the whole folder (it's just temporary garbage).

In fact - delete the contents of that folder anyway - and be sure Explorer is set to show you hidden and system files (at least for now).

If you don't see any as I suspect, search your whole computer, including hidden folders for files named as I suggested.

When found, delete the contents of that temporary folder.

Don't delete the temporary folders, just the contents.

Then try today's RUU again.
Click to expand...

Searched everywhere. Nothing found with those keywords. Tried clearing everything through TWRP too. Same outcome.
 
You must log in or register to reply here.
Back
Top Bottom