Develop Bugs

[Q] Soft bricked, can't boot after flashing any Rom

Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.

n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..

Did you recently do the GPE conversion?

May be you should try to flash the stock rom and stock recovery then flash the ruu.

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back

According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone

We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!

Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.

Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...

n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk

n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks

7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?

[Q] Trouble getting back to stock on German One m8

Hello xda-Community!
First off, I have posted this a couple of weeks ago in the general help thread, however it quickly got swarmed and lost, so I wanted to try again.
I have run into some trouble with my O2 HTC One M8. First, my readout from fastboot:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I have been running CM11 for some months and am pretty happy with it, but I want to upgrade to Lollipop. However, the phone won't let me do that, as hboot is only version 3.16.0.0000 and Lollipop needs 3.19 (apparently). The version_main is empty for some reason, I did not erase that part.
But now comes the kicker: To upgrade hboot, I need to return to stock (or set the CID to SuperCID), right?
Now, I cannot return to stock, because there is no RUU / nandroid backup for my CID (O2___102).
As I don't have S-OFF, I cannot install any other RUU. To get S-OFF with SunShine, I need to be on stock though, because right now I get the following error message: "Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best."
So basically: I need to get back to stock to go back to stock, or am I reading this wrong?
Is there a way out of this?
In the general help thread, someone said I should flash a ROM close to stock (he/she suggested Maximus HD) for this to go away, but I cannot flash any ROM besides the CM11 one I am already on, as none of the other ROMs allow me to boot - I simply get stuck during boot-up and have to reflash CM11 to use the phone.
The recovery I am using is TWRP 2.7.0.2 if that information is necessary or helpful.
Thanks in advance for anybody who can help me.

Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376

ckpv5 said:
Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Well god damn it. I had tried those but apparently, they got corrupted in the download. Just tried again (from my laptop) and it worked marvellously. Thank you for your reply!

[Q] Problems reverting back to stock

Hey Guys, First off, this is the first thread I've created so sorry if this has already been posted.
So I'm having issues reverting back to stock, using a stock nandroid back up from Mr Hoffs page (http://forum.xda-developers.com/showthread.php?t=2701376), my CID is OPTUS001 and did the restore from the back up all goods, but then when I do OTA and after is has finished installing (I think the update is 1.54). So then when it has booted back up, My wifi is no longer working, It wont switch on.
I'm going back to stock to update my phone as far as possible, hopefully up to Lollipop.
Help me out guys, surely there is a way to revert back to complete stock without the need to S-Off the device.
If you need information about my phone, Just ask, hopefully I will be able to answer it!
Regards,
Marcus Garces

Post the output of fastboot getvar all and we'll go from there (remove the IMEI and serial number for security)

EddyOS said:
Post the output of fastboot getvar all and we'll go from there (remove the IMEI and serial number for security)
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.00
(bootloader) version-baseband: 1.19.213311
(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: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: OPTUS001
(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: cdb72c6d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
Before you ask, I have no idea why Version main is blank.

You have blank version-main because you use old outdated TWRP 2.7.x.x
Use 2.8.1.0 for your hboot version
You can't do update with that backup which is too low version for your device.
You need 2.07.980.2 backup

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(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: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm on last TWRP (2.8.5.0) and my main is not shown.. what stock recovery and firmware should i use ?
Thanks!

c1scolici said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
I'm on last TWRP (2.8.5.0) and my main is not shown.. what stock recovery and firmware should i use ?
Thanks!
Click to expand...
Click to collapse
Once the version-main already been removed by the old TWRP version, installing the latest TWRP will not bring it back. You need to restore the firmware then flash latest TWRP will fix it.
Based on your info, you need 3.32.111.3, restore the 3.32.111.3 backup and its stock recovery. Do OTA update to the latest 4.19.111.2

Ok, so.. i found the 3.32.111.3 backup but i didn't find the 3.32.111.3 recovery.. can i put on 3.32.771.3 recovery ?
LE: I just found M8_UL_Stock_Recovery_3.32.111.3.img , i think this is ok
Thanks!

c1scolici said:
Ok, so.. i found the 3.32.111.3 backup but i didn't find the 3.32.111.3 recovery.. can i put on 3.32.771.3 recovery ?
LE: I just found M8_UL_Stock_Recovery_3.32.111.3.img , i think this is ok
Thanks!
Click to expand...
Click to collapse
Yep ... only use 3.32.111.3 recovery

Ok, let's get to work. Thanks for helping !
---------- Post added at 06:39 PM ---------- Previous post was at 06:02 PM ----------
I can't restore the backup because..i can't found it in recovery. . I put it on both sd (internal and external ).. any ideas why ?

stock recovery or back to stock neew new firmware
Hi
I running venoms 3.20 rom and want to go to 4.2 but with being s-on I cant just update the firmware
I have tried to use a stock recovery backup but it doesn't work I don't get any OTA updates for the new firmware
I don't really know which way to go either with a stock recovery or a nan droid backup to get me back to stock
I have tried different stock recovery's but im not sure on the ones I need I have tried 3.28.401.9 and 3.29.161.5 stock recovery's
not sure which nandroid back to use
I not bothered if I have to go back to stock I just need the latest firmware to upgrade to the new rom
I will post my get all ver
hope somebody can help me im totally stuck and read lots of different things and don't fancy bricking my phone
if there's a step by step guide it would be great or any advice
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.29.161.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Many thanks
Benitez1

Go here : http://forum.xda-developers.com/showthread.php?t=2701376
-from CID VODAP001 / VODAP102 / VODAP304 / VODAP405 / VODAPE17 / VODAPD18 section , download 3.29.161.5 - TWRP(as your version-main: 3.29.161.5)
-from https://www.androidfilehost.com/?w=files&flid=24386 download 3.29.161.5 recovery.img (as your version-main: 3.29.161.5)
To get back to stock use this tutorial with those 2 files above: http://venomroms.com/firmware_443/
Good luck

ckpv5 said:
You have blank version-main because you use old outdated TWRP 2.7.x.x
Use 2.8.1.0 for your hboot version
You can't do update with that backup which is too low version for your device.
You need 2.07.980.2 backup
Click to expand...
Click to collapse
Sorry for the late response, been busy with school.
So what do I do now? I have installed 2.1.8.0. Here is my getvar:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(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: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: OPTUS001
(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: cdb72c6d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
As you can see, version main is still blank... so what do I do now? Do I still get a 2.07.980.2 backup and where can I find one?

mgarces024 said:
As you can see, version main is still blank... so what do I do now? Do I still get a 2.07.980.2 backup and where can I find one?
Click to expand...
Click to collapse
Flashing TWRP 2.8.1.0 alone won't fix that blank version-main
You need to restore 2.07.980.2 backup and its stock recovery then do OTA to 3.32.980.4 this will fix the missing version-main.
I have all the needed files .. I'll upload them if you still interested to fix your device.

ckpv5 said:
Flashing TWRP 2.8.1.0 alone won't fix that blank version-main
You need to restore 2.07.980.2 backup and its stock recovery then do OTA to 3.32.980.4 this will fix the missing version-main.
I have all the needed files .. I'll upload them if you still interested to fix your device.
Click to expand...
Click to collapse
Please do! I'd really like if you uploaded them.

mgarces024 said:
Please do! I'd really like if you uploaded them.
Click to expand...
Click to collapse
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 2.07.980.2 - https://mega.co.nz/#!uwQgjLbB!S28B3t5rxGciffiuUwChR_rei6v_Z27gXLwZnT5svzU
3. Download stock 2.07.980.2 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/2.07.980.2_recovery.img/download
4. Extract the downloaded 2.07.980.2_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 2.07.980.2 folder (not 2.07.980.2_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./2.07.980.2
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 2.07.980.2_recovery.img
12. reboot - check for OTA, download, install
13. your device should be updated to 3.32.980.4, repeat step 12 and see whether any update for lollipop as I the last time I checked, nothing yet.
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.4.0/2.8.5.0 after last OTA

ckpv5 said:
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 2.07.980.2 - https://mega.co.nz/#!uwQgjLbB!S28B3t5rxGciffiuUwChR_rei6v_Z27gXLwZnT5svzU
3. Download stock 2.07.980.2 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/2.07.980.2_recovery.img/download
4. Extract the downloaded 2.07.980.2_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 2.07.980.2 folder (not 2.07.980.2_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./2.07.980.2
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 2.07.980.2_recovery.img
12. reboot - check for OTA, download, install
13. your device should be updated to 3.32.980.4, repeat step 12 and see whether any update for lollipop as I the last time I checked, nothing yet.
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.4.0/2.8.5.0 after last OTA
Click to expand...
Click to collapse
Very Pleased to report, Everything went down to plan! Although it would be nice to be on Lollipop... is there anyway of getting Lollipop through rom flashing? or is it not possible?

mgarces024 said:
Very Pleased to report, Everything went down to plan! Although it would be nice to be on Lollipop... is there anyway of getting Lollipop through rom flashing? or is it not possible?
Click to expand...
Click to collapse
Eventually lollipop will come to your carrier ... it just a matter of time.
With hboot 3.19 you can try lollipop custom ROM, only maybe not 100% perfect but you can try and see any big problem or not.

Boot loop problem

Hi, I'm in need of some assistance if anyone is willing to help.
Just updated to Marshmallow few day ago through OTA. Since my M8 has only 16GB of internal storage decided to root so that I can move some apps to SD. It's my first time rooting a device so I searched through the forum and followed these steps:
1) I have succesffully unlocked bootloader
2) flashed TWRP 2.8.7.0
3) downloaded and installed SuperSU-v2.67 ( from chainfire's download page ) via recovery
After that the only way to get to bootloader is to hold volume up+power and after screen goes blank press volume down. No way of getting back to TWRP recovery, even tried factory reset via bootloader and no changes. Any advice would be greatly appreciated.
More info on device:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxx
(bootloader) imei: xxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Boot loop problem solved by flashing RUU found HERE . I still have to figure out what went wrong with rooting in the first place
Edit:
Did it! I got stuck to boot loop again when I accepted automatic install of Super Su in TWRP. Everything worked when I manually intalled Super Su v2.67. Got root access finally

0taurus0 said:
I got stuck to boot loop again when I accepted automatic install of Super Su in TWRP. Everything worked when I manually intalled Super Su v2.67. Got root access finally
Click to expand...
Click to collapse
TWRP isn't updated to root MM, so the result is a bootloop.

M8 stuck whilst loading recovery mode..

So i accidentally wiped the phone including the internal storage and the OS instead of factory resetting (wasn't paying attention) and tried to re install the android marshmallow OS onto the phone which didn't work..
i managed to flash the twrp by following another forum where someone had the same problem, using the adb process to flash the bootloader etc but now i can't access the recovery at all, it just says entering recovery and remains idle until i get bored of waiting and power off.
Can anyone help me?
i can provide whatever information is necessary for you to help, just need my phone revitalised as i desperately need it for my new job that i should hopefully be starting at the end of the week.
thanks in advance!

@mcg0v
post getvar all after removing serialno and imei
this info will help to know which RUU you need to flash and return your device to stock
any info you can provide is helpful

C:\Users\mcg0v\Desktop\Android\sdk-tools\sdk-tools>getvar all
'getvar' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\mcg0v\Desktop\Android\sdk-tools\sdk-tools>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.318s
Hope this helps, I'm really not that good with anything Android related as of yet, but i really need this phone fixed asap.

@mcg0v
you post your issue in the wrong forum
your device is HTC One m7
this forum is for HTC One m8
go to this thread http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
this is for your device ask there some one will guide you

I have quite the same problem (and i have One M8). Can't enter TWRP recovery, bootloop - just shows an endless loading, i can start the phone without that by pushing pwr button/VOL+/VOL- at the same time (fastboot mode - ok). I want to get the stock back, but it's impossible without entering TWRP. Can someone help me please? It seems that i do not understand this thing anymore.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s

andreech95 said:
I have quite the same problem (and i have One M8). Can't enter TWRP recovery, bootloop - just shows an endless loading, i can start the phone without that by pushing pwr button/VOL+/VOL- at the same time (fastboot mode - ok). I want to get the stock back, but it's impossible without entering TWRP. Can someone help me please? It seems that i do not understand this thing anymore.
Click to expand...
Click to collapse
Fastboot erase cache, then flash TWRP again in fastboot. Try TWRP 2.8.1.0, which is an older version (more compatible with your old firmware). Then see if you can boot into recovery.
Or flash signed firmware, to update firmware (yours is ancient) then flash TWRP 2.8.7 and restore a newer stock backup (corresponding to the firmware flashed).

redpoint73 said:
Fastboot erase cache, then flash TWRP again in fastboot. Try TWRP 2.8.1.0, which is an older version (more compatible with your old firmware). Then see if you can boot into recovery.
Or flash signed firmware, to update firmware (yours is ancient) then flash TWRP 2.8.7 and restore a newer stock backup (corresponding to the firmware flashed).
Click to expand...
Click to collapse
Thanks a lot. I've tried the first solution and at least TWRP is now working. I've tried the same thing, but it seems, that it was a wrong version of TWRP

Many apologies, turns out i misread the model and its actually the M7 i have. But im glad that this post is helping others with my original problem and thanks to other members who contributed to helping!
-mcg0v