M8 stuck on bootscreen, can't boot into recovery mode - One (M8) Q&A, Help & Troubleshooting

Hello, guys, I wanted to flash new version of LineageOS 14.1. today, but now I can't enter recovery, and the device is stuck on boot screen. I can enter only bootloader. I didn't flashed then new ROM I have just send boot.img of the new ROM to phone via cmd. And since I did this I can't boot into recovery. I have backup of RR ROM which I was using for more than 6 months, but I need to acces recovery for that. I was trying to flash the recovery image but it didn't work. Every help is really apreciated. Thank you.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Troksik said:
I didn't flashed then new ROM I have just send boot.img of the new ROM to phone via cmd.
Click to expand...
Click to collapse
Why would you do this, in the first place? It's not necessary to flash boot.img separately. It flashes automatically, when you flash the ROM.
What command (exactly how you typed it), did you use to flash the boot.img? I have a feeling you flashed it to the recovery partition.

Related

[Q] Need help, HTC One X 4.2.2 stuck at boot logo

I need some help to recover my HTC One X international. I can't boot into OS, and it is stuck at HTC boot logo. I am trying to flash kernel but somehow things went bad and i cant boot, I have tried to restore RUU RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed.exe but since my Hboot version is higher than the RUU, i got error 158. I am out of idea right now how to get my phone back alive. It Is S-ON.
this is my getvar:
version: 0.5a
version-bootloader: 1.73.0000
version-baseband: 5.1204.167.31
version-cpld: None
version-microp: None
version-main: 4.19.707.3
serialno: SH24JW111563
imei: 354461057205714
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: HTC__044
battery-status: good
battery-voltage: 3774mV
devpower: 41
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
kolniklaus said:
I need some help to recover my HTC One X international. I can't boot into OS, and it is stuck at HTC boot logo. I am trying to flash kernel but somehow things went bad and i cant boot, I have tried to restore RUU RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed.exe but since my Hboot version is higher than the RUU, i got error 158. I am out of idea right now how to get my phone back alive. It Is S-ON.
this is my getvar:
version: 0.5a
version-bootloader: 1.73.0000
version-baseband: 5.1204.167.31
version-cpld: None
version-microp: None
version-main: 4.19.707.3
serialno: SH24JW111563
imei: 354461057205714
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: HTC__044
battery-status: good
battery-voltage: 3774mV
devpower: 41
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
For you will work only nandroid backup nothing else go in general section download nandroid backup and install or install custom recovery like Philz and install custom rom
Thant said:
For you will work only nandroid backup nothing else go in general section download nandroid backup and install or install custom recovery like Philz and install custom rom
Click to expand...
Click to collapse
thanks so much, i am downloading nandroid backup now. After I am done with nandroid backup do i need to install custom rom?
If you want to run a custom rom you don't have to install a nandroid backup ! Go straight for a custom one.....saves time

No OS. Stuck on Bootscreen VODAP001

Hi Guys,
I made a mistake of formatting my phone from TWRP. NowI am stuck on bootloop. I am S-ON.
I can get into TWRP or fastboot but I don't know what to do from there.
I read around that I could do a sideload but I don't know what file to use.
I could not find any RUU files for my CID.
Please help salvage my phone.
The dump of my getvar all is here:
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: VODAP001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Load ROM onto external SD card and insert. From TWRP mount extSD, then install ROM from there.
flyera343 said:
Load ROM onto external SD card and insert. From TWRP mount extSD, then install ROM from there.
Click to expand...
Click to collapse
You mean restore a nandroid backup?
mentos84 said:
You mean restore a nandroid backup?
Click to expand...
Click to collapse
Ok.. so I did a 3.29.161.2 nandroid backup and my phone came up
How can I now update to the latest 4.19 ?

Softbrick HTC ONE M8s

Hi,
I was trying to flash my HTC ONE M8s but was unsuccessful. I wasn't aware that only a certain ROM could be used.
I am not exactly sure what I did but even the recovery partition is gone. Anytime I try to go into recovery or boot the phone it just goes to the htc logo screen. I have tried to flash a new recovery (TWRP) and (CWM). Fastboot tells me it has gone across ok but when I try to boot into recovery again I just get the htc logo screen.
I have tried to use ADB but it will not pick up my device. I don't think I enabled developer mode correctly before I started fooling around with the phone.
I unlocked the bootloader but still have S-ON. I have tried using RUU file for my model id but still nothing.
Is there any tools out there that I can use to totally wipe the phone clear and start fresh without having to send it back to HTC.
The reason I tried to flash it in the first place was that my camera stopped working after the update for Marshmallow came out. I asked HTC about it and they just wanted me to send it to them.
Their support is not very good!!!
Any help would be greatly appreciated.
Also if this post is not in the right place feel free to move me on, this is my first time.
Heres my phone details:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main: 2.10.401.1
version-misc: PVT SHIP S-ON
serialno: FA576YS00568
imei: 358031062652980
imei2: Not Support
meid: 00000000000000
product: m8ql_ul
platform: hTCBmsm8939
modelid: 0PKV10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0b9a12e3
hbootpreupdate: 11
gencheckpt: 0
mfg-name: 0001
Install 2.10.401.1 RUU
Read this : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
and this : http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this too : http://forum.xda-developers.com/htc...able-to-install-m8s-ota-update-v2-20-t3513297

need help with a51_dtul device,get stuck in bootloop, doesn't flash, doesn't work

hi, everybody.
I wanted to flash a custom ROM on my a51_dtul device with KitKat android. but it didn't work. so I wiped cache, Dalvik and internal storage as well. in fact, nothing is in internal storage now, and won't boot any os. my device is unlocked and below is the information.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 01.01.010_U10305041_08.01.41222_2
version-cpld: None
version-microp: None
version-main: 1.29.1405.1
version-misc: PVT SHIP S-OFF
serialno: HC4AWYC03279
product: a51_dtul
platform: hTCBmsm8939
modelid: 0PFJ11000
cidnum: HTCCN701
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: eae94f74
hbootpreupdate: 11
gencheckpt: 0
mfg-name:
I also downloaded the firmware from the gsmdevelopers(i can't provide the link), but the zip file is corrupted.
but you can reach the link here on number 5
but I flashed a firmware in Hboot mode and successfully done it. but still don't boot any os and any time I reset or reboot it stucks in boot loop and gets back to TWRP recovery mode. I really don't know what should I do.
I wanted to flash cm12 with a higher android version, but I loosed what I had .
if anybody has the backup for a51_dtul can upload for me? at least I can use my phone if I restore it.

HTC One M8 twrp-2.8.7.0 works, but twrp-3.x.x.x doesn't work

Hi Guys,
I want to revive my HTC One M8 (unlocked bootloader since 2014). Unfortunately, Installing the newest TWRP Image doesn't work. I tried install twrp-3.4.0-1-m8.img, but after I click in the bootloader "reboot recovery" or type "fastboot boot twrp.img" there is written on the screen for 0.1 seconds "entering recovery" but then the screen turns black.
So I tried different TWRP Versions, but the most recent version is twrp-2.8.7.0, but I can't use it to install Lineage OS 17.1.
Even the Lineage OS Recovery isn't working. Same here. After installing and entering recovery, the screen stays black (or the phone is off, not sure)
Any Ideas why it doesn't work? :/
Umm i have the same htc with the same problem as yours.I had unlocked bootloader since 2014 and TWRP 2.4 something worked flawlessly.When i updated to TWRP 3.4 the latest build it says entering recovery and it freezes,but it's actually a bug at least on mine,when i just double click Power button the screen flashes and it enters TWRP (I don't know it's weird).Try to getvar all so we know,what do you need exactly,because there is a high chance since you haven't touched your firmware since 2014,that your bootloader version will be smaller than 3.19 (which is needed to flash LineageOs) like mine.
snakeskaterthree said:
Hi Guys,
I want to revive my HTC One M8 (unlocked bootloader since 2014). Unfortunately, Installing the newest TWRP Image doesn't work. I tried install twrp-3.4.0-1-m8.img, but after I click in the bootloader "reboot recovery" or type "fastboot boot twrp.img" there is written on the screen for 0.1 seconds "entering recovery" but then the screen turns black.
So I tried different TWRP Versions, but the most recent version is twrp-2.8.7.0, but I can't use it to install Lineage OS 17.1.
Even the Lineage OS Recovery isn't working. Same here. After installing and entering recovery, the screen stays black (or the phone is off, not sure)
Any Ideas why it doesn't work? :/
Click to expand...
Click to collapse
I have a similar problem. With my htc m8, the TWRP only works up to version twrp-3.3.1-0-m8.img. Everything beyond that can supposedly be installed successfully (according to the adb terminal), but not started. That means that I cannot install the current Linage 17.xxx correctly.
Strange. I'm using 3.4.0-1 and it works flawlessly. I could install Lineage 17 two months ago with no problem at all
Have you tried to download the image for the M8 using the official TWRP app? to be sure that the image is correct
kadyt said:
Strange. I'm using 3.4.0-1 and it works flawlessly. I could install Lineage 17 two months ago with no problem at all
Have you tried to download the image for the M8 using the official TWRP app? to be sure that the image is correct
Click to expand...
Click to collapse
Yes, I am sure that I use the official version ?!
I'm having a very similar issue with a used phone I just bought. TWRP 2.8.7.0 works (but can't install the latest ROMs), but if I flash the latest version and try to reboot to recovery I end up back in the fastboot menu. This happens whether I use fastboot reboot recovery or the menu.
I have the AT&T version with the latest software I could download. Here's the fastboot information if it helps anyone:
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.42.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA46EWM00439
(bootloader) imei: 358718051679624
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm going to keep digging for a bit, I'll post an update here if I figure anything out.
I got it! The firmware was out of date, but AT&T's updater wouldn't give me an OTA. I downloaded and flashed the Lollipop RUU exe from this thread (AT&T only) and all is well. New fastboot info below with updated version-baseband, version-main, and commitno-bootloader:
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA46EWM00439
(bootloader) imei: 358718051679624
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hopefully others in this thread are having trouble for the same reason and can solve the problem by finding the latest RUU for their model.

Categories

Resources