Develop Bugs

[RUU] VZW 3.10.605.7 & 3.37.605.7 0PJAIMG Signed

Verizon RUU 3.10.605.7 & 3.37.605.7 0PJAIMG Signed​
Disclaimer:
Flash at your own risk!
This will wipe your entire phone, including internal sdcard. The only thing not wiped is the external(removable) sdcard
This will not effect s-off status.
How To Flash:
Check MD5 sum and make sure it is correct
Rename file to exactly 0PJAIMG.zip ([ZERO]PJAIMG.zip)
Place file on fat32 formated external sd card in no folders
Boot to aboot (power off phone, hold volume down and power at the same time)
Use volume keys to navigate to download mode and select with the power button.
Once in download mode it should automatically find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, it will try to boot up, but will just bootloop.
Boot back to aboot ( hold power and vol up until the screen goes black, and then while still holding power slide your finger down and hold vol down until aboot comes up).
Select recovery from the menu. Once you see a red triangle, hold down the power button and tap vol up once, and then release the power button.
Select wipe data / factory reset. The phone will reboot several times, once its done it will boot up to stock 3.10.605.7 / 3.37.605.7
DOWNLOAD
0PJAIMG_HIMA_WL_L5[email protected]50918_CNV_VZW_1.21_002_release_453147_signed_1 zip
MD5: 02b2edc731b8fc089dd8575efbe41caf
DOWNLOAD
0PJAIMG_HIMA_WL_M6[email protected]60105_CNV_1.26_002_release_469809_signed_1 zip
MD5: df6b0c42bdd17edc605034ecd577f023​
.

Other M9 Files:
https://androidfilehost.com/?w=files&flid=46151

Problems Flashing / Not Finding File:
Make sure md5 matches
Make sure sdcard is formated to fat32 (exfat)
Make sure the file is named correctly - 0PJAIMG.zip ([ZERO]PJAIMG.zip)
If windows is set to hide file extensions, make sure the file is not named 0PJAIMG.zip.zip
Make sure the file is on the external (removable) sdcard, not the internal sdcard.
Make sure you are flashing to the right model (HTC6535LVW) (cid: VZW__001)

Thought this might be usefull to some people. Merry Christmas!

Links temporarly down. Uploading to AFH now.
UPDATE: New links are up!

Is this the official marshmallow RUU?
Sent from my HTC6535LVW using Tapatalk
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
Never mind I see it's 5.1.1
Sent from my HTC6535LVW using Tapatalk

dajmanjt said:
Is this the official marshmallow RUU?
Sent from my HTC6535LVW using Tapatalk
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
Never mind I see it's 5.1.1
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I wish it was. I hear its set to start rolling out today.

cmlusco said:
Verizon RUU 3.10.605.7 0PJAIMG Signed
0PJAIMG_HIMA_WL_L5[email protected]50918_CNV_VZW_1.21_002_release_453147_signed_1​
Disclaimer:
Flash at your own risk!
This will wipe your entire phone, including internal sdcard. The only thing not wiped is the external(removable) sdcard
This will not effect s-off status.
How To Flash:
Check MD5 sum and make sure it is correct
Rename file to exactly 0PJAIMG.zip ([ZERO]PJAIMG.zip)
Place file on fat32 formated external sd card in no folders
Boot to aboot (power off phone, hold volume down and power at the same time)
Use volume keys to navigate to download mode and select with the power button.
Once in download mode it should automaticly find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, you will be on stock 3.10.605.7
DOWNLOAD
0PJAIMG_HIMA_WL_L5[email protected]50918_CNV_VZW_1.21_002_release_453147_signed_1 zip
MD5: 02b2edc731b8fc089dd8575efbe41caf​
.
Click to expand...
Click to collapse
Did you verify / test that it wipes? The hsm ones so far haven't wiped.
Sent from my SM-T810 using Tapatalk

dottat said:
Did you verify / test that it wipes? The hsm ones so far haven't wiped.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Yes i believe it does. When i flashed it all userdata was wiped, and this is found within in the ruu.
DelUserData:0
modelid: 0PJA30000
cidnum: VZW__001
mainver: 3.10.605.7
btype:1
aareport:1
hbootpreupdate: 3
nohardreset: 1
resparseoption: -S800M
erasepartition: cache
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
eraseonsoff: frp
eraseonflash: cota
erasepartition: ddr
erasepartition: carrier
I believe it depends on what option you choose while in hsm. If you get the update file, it does not wipe. But if you get the repair file, it does. This is the repair file.

cmlusco said:
Yes i believe it does. When i flashed it all userdata was wiped, and this is found within in the ruu.
DelUserData:0
modelid: 0PJA30000
cidnum: VZW__001
mainver: 3.10.605.7
btype:1
aareport:1
hbootpreupdate: 3
nohardreset: 1
resparseoption: -S800M
erasepartition: cache
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
eraseonsoff: frp
eraseonflash: cota
erasepartition: ddr
erasepartition: carrier
I believe it depends on what option you choose while in hsm. If you get the update file, it does not wipe. But if you get the repair file, it does. This is the repair file.
Click to expand...
Click to collapse
Interesting change on their part.
Sent from my Nexus 6 using Tapatalk

@dottat, how is this different than the one you have posted in the "Stock 5.1 resources" thread ? The version # is the same.

hallstevenson said:
@dottat, how is this different than the one you have posted in the "Stock 5.1 resources" thread ? The version # is the same.
Click to expand...
Click to collapse
This is an ruu not a twrp nand.
Sent from my Nexus 6 using Tapatalk

And I don't believe this will wipe. Deluserdata is set to 0
Sent from my Nexus 6 using Tapatalk

dottat said:
This is an ruu not a twrp nand.
Click to expand...
Click to collapse
Ahhh, I didn't look that closely, to be honest, at either one. With the one you posted, I was only interested in the "firmware" portion anyway.

dottat said:
And I don't believe this will wipe. Deluserdata is set to 0
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I seen that, but then it says eraseonflash userdata. I dont have my m9 right now, im an idiot and bricked it. I will do further testing when i get it back.
Can anyone whos downloaded and flashed it so far confirm if it wipes or not? Any other issues?

cmlusco said:
I seen that, but then it says eraseonflash userdata. I dont have my m9 right now, im an idiot and bricked it. I will do further testing when i get it back.
Can anyone whos downloaded and flashed it so far confirm if it wipes or not? Any other issues?
Click to expand...
Click to collapse
If there's no userdata.img it won't wipe.
Sent from my Nexus 6 using Tapatalk

cmlusco said:
I seen that, but then it says eraseonflash userdata. I dont have my m9 right now, im an idiot and bricked it. I will do further testing when i get it back.
Can anyone whos downloaded and flashed it so far confirm if it wipes or not? Any other issues?
Click to expand...
Click to collapse
i can confirm that it does not wipe. Used it earlier to get ready for MM update. No issues otherwise. @dottat suggested that after flashing, just do a system reset and it will serve the purpose

Posting my experience flashing this for what it's worth as the process went a bit different than described in the OP, just in case anyone gets confused or worried if the same thing happens to them.
When I rebooted using power+vol down with the file on my ext sdcard it immediately gave me the message that it found the zip file and asked if I wanted to flash it and if so, press vol up to flash. Did that.
Phone went through the process, rebooting once, then it got to being complete and said to press the power button to continue at the top, and at the bottom it said press power to shutdown. I did. After a few minutes I pushed the power button again and after a minute or so it booted up and the Verizon screen came on. That took a little while, then it went into the OS and started optimizing apps. After that it was up and running.
So no bootlooping step for me. Everything just happened in a very straightforward manner.
I was coming off an earlier RUU since my phone had just been unlocked and s-offed and apparently had been relocked or a refurb so Cykhet flashed the 1.x RUU in order to be able to unlock it.
I can also confirm that it does not wipe internal card/user data.

feralicious said:
Posting my experience flashing this for what it's worth as the process went a bit different than described in the OP, just in case anyone gets confused or worried if the same thing happens to them.
When I rebooted using power+vol down with the file on my ext sdcard it immediately gave me the message that it found the zip file and asked if I wanted to flash it and if so, press vol up to flash. Did that.
Phone went through the process, rebooting once, then it got to being complete and said to press the power button to continue at the top, and at the bottom it said press power to shutdown. I did. After a few minutes I pushed the power button again and after a minute or so it booted up and the Verizon screen came on. That took a little while, then it went into the OS and started optimizing apps. After that it was up and running.
So no bootlooping step for me. Everything just happened in a very straightforward manner.
I was coming off an earlier RUU since my phone had just been unlocked and s-offed and apparently had been relocked or a refurb so Cykhet flashed the 1.x RUU in order to be able to unlock it.
I can also confirm that it does not wipe internal card/user data.
Click to expand...
Click to collapse
Thanks for the feed back. It may bootloop and it may not, depending on your previous setup, since it does not wipe data.

cmlusco said:
Thanks for the feed back. It may bootloop and it may not, depending on your previous setup, since it does not wipe data.
Click to expand...
Click to collapse
If it's appearing to be bootlooped when coming from a custom rom that simply means it needs a factory reset to continue. On the M8 we had guys/gals restoring from CM and expecting the phone to boot with CM /data and for obviously resets it will not. Simple factory reset fixes that.

Stock Recovery Issue

Everytime i try and flash the stock image in fastboot it fails when it gets to anything pertaining to the bootloader
FAILED (remote: Do not allow to flash Bootloader image on Unlock device)
My device is unlocked but to try and compat this i even try to re-lock the device which also fails:
FAILED (remote: oem lock back is forbidden)
Im stuck, i cant use the flashall because it fails, i cant individually flash files because the bootloader items fail,
im at a loss as to what to do.
Im able to flash a custom recovery but i cant do anything with it, except try and flash modem items with twrp which also did nothing.

brother, i am sorry for your condition , i dont have much knowledge on such things, but i once had MotoG, i used to flash Stock files with this method..
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
if you are flashing Stock files, then Bootloader need not to be stayed UNLOCKED..
hope you get any idea from there.. all the best
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
look in to this also :
https://forum.xda-developers.com/mo...e-restore-moto-e-2015-stock-firmware-t3054303
this might give u anyidea

Did you have TWRP installed before you tried to flash stock Rom ? I'm guessing thats why its failing , but i dont know how to fix

maybe you're trying to flash older version of bootloader than the one you've already got? besides you don't need to flash bootloader to lash the rest, like system, modem or kernel

Okay so i know what my problem is i just dont know how to solve it:
I have a partially unlocked bootloader. is i do the fastboot oem device-info command, it tells me that my bootloader is unlocked but im unable to flash bootloader images (Device critical unlocked: false)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Device Secure boot: yes
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.080s]
finished. total time: 0.081s
Does anyone know how to get Device critical unlocked: true?

I stuck in the bootanimation and i cant flash a stock rom because there is no such thing. I found one, but this is no flashable zip. And the "flashall.bat" doesnt work. CM also doesnt work. I dont know what to do now.
Edit: Now i dont get into twrp recovery. With adb and with the hardware its not possible to enter twrp.

Did anyone found any solution? I am in same situation...

Found
flash only boot and system, not bootloader

finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!

nandakis4 said:
finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!
Click to expand...
Click to collapse
if you have the stock rom just follow the trouble shooting guide at the start of this thread , should work

Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??

nandakis4 said:
Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??
Click to expand...
Click to collapse
I am having the same issues:
I cannot flash anything pertaining to the bootloader, this is the official flash list, open fastboot and paste this entire list, when its finished you will see "failed" next to anything pertaining to the bootloader. And therein lies the issue, i havent found a soloution and ive been searching for 2 months now
fastboot flash partition gpt_both0.bin
fastboot flash sec sec.dat
fastboot flash apdp dp_AP_signed.mbn
fastboot flash msadp dp_MSA_signed.mbn
fastboot flash prov prov32.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devcfgbak devcfg.mbn
fastboot flash lksecapp lksecapp.mbn
fastboot flash lksecappbak lksecapp.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash cache cache.img
fastboot erase userdata
FYI i have unlocked my bootloader, and it wont let me lock it again

@nandakis4 Did you manage to solve your issue?
@itsjustbilly Why are you flashing the bootloader? It will fail if it's unlocked.
I'd want to go back to stock to start off fresh, but these are some discouraging stories.

cyrrrinda said:
Found
flash only boot and system, not bootloader
Click to expand...
Click to collapse
Please confirm if you were able to revert to MM without losing your signal.
Edit: It crossed my mind just now. TWRP has the ability to backup the modem so surely you could use it if you were to have problems with the signal later? Provided you can access the recovery of course, but that doesn't seem to be a problem in most cases.

qcn backup
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?

cyrrrinda said:
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?
Click to expand...
Click to collapse
Do 2G and 3G work? My phone can detect 4G, but not 2G and 3G.
You've probably solved the sound issue by now, otherwise have a look at this thread.

Is my HTC 10 another Brick for the USA-MEX wall?

Hi Guys! I appreciate any help or orientation to find out how should I proceed,
I don't know why my phone just got Brick yesterday, it was running fine for two months since the last Room's flash, suddenly I notice an estrange behavior of the system, then the capacitive buttons were not responding nor its backlit appear when I touch them, the home button and the fingerprint and everything else was working fine, so I think that with a simple Reboot it will be back to normality. For my disgrace, it enter in a Bootloop in the HTC logo screen and for my surprise when I manage to get to the Bootloader and try to enter to the Download and Recovery mode get me to the same HTC logo Bootloop!!
The principal suspect for me is that like 15 days ago a installed the TotallyFreeVPN app to see some Japanese Netflix
To complicate the things I want to make my phone thefts proof, so I disable usb debugging and OEM unlocking and installed Cerberus with the option of block usb debugging and also in security I enable the encrypted data option for every reboot or when enter in recovery.
My only hope is that you know if something can be done from the Bootloader to unbricked?
I attach the only two screens I have access right now
HTC 10
Firmware 2.41.401.4
Leedroid V3.6.1
Unlocked Bootloader
S-OFF
TWRP 2.8.4
I manage to run some fastboot commands from Bootloader, getvar all give me the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT64EBN02616

flash a stock ruu

If your phone will still power on, it's not bricked.

BrianKuo1853 said:
flash a stock ruu
Click to expand...
Click to collapse
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:

ALOMAJEMO said:
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
Click to expand...
Click to collapse
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on

Yeah and use the full version, not the NoWipe...

I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.

j to the 4n said:
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Click to expand...
Click to collapse
Sneakyghost said:
Yeah and use the full version, not the NoWipe...
Click to expand...
Click to collapse
Thank for your tips guys,
I follow exactly the order you suggest my good j to the 4n, and I download the firmware from your useful thread Sneakyghost, but still, I can not get it out of the Bootloop my friends
Dont you think my case is very strange?
If it serves for any other suggestion, I I add the following details
-The only image that is not flashing is rcdata, everything else is flashing OK
-I buy a microsd card class 10 of 32GB only to discard that the old microsd card of 3GB was not reading the RUU zip file.
-I optained the zip file, from the RUU.exe with the same version of the firmware 2.41.401.4 (the full version) and I copying it from the Temp files in Windows.
-With the microSD in FAT32 format I put the RUU zip file with the 2PS6IMG.zip name
-After flashing all the img files and rebooting to bootloader, then I inserted the card and select Download mode, where is supposed should appear the screen that jichuan89 mention to flash the RUU, but again nothing happen.
-Also I should say that I try also with the firmware and RUU version 2.41.617.3 (the corresponding for my model 2PS6500 in the back) but the last I have was the 2.41.401.4 with superCID and cidnum change it to HTC-001.
-And also among the hundreds of attempts I have executed fastboot erase userdata, erase cache, erase system, to try to clean any corrupt file.
Do you think there is any hope yet?
Once again thank you for your support guys!:good::good:

singlemalt said:
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
Click to expand...
Click to collapse
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL

ALOMAJEMO said:
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
Click to expand...
Click to collapse
Haha...we have two bricks for the wall now...do you know if Donald would cover shipping costs from Argentina?

curious if anyone know how to view the firmware if cannout access downlad mode

venom55521 said:
curious if anyone know how to view the firmware if cannout access downlad mode
Click to expand...
Click to collapse
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........

Mr Hofs said:
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Click to expand...
Click to collapse
my bad,i was looking around for info and ideas and just had a question when i was reading it

venom55521 said:
my bad,i was looking around for info and ideas and just had a question when i was reading it
Click to expand...
Click to collapse
Please pick up a sledgehammer and smash your device....... it's the best for all of us.

Mr Hofs said:
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Click to expand...
Click to collapse
i realize you help a lot people out which is appreciated ,but being rude is pointless

venom55521 said:
i realize you help a lot people out which is appreciated ,but being rude is pointless
Click to expand...
Click to collapse
Your interpretation of the situation. I'm honest, not rude.

how to upadate hboot from 3.16 to 3.19 ?

I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone

sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
post the result of fastboot getvar all ( after removing serialno and mei )

sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.

redpoint73 said:
You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware.
Click to expand...
Click to collapse
Here's something I just learned recently (2 or 3 mos ago), although I haven't been able to test it myself since my M8 is S-Off.
When flashing an RUU.zip or signed firmware.zip from extSD instead of from your PC, relocking your bootloader isn't necessary.
Like I said, I haven't confirmed it myself, but the person who told me that I consider a reliable source. He was positive about it with M9, and quite sure it was the same with the M8.

redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s

redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?

sheikharfaz said:
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
Click to expand...
Click to collapse
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard

sheikharfaz said:
(bootloader) version-main: 1.58.502.1
Click to expand...
Click to collapse
As suspected, you need to update all the firmware, not just hboot. Your firmware is still on the original 2014 release of Kitkat. This will cause many issues, even if you updated hboot. For instance, you would find WiFi would be broken on just about every current custom ROM around; due to the WiFi firmware partition on the phone being outdated, and not compatible with the current ROMs.
ahmed has the process outlined well. I would recommend to follow his instructions above.

ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?

sheikharfaz said:
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
Click to expand...
Click to collapse
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting

ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
i am not able to unlock my device back
E:\new\android-sdk-windows\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826418688 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.133s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.144s

ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
stuck in bootloop after locking the device
i accidently mistyped fastboot reboot instead of fastboot reboot-bootloader
what shall i do now

xunholyx said:
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
Click to expand...
Click to collapse
stuck in bootloop
what can i do?please help

ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
please send me next steps too.

sheikharfaz said:
stuck in bootloop
what can i do?please help
Click to expand...
Click to collapse
You flashed firmware first?

xunholyx said:
You flashed firmware first?
Click to expand...
Click to collapse
yes,now how do i come out of this bootloop ,there is nothing on screen except that htc logo

Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know

xunholyx said:
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
Click to expand...
Click to collapse
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help

sheikharfaz said:
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
Click to expand...
Click to collapse
request another unlock_code
follow the steps to unlock the bootloader again on the hcdev website http://www.htcdev.com/bootloader/

sheikharfaz said:
can i please get how to unloack bootloader .i have tried fastboot oem unlock please help
Click to expand...
Click to collapse
This command doesn't work on the M8, it's not even worth trying. The whole point of the HTCDev.com bootloader unlock process, is due to the fact that HTC forbids unlocking the bootloader with that command. It only applies to certain devices.
You need to use the bin code command. If it doesn't work, just request a new bin code, like ahmed suggested.

Stuck in bootloader and getvar all empty

Hello everyone,
I've got some trouble with my phone.
The battery was empty I plugged it with the official charger, I heard some crackling. Then it's hard to boot into bootloader, it wo'nt charge.
When I plug it it show the "charging icon" with 0% but without the green progression bar.
I can't relock the bootloader to flash a stock firmware. I'm S-ON.
You can see below my "fastboot getvar all" it's pretty empty so weird :
e_Kit_v1.0\Data>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA66TBNXXXX
all:
Click to expand...
Click to collapse
Anyone can help me ?
Thanks

That's the way the fastboot getvar all info is gonna look if you're in bootloader. It'll show when you're in download mode.

OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.

GaTeRy86 said:
OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.
Click to expand...
Click to collapse
If you're in bootloader mode you should be able to boot to download mode from there. It's the third entry from the top. Just navigate to it with the Vol- and confirm with the power button. If there post the getvar all without IMEI and serial number.
And please elaborate a little bit more which image are you trying to flash? Is the only problem that your device doesn't seem to charge or are there more problems you encounter. Did you previously flash a custom recovery or ROM?
Sent from my htc_pmeuhl using XDA Labs

I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Click to expand...
Click to collapse
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.

OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.

GaTeRy86 said:
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.
Click to expand...
Click to collapse
Try fastboot oem rebootRUU then try flashing the firmware after

xunholyx said:
Try fastboot oem rebootRUU then try flashing the firmware after
Click to expand...
Click to collapse
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging

GaTeRy86 said:
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging
Click to expand...
Click to collapse
Sadly welcome to the club , my phone is s-off with exactly the same issue, it's almost two months as a paperweight
It seems that it is difficult to understand even for the most illustrious of this forum that theres is no way to enter to recovery, download mode, RUU mode or whatever other mode in which you can do something more than flashing img in the broken bootloader.
https://forum.xda-developers.com/htc-10/help/htc-10-brick-usa-mex-wall-t3574704

You can't brick it from S-ON. It's just not possible.

tabp0le said:
You can't brick it from S-ON. It's just not possible.
Click to expand...
Click to collapse
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
GaTeRy86 said:
I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
Quote:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.
Click to expand...
Click to collapse
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972

xunholyx said:
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972
Click to expand...
Click to collapse
Good point! You're absolutely right. I wasn't even thinking about that!