Develop Bugs

Wildfire Wipe Battery Stats

Hello,
I have a Wildfire on stock Rom, it won't charge above 3%.
As I've read in the forum it would help to wipe the battery stats.
I have a new 100% charged battery but with the new one there is still the same problem.
As far as I know with clockworkmod it is possible to wipe battery stats - but is there an option to make this with the stock rom?
HTC unlocker and scripts from the forum stop the process of rooting the phone because the battery says it's lower than 30% charged - what is definitly wrong.
Anyone with further advice?
Thx

zeroone said:
Hello,
I have a Wildfire on stock Rom, it won't charge above 3%.
As I've read in the forum it would help to wipe the battery stats.
I have a new 100% charged battery but with the new one there is still the same problem.
As far as I know with clockworkmod it is possible to wipe battery stats - but is there an option to make this with the stock rom?
HTC unlocker and scripts from the forum stop the process of rooting the phone because the battery says it's lower than 30% charged - what is definitly wrong.
Anyone with further advice?
Thx
Click to expand...
Click to collapse
Ouch, sorry to say pal but wiping the battery stats isn't going to help. The battery stats doesn't actually reflect the current condition of your battery at all, it only reflects what has been draining it. What it "might" be is the phones Information about the battery is corrupt, and as such it thinks you have far less than you actually do. For example say your battery holds 24volts and the android system is expecting you to have 240volts, then the maximum fully charged your battery can be is only going to show as 10% battery life. So your battery may well be fine (especially since it's new ) but the systems info maybe corrupted. Have you done any android modding before?
Do you know if your phone is s-on or not?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

no - that would have been my first modding.
s-on, iirc I need s-off for rooting and it's the opposite ;-P
the interesting part is that the system says only 3% are left but if i go into the recovery mode (vol-down + power btn) there is no red led indicating low battery and if i put it on my table it stays on until i turn it off (never tried out a time span - but while reading some threads in the forum it was turned on for more than 10 min. with display light on). But if itry to charge the battery with that phone the red led will never turn off.

zeroone said:
no - that would have been my first modding.
s-on, iirc I need s-off for rooting and it's the opposite ;-P
the interesting part is that the system says only 3% are left but if i go into the recovery mode (vol-down + power btn) there is no red led indicating low battery and if i put it on my table it stays on until i turn it off (never tried out a time span - but while reading some threads in the forum it was turned on for more than 10 min. with display light on). But if itry to charge the battery with that phone the red led will never turn off.
Click to expand...
Click to collapse
Okey dokey can you tell me your hboot version please? Also is your phone branded to a cell carrier, ie o2 virizion vodaphone etc?
All going well we will be able to use a RUU on your phone, which will reflash the software and hopefully fix your issue
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

actually i'm not at home but it's version 2 of hboot so should be 1.01.0002, cell carrier is A1 Telekom Austria - i guess it's an adopted version from the vodafone rom, but i'm not sure. Can I see anywhere what kind of branded version I've got?
And also: Thank you very much!

zeroone said:
actually i'm not at home but it's version 2 of hboot so should be 1.01.0002, cell carrier is A1 Telekom Austria - i guess it's an adopted version from the vodafone rom, but i'm not sure. Can I see anywhere what kind of branded version I've got?
And also: Thank you very much!
Click to expand...
Click to collapse
If you can have a look around xda/Google about setting up an adb and fastboot folder for windows(assuming that's what your PC is running,if not change accordingly ) and look at the command fastboot getvar all. If you issue this to the phone while it is connected to the PC via usb in hboot/fastboot mode (boot into hboot with volume down and power, then use power to select fastboot) it will output a whole range of information. If you can tell me the cid it will make finding a compatible ruu much easier
If you want to look at ruus Google for a website called shipped roms, the wildfire will be under android and its codename, which is buzz. Happy hunting
Sent from my Nexus 7 using Tapatalk 4

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0002
(bootloader) version-baseband: 3.35.20.10
(bootloader) version-cpld: None
(bootloader) version-microp: 0622
(bootloader) version-main: 2.31.163.1
(bootloader) product: buzz
(bootloader) platform: HBOOT-7225
(bootloader) modelid: PC4910000
(bootloader) cidnum: VODAP120
(bootloader) battery-status: low
(bootloader) battery-voltage: 3480mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ab9ba933
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i guess these are the things you need to know right?

zeroone said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0002
(bootloader) version-baseband: 3.35.20.10
(bootloader) version-cpld: None
(bootloader) version-microp: 0622
(bootloader) version-main: 2.31.163.1
(bootloader) product: buzz
(bootloader) platform: HBOOT-7225
(bootloader) modelid: PC4910000
(bootloader) cidnum: VODAP120
(bootloader) battery-status: low
(bootloader) battery-voltage: 3480mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ab9ba933
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i guess these are the things you need to know right?
Click to expand...
Click to collapse
Perfect looks like your on an edited vodaphone Rom. When I get out of work later on I will have a look for an RUU for you
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

thx in advance

zeroone said:
thx in advance
Click to expand...
Click to collapse
ok pal, heres the plan
download this and rename it to update.zip (make sure its not update.zip.zip ) and place it onto the root of your sd card. ( the root means not within any folders or anything). using volume down and power boot into hboot again, once its finished its scan use the volume down button to move onto recovery and select it with power. you should be taken to a screen with a phone and a red exclamation mark. mash the buttons on the phone until options appear on the screen. im not sure what the combination is to make it come up so just experiment once you have the options up select install update from sdcard, and select your update.zip this will flash a bootloader and radio and all the other components hopefully this will fix your issue pal

hmm... i guess that was the wrong ruu, it stops with error code 7 - a quick search told me the ruu is not for the phone. but it's possible to make it install on any device. I'm just afraid this will brick it - or lock it to a german provider or anything else making it useless for me (unfortunately not better than the situation now).

[Q] Stuck in fastboot and no connections in ADB

Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi

ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.

riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?

Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app

elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?

PLS can anyone help me ? :crying:

themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?

FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.

FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..

Out of options, phone fails to work.

Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?

boomboxie said:
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
Click to expand...
Click to collapse
UPDATE: Seems like it`s mostly happening when installing new apps, or recovering them. Tried to remove sdcard , did`t help.

boomboxie said:
H
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
Click to expand...
Click to collapse
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).

redpoint73 said:
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
Click to expand...
Click to collapse
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Will try to convert to stock GPE with RUU and update on results.

boomboxie said:
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Click to expand...
Click to collapse
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
boomboxie said:
Will try to convert to stock GPE with RUU and update on results.
Click to expand...
Click to collapse
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.

To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery

redpoint73 said:
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
Click to expand...
Click to collapse
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.

boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
Click to expand...
Click to collapse
Be careful with your terminology there, to avoid confusion. From your previous post, you stated you just flashed a GPE ROM.
This isn't the same as "converting" to GPE with RUU, which puts you on GPE firmware, GPE partitioning, etc.
boomboxie said:
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
I don't know what that means, if you don't give details on what you did, and the specific results. But I'm assuming you know how to use command prompt to issue adb/fastboot commands, entered the command, and get no response (or device offline)?
If so, check that you are in bootloader-fastboot mode, have HTC drivers installed, or try different cable or USB port.
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
bombo_b said:
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
Click to expand...
Click to collapse
I tend to agree that its a hardware problem. But its always a good idea to return to full stock by RUU, to eliminate the possibility its a software issue, before concluding its a hardware problem.

boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
1) at first go to bootloader
2) connect device via usb cable into pc
3) confirm you are in fastboot mode
4) install drivers through htc sync manager
5) download the following zip
6) at first create a new folder in desktop. then copy zip into that folder & extract.
7) while press ''shift'' right clik on the new folder & select ''open command window here''
8) on the command prompt type fastboot getvar all

I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s

Disregard this post.Sorry

boomboxie said:
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.

umesh.lk said:
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
Click to expand...
Click to collapse
What would be the best way to do that ?

boomboxie said:
What would be the best way to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
boomboxie said:
I have newest TWRP installed.
Yes firmware is up to date.
Click to expand...
Click to collapse
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.

redpoint73 said:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
Click to expand...
Click to collapse
Thanks, will update on outcome.
EDIT: I thought i was "up to date" i guess i wasn`t lol, my bad.

UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failure.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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.049s
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/

boomboxie said:
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failur
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
Click to expand...
Click to collapse
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.

umesh.lk said:
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
Click to expand...
Click to collapse
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4

boomboxie said:
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
Click to expand...
Click to collapse
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.

umesh.lk said:
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
Click to expand...
Click to collapse
By that you mean: Connecting phone to PC and flashing Newer recovery or OS ?

Help me find corrent RUU for my HTC one X

Mine was stucked in boot loop after flashing incorrect ROM (i think)
Right now it can boot into recovery but cannot find any ROM that would install. After searching I think the solution would be flashing the RUU(i think also) but I couldn't find the correct one, here are my details
EVITA PVT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jul 11 2012,14:36:28
*********
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT29VW306913
(bootloader) imei: 359691048837242
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I believe everything was already deleted and no backup.
Please help me fix my HTC.
Thanks in advance.

Your phone is not an HTC One X International. The first line shows EVITA PVT SHP S-ON RL
This HTC One XL or One X (North America)
Do you know which model you have?

If your One x Evita is a AT&T branded phone. Try this RUU.
dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Source: http://www.htc.com/us/support/htc-one-x-att/news/
If it does not work, browse and try any of the RUU here.
http://androidruu.com/?developer=Evita

SÜPERUSER said:
If your One x Evita is a AT&T branded phone. Try this RUU.
Source:
If it does not work, browse and try any of the RUU here.
Click to expand...
Click to collapse
Hi, thank you for your reply, yes I have an AT&T, hopely this works, its been weeks that my phone is not working, BTW what will be the correct process to install this RUU? Do I need to relock my HTC? or just rebootRUU?
Another info that I like to share , "fastboot get version-main" & "adb devices" doesn't display any information, only in "getvar All' where I got some information
modelid: PJ8310000 - This is what I have when I execute fastboot getvar All

Oh my, what happened?
It was in the middle of installing RUU when i thought it will finally repaired.. It shuts down & no longer charging? I tried to wait by keeping it plugged but still no led light, but everytime i plug & unplug it could here that my computer is detecting it?
What happened?

daxjeremy said:
Oh my, what happened?
It was in the middle of installing RUU when i thought it will finally repaired.. It shuts down & no longer charging? I tried to wait by keeping it plugged but still no led light, but everytime i plug & unplug it could here that my computer is detecting it?
What happened?
Click to expand...
Click to collapse
It is recommended that you do "fastboot oem relock" before running the ruu.
Did you make sure that the phone had 100% charge BEFORE you ran the ruu file?
If the phone died...its bricked
Can you boot the phone to Hboot?

SÜPERUSER said:
It is recommended that you do "fastboot oem relock" before running the ruu.
Did you make sure that the phone had 100% charge BEFORE you ran the ruu file?
If the phone died...its bricked
Can you boot the phone to Hboot?
Click to expand...
Click to collapse
Oh my, I don't know its battery capacity before I run the RUU
Yes I had the fastboot oem relocked before RUU
But now, I cannot boot the phone, its not even have led light

Hi, is my phone will be just a paperweight? or there's still hope to unbrick my HTC? Please help.

daxjeremy said:
Hi, is my phone will be just a paperweight? or there's still hope to unbrick my HTC? Please help.
Click to expand...
Click to collapse
Your device is dead. You can unbrick it if you have access to a Riff Jtag tool. This tool cost £191.66 (ex. VAT) to buy new.
http://www.fonefunshop.co.uk/Unlocking/riff_box.htm
You can either solder you own cables to the pinout or buy this ready-made adapter for the PJ8310000
http://multi-com.eu/,details,id_pr,14355,key,jtag-for-htc-one-xl-x-att-pj83120-pj83100.html
http://www.pak-gsm.com/attachments/...3100-repair-boot-sn-cid-htc_one-x-pj83100.jpg
http://www.riffbox.org/jtag-news/riff-jtag-htc-att-unbrick-imei-supercid-repair-supported/
http://www.brickedmyphone.com/hard-bricked-htc-one-x-att-evita-repaired-with-jtag/
https://www.youtube.com/watch?v=4X14NkD9J_o
*Send an email to this guy. He might be able to help you.
http://www.brickedmyphone.com/products/jtag-unbrick-service/

Well, I guess its time to say goodbye to my HTC.
Thanks everyone.

M out after going back to stock Rom

Hello guys,
I have a big probleme. I decided to change mobile, i put my as original since it's easy to sell. I was on leedroid rom with twrp on custom recovery.
So on twrp i flash my original Rom (i ever done it one time so i know it's the good one). Everithing work great, the phone restart. I want to improve the Rom step by step, and i download kitkat 4.4.4, when it's done the phone restart, load kitkat and restart. That the begenning of probleme, it reboot i here the small song, then i stay lock one start screen (Htc-Powered by android), very strange, the screen give some vibration as if it work but nothing move, locking on this screen ........ No probleme, i restart on recovery and i start on recovery factory, the phone boot, as if it load the recovery factory version, it boot again, but nothing more, locked on white screen with Htc powered by android, and the small thong.
Here's, i don't have phone since 2 days. If you have a solution to restart this M8, please help me.
Thanks in advance for your answer.

Most probably because of a very low android version installed on a high firmware version.
Post fastboot getvar all result (without serial & imei no.) to see what actually that you need.

Thanks for you answer, how can i get fastboot getvard ?

Never expect this kind of question from a "member" of XDA.
Anyway ... connect your device to pc after you put it on bootloader/fastboot mode
Open a command prompt from your adb/fastboot folder then type
fastboot getvar all

Sorry, i have done that long time ago.
So, here is
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.163.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP203
(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

That's your problem .. you have Marshmallow 6.12.163.4 firmware but you restored a very old version and it get stuck due to too high firmware.
I don't see anywhere a backup or RUU for 6.12.163.4 around ... you need to find it.
I'll see whether I can find a lower version than make a good collection in my backup thread
Edit : you should have already make your own backup since our last conversation here : http://forum.xda-developers.com/showpost.php?p=57254494&postcount=3175 .... maybe you can contact him again.
Edit 2 : You can wait and I'll upload 6.12.163.4 backup to my backup thread (link in my signature) either tomorrow or Sunday

Arf, ok, so i will try to find this one. I hope i will get it.
I'm just asking, how can i flash this version (if i find it), since i can't access to my phone, i never do this before ?

I found this for you ....
ROM 4.19.163.2 (+ radio & stock recovery, màd par Migascalp, flash via TWRP*)
Install TWRP then install it as same as you install custom ROM then do OTA to 6.12.163.4
Source : https://monhtcone.com/2015/03/05/boite-a-outils-pour-le-htc-one-m8/comment-page-1/
Thanks to @migascalp

Thanks a lot
The problem is that before i use Twrp to flash my custom rom, and now i only have the original recovery

Aguyos said:
....before i use Twrp to flash my custom rom, and now i only have the original recovery
Click to expand...
Click to collapse
Reinstall TWRP - https://dl.twrp.me/m8/
Download twrp-3.0.2-0-m8.img and place it in your adb/fastboot folder
connect your device to pc after you put it on bootloader/fastboot mode
Open a command prompt from your adb/fastboot folder then type
fastboot flash recovery twrp-3.0.2-0-m8.img
then you get TWRP recovery installed then proceed the rest
gotta go now ... good luck

Thanks a lot Kuala for your help. I download everythings then i do it. I give you news when it's done.
Thanks again mate

Thanks a lot mate for your help.
TWRP installed
15 minutes to go for Rom ....

Working great Kuala. Amazing, thanks for advices and help

Arf, it's not working perfectly, i can't install 6.0. It's loading, decompress, but when M8 reboot to install it make error.....
Does some one have idea ?
Thanks for answer.

Why error ? Did you root it ? If you root it, you'll get error.
Here is another way for you :
Install latest TWRP
Restore 6.12.163.4 non-rooted backup
Install 6.12.163.4 stock recovery
Done
All files needed and how-to, read my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Any further question, ask in my thread