• 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

dil_s13

Member
I have an HTC One (M8) in a boot loop. I have two ROMs (HTC RUU and SkyDragon Sense 7) on a Micro SD card inserted in the device. I initially entered this state of boot loop when i deleted everything and had no ROM to load. I tried using TWRP recovery to sideload the ROM before purchasing a Micro SD card and reader/writer. I then tried using TWRP recovery to flash the ROM from the Micro SD. I wiped everything including cache and Dalvik cache. Neither ROMs would flash. I tried the same thing with CWM recovery. Only change was that the SkyDragon ROM flashed and loaded it's setup. I went through all of the setup of SkyDragon and it installed. I selected yes to reboot, and it just booted to the "HTC powered by ANDROID" screen with red warning message covering "powered by ANDROID". Please help me, as I've been without a phone since yesterday, and am pretty handicapped.
 
This is my hboot screen.
 

Attachments

  • boot.jpg
    boot.jpg
    49.7 KB · Views: 210
An RUU is not a rom. Don't ever try to work with one without checking with us or someone knowledgeable at XDA unless you want to convert your phone into a paperweight.

What version of TWRP are you running?

Can you get to it from hboot?

Which thread did you go to get Skydragon? (Link to thread please.)

What carrier are you on?
 
An RUU is not a rom. Don't ever try to work with one without checking with us or someone knowledgeable at XDA unless you want to convert your phone into a paperweight.

What version of TWRP are you running?
-v2.7.0.2

Can you get to it from hboot?
-Yes

Which thread did you go to get Skydragon? (Link to thread please.)
-This is the link to the location of the download, however, I can no longer access it. I downloaded it last night.
https://kbeexa.bl3301.livefilestore...Sense+7+Full+Variants.zip.zip?download&psid=1


What carrier are you on?
-AT&T
 
I am not able to find it. There is a possibility that it isn't a reliable source. Is that your concern?
More a concern that it wasn't really the M8 version and I'd like no partition surprises going in.

We'll just have to proceed without it.

AT&T has finally released Lollipop.

Ideally, we want to find the RUU for that (your firmware is way old and going to do you no favors with a new Lollipop), update you to a current TWRP (same deal) and then go for Skydragon if that's your choice.

No promises on the RUU.

Please get into FASTBOOT USB mode and from your tools folder say -

fastboot getvar all

Alt+space in the command window, E for edit, select all, copy and paste your results here -

And edit out your meid and serial number.
 
More a concern that it wasn't really the M8 version and I'd like no partition surprises going in.

We'll just have to proceed without it.

AT&T has finally released Lollipop.

Ideally, we want to find the RUU for that (your firmware is way old and going to do you no favors with a new Lollipop), update you to a current TWRP (same deal) and then go for Skydragon if that's your choice.

No promises on the RUU.

Please get into FASTBOOT USB mode and from your tools folder say -

fastboot getvar all

Alt+space in the command window, E for edit, select all, copy and paste your results here -


C:\Users\EG\Downloads\fastboot_adb>fastboot devices
xxxxxxxxxxxx fastboot

C:\Users\EG\Downloads\fastboot_adb>fastboot flash recovery twrp-2.8.6.0-m8.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.687s]
writing 'recovery'...
OKAY [ 0.996s]
finished. total time: 2.684s

C:\Users\EG\Downloads\fastboot_adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s

C:\Users\EG\Downloads\fastboot_adb>

And edit out your meid and serial number.
 
OK, no one has the latest RUU yet.

Let's try to just get you running.

Install the latest TWRP from here in FASTBOOT USB mode, using

fastboot flash recovery twrp-2.8.6.0-m8.img

http://dl.twrp.me/m8/ (and place in same folder as your fastboot)

The reason that you didn't have a good download source for Skydragon - and I did not know this - was that the dev was disgusted with being constantly ripped off -

http://forum.xda-developers.com/showpost.php?p=59624010&postcount=3022

It's been officially withdrawn, and is no longer supported.

I'd recommend a nice ViperOneM8 rom to at least get you in business until you can sort out your options.

http://venomroms.com/htc-one-m8/

I'd recommend version 3.2.1 until a suitable firmware becomes available to you to move up to the latest.

Alternatively you could go for a stock rooted rom, get Sunshine s-off, update your firmware from the sources already available and then go for Lollipop.

If it were me, I'd get running with ViperOneM8 KitKat, hold off a few days or so for the AT&T RUU and look at options from there.
 
If you go with ViperOneM8 as I suggest, go ahead and choose full wipe from within the Aroma installer.

Because of your phone condition, expect it to take a LONG TIME at that phase.

Give it up to a half hour and leave it be - so you're going to want a good charge before starting.


If it boot loops after installation -

Place a copy of the rom in your fastboot folder in the meantime and extract the boot.img file from the rom zip into your fastboot folder and then -

fastboot flash boot boot.img

And all of this assumes that you didn't have a nandroid backup to fall back on.
 
If you go with ViperOneM8 as I suggest, go ahead and choose full wipe from within the Aroma installer.

Because of your phone condition, expect it to take a LONG TIME at that phase.

Give it up to a half hour and leave it be - so you're going to want a good charge before starting.


If it boot loops after installation -

Place a copy of the rom in your fastboot folder in the meantime and extract the boot.img file from the rom zip into your fastboot folder and then -

fastboot flash boot boot.img

And all of this assumes that you didn't have a nandroid backup to fall back on.


OK. as far as the 2.8 TWRP, It does not load from bootloader. I downloaded the exact same one. The only TWRP that loads is the version i have (2.7xxx)
 
OK. as far as the 2.8 TWRP, It does not load from bootloader. I downloaded the exact same one. The only TWRP that loads is the version i have (2.7xxx)
Check the md5 checksum of your later TWRP.

If it doesn't match, download again.

If it does match, try to flash it again.

If you still can't get into it, your partitions are hosed and you're on borrowed time until fixed.

No telling if any rom will install.

If it does, get a full backup of anything you can, especially from your internal storage.
Also, the viper download. I'm not downloading the latest? where do I find the one i need?
No, don't try for the latest, your firmware is too old.

At the link I provided, click on previous roms to find 3.2.1.
 
Check the md5 checksum of your later TWRP.

If it doesn't match, download again.

If it does match, try to flash it again.

If you still can't get into it, your partitions are hosed and you're on borrowed time until fixed.

No telling if any rom will install.

If it does, get a full backup of anything you can, especially from your internal storage.

No, don't try for the latest, your firmware is too old.

At the link I provided, click on previous roms to find 3.2.1.

I've checked the checksum and redownloaded and reflashed it many times. Only 2.7 boots with my bootloader. I was told that the 2.8 doesn't work well with old firmware.
 
Back
Top Bottom