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

Root HTC one m8 bricked. Please help

C

calym1011

Newbie
Hello, i have bricked my htc one m8. when i start it up it is stuck on the htc logo. I'm able to access bootloader, but i dont know what to do right now to get it to work. Please help me to fix this
picture000.jpg


(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH446WM03623
(bootloader) imei: **mod removed for security**
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
 
Last edited by a moderator:
Hello and welcome to AF!! :)
Can you provide us with some background info as to what you did, or didn't do that led up to this?
Also, I have removed your IMEI number for security purposes (folks can do not-so-nice things with it;) )
 
i unrooted and everything and then i was trying to do the ota 5.0.1 lollipop update and then it still wouldnt work taking me to stock recovery so i flashed this OTA_M8_UL_L50_SENSE60_MR_Rogers_WWE_4.20.631.2-3.34.631.4_release_41994893s8m7752dj4px5o.zip and then i flashed just the firmware but forgot i wasnt s-off anymore so like after it showed the firmware was done downloading or whatever it is onto my phone i rebooted it and couldnt get past the htc logo screen
 
I'm concerned as you are about the firmware flash going wrong.

I don't know if an ruu is required or possible here to be honest - I've never much used them.

If it were me, I'd try to unlock it again, install TWRP and see if a nandroid restore will get you out of it.

Those don't go near the firmware partitions so not sure if that'll help.

You mentioned that you're not s-off anymore - did you first attempt to take it from s-off or did you mean a previous phone?

When in FASTBOOT USB mode have you tried using your pc to -

fastboot erase cache
 
EarlyMon said:
I'm concerned as you are about the firmware flash going wrong.

I don't know if an ruu is required or possible here to be honest - I've never much used them.

If it were me, I'd try to unlock it again, install TWRP and see if a nandroid restore will get you out of it.

Those don't go near the firmware partitions so not sure if that'll help.

You mentioned that you're not s-off anymore - did you first attempt to take it from s-off or did you mean a previous phone?

When in FASTBOOT USB mode have you tried using your pc to -

fastboot erase cache
Click to expand...
i became s-on while unrooting. i dont know if i can unlock it or install twrp again as my usb debugging got disabled, so i dont know what to do
 
Fastboot may not care about usb debugging, try it.

I'll call on a friend who's expert on this stuff. Given the late hour I wouldn't expect a response tonight.

Hope this can be recovered.
 
calym1011 said:
i dont remember how to get my backup onto my phone because my data got reset
Click to expand...
In the phone's present state I don't know if we can.

Let's take another approach and see if we can at least get you up and running.

Download ViperOneM8 (Lollipop not available) and put it in the same folder as your fastboot.

TWRP, Advanced, adb sideload, slide to activate.

PC command window where fastboot and the Viper zip file are -

adb sideload name-of-rom-file.zip

With luck, the Viper installer will launch - choose the defaults, nothing to over think, install Viper.

Best luck!
 
Then you had a bad download or it's not in the same folder as adb - those are the only two things that can cause that message.

In your command window, say -

dir

Make sure that Windows didn't help you rename it to rom.zip.zip it's famous for that.

In the dir listing you should see adb.exe and rom.zip.
 
EarlyMon said:
Then you had a bad download or it's not in the same folder as adb - those are the only two things that can cause that message.

In your command window, say -

dir

Make sure that Windows didn't help you rename it to rom.zip.zip it's famous for that.

In the dir listing you should see adb.exe and rom.zip.
Click to expand...
i see both
 
You must log in or register to reply here.
Back
Top Bottom