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?

HTC ONE M8- Stuck In Bootloop After Trying To Update

After Update bootloop ... please help!
Hello everyone!
So im trying to fix this HTC One M8 since yesterday. My gf tried to install the latest update, after she did the phone went into bootloop.
It was rooted, TWRP recovery installed.
Now i tried yesterday to get i back to stock, but strangely nothing seems to work. I downloaded a couple of ruu ZIP files, none of them worked. Only thing worked was the cyanogenmod but well... she wants her phone back to stock
Every Stock-image i could find was for 4.16.401.10, but the phone says its 4.16.401.13.
Please help me! What exactly must i do in order to get i back to stock?
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(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: HTC__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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
EDIT
strange thing is, even with android SDK and USB drivers my laptop wont execute an RUU.exe... it fails due to not finding the device even though its connected to the laptop and i can acess the phones memory

Khaira said:
So im trying to fix this HTC One M8 since yesterday. My gf tried to install the latest update, after she did the phone went into bootloop.
It was rooted, TWRP recovery installed.
Click to expand...
Click to collapse
In addition to stock 4.16.401.13 ROM, you will also need stock recovery. Since TWRP is on the phone, OTA will cause the phone to boot over and over looking for stock recovery (and not finding it).
Khaira said:
Now i tried yesterday to get i back to stock, but strangely nothing seems to work. I downloaded a couple of ruu ZIP files, none of them worked.
Click to expand...
Click to collapse
Unless the RUU zip is 4.16.401.13, its going to fail CID or version checks.
Khaira said:
Every Stock-image i could find was for 4.16.401.10, but the phone says its 4.16.401.13.
Click to expand...
Click to collapse
You can get .13 stock nandroid and recovery here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Note this is a nandroid, and not a flashable ROM zip. So restore according to the instruction given in the same thread.
Khaira said:
strange thing is, even with android SDK and USB drivers my laptop wont execute an RUU.exe... it fails due to not finding the device even though its connected to the laptop and i can acess the phones memory
Click to expand...
Click to collapse
Did you try with the phone in fastboot mode?
Any response if you type the command: fastboot devices
Response should be the phone's serial number if you have fastboot connectivity.
What Windows version?
Also, as previously stated, unless the RUU is 4.16.401.13, it will fail anyway.

I got it! Thanks a lot! Seems really like I was too stupid to find the thread u posted

Khaira said:
Seems really like I was too stupid to find the thread u posted
Click to expand...
Click to collapse
Its actually a bit hard to find, as its in Q&A. Deserves to be made sticky.

Soft Bricked the HTC One M8

HTC One M8
Unlocked and S-off
From UK so with international network
Cyanogenmod 11 i think
Clockwork recovery
Soooo i bought the M8 secondhand with Cyanogenmod installed, however, i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail. since then the error came back and i managed to get a different error on reboot: "root access possibly lost. fix?". I've cleared cache(s) and done a factory reset. No matter what i pressed it would be in a boot loop. I can still get to bootloader and recovery. then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
sorry for sounding very vague / idiotic, i have no idea what i have done and no idea what i am doing to try and fix it. that means sadly i will need to be spoonfed the fix. if you need any more details or pictures of the problem let me know
thanks in advance

josborn42 said:
i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail.
Click to expand...
Click to collapse
Are you trying to update to CM12.1? If so, the error is for a reason, and not to be bypassed in the way you describe.
If you are on an hboot older than 3.19, I don't think it will work with CM12 and 12.1. You'll need to update hboot (and rest of firmware, preferably) to proceed.
Also, CWM may be too old for CM12 as well.
josborn42 said:
then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
Click to expand...
Click to collapse
Not sure what you mean here. Are you trying to install HTC Sync (and corresponding driver) by connecting the phone?
You can just do an XDA search for "simple adb" and you will find a couple really easy adb/fastboot installers.

how do i see what hboot i am on? and how would i update it?
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone) and i've installed a simple ADB/fastboot but i can't see the driver option when trying to add it to my phone on Device manager. i have got to the stage whereby i have the ADB/fastboot folder and have the TWRP file in the same folder, just i cant get any further.
where would i begin getting to cyanogenmod 12.1, or would it be easier to revert back to a basic android os?
i know this is probably incredibly frustrating for you as i am a complete novice, but i greatly appreciate your help
i would post pictures to help but i cant as im a new member, i will when i can

josborn42 said:
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone)
Click to expand...
Click to collapse
This in itself does not mean the phone is not connecting by fastboot. And fastboot is the important thing here, so we can update TWRP, etc.
Try rebooting into fastboot mode, and try the command and see if your phone's ID is returned: fastboot devices
If you don't get the phone's ID and just "waiting for device" you do indeed have some type of USB connectivity problem.
josborn42 said:
how do i see what hboot i am on? and how would i update it?
Click to expand...
Click to collapse
Boot into bootloader, andyour hboot number is listed near the top of the screen.
Since you are s-off, its fairly easy to update the firmware (and I would suggest to update all the firmware, not just hboot) by flashing the proper firmware.zip. But let's determine whether that is even the problem, before we worry about flashing firmwares.

hboot is: 3.16.0
also my phone is detected by my laptop so all is well there
i have installed a simple 15 second ADB file but am unsure how to proceed from here

josborn42 said:
hboot is: 3.16.0
Click to expand...
Click to collapse
Your firmware is very old, so will need to be updated to run CM12.1. Also, newer versions of TWRP will not run with your old hboot.
Do a fastboot getvar all, and post the output, but delete your IMEI and serial numbers (as these are private info). Need more details on the phone (particularly CID) in order to know how to proceed.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s

josborn42 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Click to expand...
Click to collapse
I'm going to suggest WWE/International firmware. The updates are available way before O2 updates.
Download this firmware (it also includes TWRP2.8.4.0). Rename it to firmware.zip and place it into your fastboot folder.
Next, boot into fastboot and change your CID to superCID (it won't flash with the O2 CID)
fastboot devices to make sure you are connected (a bunch of letters and numbers/your serial# means you are)
fastboot oem rebootRUU (a black screen with the HTC logo means you are in RUU mode)
fastboot oem writecid 11111111 (eight ones) You are now superCID!
Now flash the firmware
fastboot flash zip firmware.zip
If you get "error 90 hboot pre-update" (and you probably will with how old your current firmware is) run the same command again and the firmware will flash properly. The first run only updated your hboot.
The process will stop at 75% to 90%. That's normal and gives you a chance to check your console output. The last few percentage is the reboot.
The bar will fill to 100% after you enter fastboot reboot-bootloader
That's it. Good luck!

thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?

josborn42 said:
thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?
Click to expand...
Click to collapse
Yes. But there are more ROMs out there as well. Try them out and find the one that suits your needs best.

hi there i have htc one m8 rooted s-on & software status is modified
i got a new update so i flashed the stock recovery then downloaded the update and pressed install
it was loading the update and suddenly the screen frozen on the htc ONE screen without responding
i tried the volume down + power button nothing happened then i tried volume up + power button
it reboots and freezes on the same screen - tried to remove the sim & sd card but nothing happened
what should i do plz ???
cid : htc_j15
build number : 4.16.401.10

HTC One M8. Noob needs help fixing phone.

Hello, so quite sometime ago I rooted my phone, or unrooted it. I am not sure what the term is, I dont even remember why I done this in the first place. Anyways today I wanted to just put my phone back to like it was when I got it, and in doing so I have actually broke my phone I can't get my phone to boot up anymore, I always get a message saying I have no OS installed. I am really useless with all of this so I would appreciate it if there is a patient person out there who can help me get my phone back on and back to how it was when I recieved it. I am sure I need to add more information but I dont know what so please tell me what you guys need to know and I will try and provide the answers.

This should be the first rule when asking for help.
Post fastboot getvar all result (delete serial & imei no.)
Without this info, no one will be able to offer any help

ckpv5 said:
This should be the first rule when asking for help.
Post fastboot getvar all result (delete serial & imei no.)
Without this info, no one will be able to offer any help
Click to expand...
Click to collapse
Where do I find this?

Do you have fastboot & adb on your PC ? You should have one, if not how can you install a custom recovery and root your device before ?
If you're not sure .. install this : http://forum.xda-developers.com/showthread.php?t=2317790
Put your device in bootloader mode and connect to PC
Open a command prompt and type fasboot getvar all then "enter"
Copy the outcome and paste here

ckpv5 said:
Do you have fastboot & adb on your PC ? You should have one, if not how can you install a custom recovery and root your device before ?
If you're not sure .. install this : http://forum.xda-developers.com/showthread.php?t=2317790
Put your device in bootloader mode and connect to PC
Open a command prompt and type fasboot getvar all then "enter"
Copy the outcome and paste here
Click to expand...
Click to collapse
(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:
(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: O2___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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I think thats what you want right?.

Yes .. that's the one.
You have two options :
Option 1:
Install new stock ROM with a RUU - Download : https://www.androidfilehost.com/?fid=95916177934555499
you need to relock bootloader - run command fastboot oem lock
run RUU (right click the RUU and select run as administrator)
you need to use USB2.0 on your PC
RUU will wipe everything on your device including your files on internal storage
Option 2:
Restore a non-rooted TWRP backup 4.20.206.1
No need to relock bootloader
No internal storage wipes
Read how-to and all the needed files are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck .. I have to sleep now, good night

ckpv5 said:
Yes .. that's the one.
You have two options :
Option 1:
Install new stock ROM with a RUU - Download : https://www.androidfilehost.com/?fid=95916177934555499
you need to relock bootloader - run command fastboot oem lock
run RUU (right click the RUU and select run as administrator)
you need to use USB2.0 on your PC
RUU will wipe everything on your device including your files on internal storage
Option 2:
Restore a non-rooted TWRP backup 4.20.206.1
No need to relock bootloader
No internal storage wipes
Read how-to and all the needed files are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck .. I have to sleep now, good night
Click to expand...
Click to collapse
Option one just stays on updating 0/6 sending and nothing happens. Option 2 doesnt make sense to me, I really have no idea what most of it means.

Ok so this morning I tried option one again. It went through the first 6 stages fine, then it got stuck on the next set of stages at 1/7. When I restart my phone into the recovery screen type thing I have in red letters OS - (4.20.206.1) but I am still unable to start my phone up. I have disabled firewalls and also using USB2.0 when trying to do this process. Maybe this one that has been linked is not the right one for me? Or maybe I am doing something wrong?. I would really love to get my phone back working so all help is really appreciated.
(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:
(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: O2___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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

You have USB/Device connection problem. First it was 0/6 and now 1/7 ...
Which windows version that you use ? try with a Win7 PC .. I don't know many people cannot run RUU on windows higher version that Win7. I don't have problem on any windows version including my current Win 10.
What do you don't understand about option 2 ? It's very straight forward.
Install latest TWRP 2.8.6.0 or TWRP 2.8.7.0 (you need to reunlock bootloader because you relocked it for option 1)
Extract and copy the backup folder to TWRP backup on your device
Restore backup .. done
Or
Just install any of Sense based ROM that available in Development thread to get your device up & running ... then you can start that option 1 & 2 again
But seeing you mentioned OS - 4.20.206.1 in red, you need to get option 1 done because the firmware installation was incomplete

ckpv5 said:
You have USB/Device connection problem. First it was 0/6 and now 1/7 ...
Which windows version that you use ? try with a Win7 PC .. I don't know many people cannot run RUU on windows higher version that Win7. I don't have problem on any windows version including my current Win 10.
What do you don't understand about option 2 ? It's very straight forward.
Install latest TWRP 2.8.6.0 or TWRP 2.8.7.0 (you need to reunlock bootloader because you relocked it for option 1)
Extract and copy the backup folder to TWRP backup on your device
Restore backup .. done
Or
Just install any of Sense based ROM that available in Development thread to get your device up & running ... then you can start that option 1 & 2 again
But seeing you mentioned OS - 4.20.206.1 in red, you need to get option 1 done because the firmware installation was incomplete
Click to expand...
Click to collapse
Yes maybe I do but I am not sure why, maybe I need to look into seeing if my motherboard needs an update or if any windows updates are needed. I am on Windows 7 but like I said, it goes through the first 6 steps then as it boots the bootloader up again I hear the sound that my computer makes when plugging in a USB cable. However even if I leave it, it will not go past 1/7. But if I take the cable out it reconises I have done that so that makes me wonder if it is a USB problem?.
I dont understand option 2 because I dont know anything about all of this, I shouldnt have done it in the first place and I dont even remember why I did. I also must have deleted my backups as I cant find them. The part I was confused at, was which TWRP to get, then how to get it on my phone as my computer does not reconise my phone in the state it is in so I cant just go into the phone and place it. I also dont have an SD card with my phone either.
I will try updating my PC and try and get option 1 working and report back. Thank you for helping by the way, I really appreciate your patience with me.

Try also to install latest HTC USB driver.
Download HTC Sync Manager and install. Then uninstall the HTC Sync Manager but leave the HTC Driver installed.
http://www.htc.com/us/support/software/htc-sync-manager.aspx

Is there a way to wipe this OS version and try this whole thing again? I have found my 2.0 USB ports, I have tried a different cable and it still gets hung up. Only now it doesnt move past the 0/6 whereas it used to go through all of them then into the 1/7 and get stuck on this part. I also can try a different PC if need be.

KDK11 said:
I also can try a different PC if need be.
Click to expand...
Click to collapse
That is what I would suggest.
Also, does your PC have USB 3.0 on the ports? This has been known to cause problems with the RUU.

Ok so I have done the steps suggested now, when I uninstalled the HTC Sync Manager it let the process complete. It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed? Or is there more I need to do now that it actually has turned on?.

KDK11 said:
It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed?
Click to expand...
Click to collapse
Looks that way. It should boot into OS after its done optimizing all the apps, which is normally pretty slow (with that many, it will take 10 or more) since Android moved from Dalvik to ART.

Well I would like to say a massive thank you for the help I really appreciate the patience and help. So thank you again. I would have been lost without you's.

KDK11 said:
Ok so I have done the steps suggested now, when I uninstalled the HTC Sync Manager it let the process complete. It is now on a screen which says Android is upgrading, optimizing app 17-261. Is that my phone fixed? Or is there more I need to do now that it actually has turned on?.
Click to expand...
Click to collapse
That's it ... nothing else to do .. run the setup wizard and enjoy your device
KDK11 said:
Well I would like to say a massive thank you for the help I really appreciate the patience and help. So thank you again. I would have been lost without you's.
Click to expand...
Click to collapse
No problem .. glad that we could help

O2 RUU Marshmallow CID O2_001 pleaseee
Hi!
I have an HTC One M8 from O2 UK, that i give me a lot of problem after updating to Marshmallow.
After successfully complete the update i have done a factory reset which i guess it soft brick my phone.
It will show optimizing apps, after that starting apps and is stuck there until battery dies. I try many methods, formatting cache partition from recovery menu, made another factory restore from fastboot, I even left it plugged one night and nothing.
The only hope is if i find a RUU for CID O2_001
The phone is S-ON non rooted, i unlock then re lock boot loader thanks to htcdev website.
adb fastboot getvar command show this.
< waiting for device >
(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.13.206.5
(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: O2___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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.126s
Please help me made the phone working again!
Thank you!

cossty said:
Hi!
I have an HTC One M8 from O2 UK, that i give me a lot of problem after updating to Marshmallow.
After successfully complete the update i have done a factory reset which i guess it soft brick my phone.
It will show optimizing apps, after that starting apps and is stuck there until battery dies. I try many methods, formatting cache partition from recovery menu, made another factory restore from fastboot, I even left it plugged one night and nothing.
The only hope is if i find a RUU for CID O2_001
The phone is S-ON non rooted, i unlock then re lock boot loader thanks to htcdev website.
adb fastboot getvar command show this.
< waiting for device >
(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.13.206.5
(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: O2___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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.126s
Please help me made the phone working again!
Thank you!
Click to expand...
Click to collapse
Hello,
In this thread you will find the firmware for your phone. It looks like you know the process of installing your firmware, so if I were you I'd down load the proper firmware and try the whole process all over again.

Jerrel7 said:
Hello,
In this thread you will find the firmware for your phone. It looks like you know the process of installing your firmware, so if I were you I'd down load the proper firmware and try the whole process all over again.
Click to expand...
Click to collapse
Hi!
I didn't find because it is to new. It's an O2 UK, android 6 version, cid O2_001.
I did something else, i flashed TWRP recovery and then i flash latest InsertCoin rom, and now the phone it is working again.
Thank you!

HTC 820 cannot enter TWRP recovery

The phone itself boots up fine, however whenever I try to load up recovery (I have flashed TWRP) some red text flashes, then it loads into fastboot.
I heard it might be a cache or bad TWRP file, however I have no idea how to fix either of them.
Any advice would be greatly appreciated.

IVIemories said:
The phone itself boots up fine, however whenever I try to load up recovery (I have flashed TWRP) some red text flashes, then it loads into fastboot.
I heard it might be a cache or bad TWRP file, however I have no idea how to fix either of them.
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Which ROM u running KK or LOLLI ?
TWRP for kk & Lo are in this ZIP
Download : https://mega.nz/#!yQ1RRZxK!fzcw9gdxgYd4Qd-8FTPoYuJroZ6RGHHkeb6381NncEo
how to flash here: https://www.youtube.com/watch?v=xsn6co4Ve6M

I tried flashing the stock recoveries, but it gave the same result. Whenever I select recovery, the 'entering recovery' text flashes for a second, then the phone goes into the fastboot menu.
I'm running KK by the way.

Whats you complete model number like 820U | 820n | 820Q | 820S
Here is Twrp recovery for kk https://mega.nz/#!zM8G2AwJ!6QH8eZYZ8aoe_ap_UGu1iLf_NnqsnD4bhHp2u42MH8k
Here is stock recovery for kk https://drive.google.com/file/d/0B2DumUOvI46KM2toeGR3QXpLYW8/view?pref=2&pli=1 [ for 820U ]
Code:
how to flash here [video guide: https://www.youtube.com/watch?v=xsn6co4Ve6M
More info :http://forum.xda-developers.com/desire-820/development/play-recovery-htc-desire-820-dual-sim-t3225782
Keep in mind to flash any custom recovery (twrp,cmw,philz touch) you need to have you bootlodder unlocked
If stock is not working can you may flash TWRP

The phone model in both settings and hardware info only displays as HTC_0PFJ50. Again, both flashes work fine, it's just that whenever I enter recovery, it goes into the fastboot menu instead of the recovery menu (bootloader has been unlocked).

IVIemories said:
The phone model in both settings and hardware info only displays as HTC_0PFJ50. Again, both flashes work fine, it's just that whenever I enter recovery, it goes into the fastboot menu instead of the recovery menu (bootloader has been unlocked).
Click to expand...
Click to collapse
Can you do "fastboot getvar all" and post the result here

Whenever I try that, it only comes up with the 'adb help' list, in fact all the adb commands ends up with the help menu apart from 'adb devices' which results in
(List of devices attached
HT57NYC00235 offline)
Fastboot getvar all ends with a endless <waiting for device>. USB debugging has been turned on.

IVIemories said:
Whenever I try that, it only comes up with the 'adb help' list, in fact all the adb commands ends up with the help menu apart from 'adb devices' which results in
(List of devices attached
HT57NYC00235 offline)
Fastboot getvar all ends with a endless <waiting for device>. USB debugging has been turned on.
Click to expand...
Click to collapse
which fastboot & adb drivers you have , you need HTC this
https://mega.nz/#!6BcyEYZT!fMpb8fsPwgQ8Hryci1z3YmMcN43tM0gZqydV3I8dz30

It was still giving the same thing, until I realized the device wasn't being recognized.
I installed the ADB driver in device manager and 'fastboot getvar all' got me this:
(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: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT57NYC00235
(bootloader) imei: 355719062070426
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(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: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!

IVIemories said:
It was still giving the same thing, until I realized the device wasn't being recognized.
I installed the ADB driver in device manager and 'fastboot getvar all' got me this:
(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: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT57NYC00235
(bootloader) imei: 355719062070426
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(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: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Click to expand...
Click to collapse
Code:
./
-Read me well before you flash this recovery
/.
THIS twrp recovery is for your model A51_TUHL, but for lollipop
hence, it won't run on your kitkat which you have rite now . Can you make OTA update from your phone & get lollipop but for that too you need to flash your working stock recovery & re-lock boot lodder.
After this is done Go for lollipop OTA update & when your phone will Run lollipop
After that again Unlock bootlodder,
Code:
fastboot flash unlocktoken unlock_code.bin
- Unlocking bootlodder will wipe your device so make all types of backup
After bootlodder is unlocked stay at bootlodder and flash this twrp recovery 2.8.7
To conclude i think there is no twrp for kitkat your model .
LINKS:
Download Link: https://drive.google.com/open?id=0B1rsNvL8ZF-RMHNab3VJNFVaNEE
TWRP discussion : http://forum.xda-developers.com/des...p-2-8-7-0-64bit-a51ul-a51tuhl-europe-t3287214
:good:

Flashing the stock recovery rom still doesn't allow me to enter recovery. Relocking the ROM and checking for software update tells me that my phone is up to date. (not sure if this has anything to do with having no recovery). Now the bootloader is stuck in 'relocked' mode, and trying to unlock it again fails because I cannot enter recovery.
I'm probably taking up too much of your time anyway, and since I can use my phone without any problems (just no root) I think I might as well give up at this point. Maybe i'll figure it out eventually after a lot of trial and error.
Regardless, thank you very much for the continued support!

Its your wish

h1dd3n_sn1p3r said:
Which ROM u running KK or LOLLI ?
TWRP for kk & Lo are in this ZIP
Download : https://mega.nz/#!yQ1RRZxK!fzcw9gdxgYd4Qd-8FTPoYuJroZ6RGHHkeb6381NncEo
how to flash here: https://www.youtube.com/watch?v=xsn6co4Ve6M
Click to expand...
Click to collapse
820n running LOLLlPOP rom . are these recoveries are compatible to flash on my device?

android201 said:
820n running LOLLlPOP rom . are these recoveries are compatible to flash on my device?
Click to expand...
Click to collapse
yes go ahead
BTW which you are going to flash ?

h1dd3n_sn1p3r said:
yes go ahead
BTW which you are going to flash ?
Click to expand...
Click to collapse
i need to flash again my device official rom or custom rom 820n a51_ul because it has a extraordinary screen saver. i need to remove it. i did factory reset but its still there.

android201 said:
i need to flash again my device official rom or custom rom 820n a51_ul because it has a extraordinary screen saver. i need to remove it. i did factory reset but its still there.
Click to expand...
Click to collapse
hmm ok

h1dd3n_sn1p3r said:
hmm ok
Click to expand...
Click to collapse
are these recovery compatible with the d820u ? i have a d820u running on lollipop with bootloader unlocked
edit :nvm i got twrp 2.8.7 working

Hi.
I seem to be having the same issue as the original poster - on the same model hardware, whenever I attempt to load into recovery, it appears the system starts loading it then immediately bails back to Fastboot mode. This occurs using the recovery image linked from this thread, as well as with various other recovery images that I've tried. Each recovery image loads into the phone without error, but every time the result is the same.
Otherwise the phone boots without issue and appears to operate normally. Note that I have successfully unlocked the boot partition.
I've included the output of "getvar all" below, however one thing that may be relevant that I have noticed is that when I load into HBoot there is a brief moment where it appears the phone is verifying *.zip images. It's too quick for me to get file names, but the only thing I can think of is that it looks like it's overwriting existing partitions with stock images every time HBoot loads. Is this a thing?
Any assistance would be appreciated.
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.17.980.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT54DYC00362
(bootloader) imei: 355719061276677
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(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: a82a385a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
finished. total time: 0.007s

Hi This seems to be the same issue that I'm having. Getting bootloop on everything, when i select recovery it bootloops. I relocked the bootloader now i get errors trying to unlock. I've tried to fastboot new recovery but get Signature verify fail. I'm not sure what happened to it as a friend brought it like this. they said they did the official update then it went in to bootloop. The bootloader said "RELOCKED" So i presume they've already rooted this and put a custom recovery on but then its been deleted when they've done the official update to lollipop.
On bootloader it says Software status: Official
This is the dual sim 820n version. I've asked for help in a few threads but with no replys but came across this thread which more or less fits what my issue.
Please this is driving me mad now. Thanks

h1dd3n_sn1p3r said:
Whats you complete model number like 820U | 820n | 820Q | 820S
Here is Twrp recovery for kk https://mega.nz/#!zM8G2AwJ!6QH8eZYZ8aoe_ap_UGu1iLf_NnqsnD4bhHp2u42MH8k
Here is stock recovery for kk https://drive.google.com/file/d/0B2DumUOvI46KM2toeGR3QXpLYW8/view?pref=2&pli=1 [ for 820U ]
Code:
how to flash here [video guide: https://www.youtube.com/watch?v=xsn6co4Ve6M
More info :http://forum.xda-developers.com/desire-820/development/play-recovery-htc-desire-820-dual-sim-t3225782
Keep in mind to flash any custom recovery (twrp,cmw,philz touch) you need to have you bootlodder unlocked
If stock is not working can you may flash TWRP
Click to expand...
Click to collapse
Mine is 820q on kk can you send me the correct link as the given link did not work