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).
Related
Dear XDA-Member!
I have a HTC Desire with this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.93.0001
(bootloader) version-baseband: 5.11.05.27
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 2.29.405.14
(bootloader) serialno: HT063PL02868
(bootloader) imei: 3578410370xxxxx
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-365c78d6
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
Click to expand...
Click to collapse
PHONE IS HTC__102 GERMANY
- I try to RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe <- radio ver2 failed
- I have'nt gold card no usb debugging ON ROM not booting
- Rom not booting but flashboot have
What can i do more? How to find I a working rom for this phone? I would like to root and S-OFF.
Try this RUU: http://d-h.st/d44
Use this guide to flash it.
The fact that radio failed, may indicate a radio brick. This is the worst type of brick and there isnt really a known way to recover, other than to keep trying RUU's until one successfully flashes (very low chance). Good luck.
Chromium_ said:
Try this RUU: http://d-h.st/d44
Use this guide to flash it.
The fact that radio failed, may indicate a radio brick. This is the worst type of brick and there isnt really a known way to recover, other than to keep trying RUU's until one successfully flashes (very low chance). Good luck.
Click to expand...
Click to collapse
1. I downloaded and copied to sd card root.
2. Put the card in the phone and starting volume- + power
3. nothing happend: HTC Logo with four corner exclamation icon
Phone is RUU mode???
UPDATE:
1. with this RUU working: http://shipped-roms.com/download.php?&model=Desire&file=RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00.32U_5.11.05.27_release_224699_signed.exe&send_file=yes
But not booting, stop on white screen with HTC LOGO
That was is the original state
UPADTE2:
I'm installing your ROM - failed-PU
UPDATE3:
I try to reinstall RUU ROM, but not working: bootloader - bypass, radio ver2 - failed-PU
UPDATE4:
I installed RUU HTC Desire 2.3 Upgrade.exe from HTCDEV.
Phone not started, stopped HTC logo with white screen, then 1-2 minuten restarting, one more vibrating on start.
HBOOT upgraded to 1.02.0001!!!!! Radio is 5.17.05.23
End of this things. After the freezing, working the phone. Probelem is the motherboard or hardware issue.
Thank you for your help. I going to my Friend he is a hardware specialist.
tomatos said:
End of this things. After the freezing, working the phone. Probelem is the motherboard or hardware issue.
Thank you for your help. I going to my Friend he is a hardware specialist.
Click to expand...
Click to collapse
Well, actually it's a radio brick. A critical component of the software is corrupt, and this can hardly be overcome.
But yeah, changing the motherboard will solve the issue.
abaaaabbbb63 said:
Well, actually it's a radio brick. A critical component of the software is corrupt, and this can hardly be overcome.
But yeah, changing the motherboard will solve the issue.
Click to expand...
Click to collapse
Morning can make I the Gold Card After Freezing (2-3 minute) then working ~ 10 minute. Now working this phone with HTC Desire 2.3.3 RUU Rom.
Have you solution, which components on motherboard is wrong? I wan't change complete motherboard just the wrong hardware component.
Thank you for your help. I push the THANKS button
tomatos said:
Morning can make I the Gold Card After Freezing (2-3 minute) then working ~ 10 minute. Now working this phone with HTC Desire 2.3.3 RUU Rom.
Have you solution, which components on motherboard is wrong? I wan't change complete motherboard just the wrong hardware component.
Thank you for your help. I push the THANKS button
Click to expand...
Click to collapse
Well, I don't really know where the radio is stored, but changing the internal memory chip could probably solve the problem. (I AM NOT SURE AT ALL)
I don't think you can find a separate memory chip, and easily replace it. You can barely find motherboards, so I would recommend either replacing the whole motherboard, or buying a new phone.
Hi guys,
So I got a htc one from a friend to fix the onex. The rom is stuck on the 2nd bootanimation (no loop just freezes).
So I thought let me update the firmware because he flashed ARHD 31 wich is JB 4.2.2 and he has hboot 0.95.
But now comes the weird part.. when i got into fastboot and i plug it in my pc there is no usb popup sound? neither it says "Fastboot USB".
It just hangs there at fastboot... I tried it on my moms laptop and it said Fastboot USB for 1 sec then it went to install the fastboot drivers but then suddenly windows says: device unplugged...
So I can get into recovery but ADB doesn't recognize it. USB mass storage in CWM doesnt work either (LMSunifile error or something wich means that I need to update CWM but I CANT since I cant transfer anything now).
Anyone has an idea???
I'm good at hacking/rooting but this is a problem I've never seen before...
If it's hardware failure there is not much you can do !
Try to reinstall all pc drivers from scratch and setup fastboot again ?!
Guess what. it is working in fastboot usb now.. it was my cable. tried another 1 and it suddenly worked! solved
Lol :thumbup:
but now the next problem.. I try to flash newest JB firmware.. but it gives me this error: FAILED (remote: 42 custom id check fail)
Now I did fastboot getvar all and this is the result.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.
(bootloader) version-baseband: 5.1204.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT24VW118369
(bootloader) imei: 353043051993171
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3739mV
(bootloader) devpower: 18
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
IT DOESN'T EVEN HAVE A CID ???? The bootloader is relocked and the device is S-OFF so I cannot write CID.. what can I do now ??
What firmware did you try to flash ?
3.14.980.27. I will try 4.18.401.2 now and report back..
Yeah keep it to 401 firmwares as that's the original main as the command showed......
**** man... I cant flash it because the batery is too low... I let it in the charger the whole day.. tried to charge it in fastboot RUU mode and in fastboot mode.
Also tried some script someone suggested here in the oneX section.. any idea how I charge the freakin battery and FLASH something ??
Yeah charging in fastboot mode doesn't work. Try turning it off via fastboot menu, or charge via the battery charge script !
I am charging it now via battery script. reached 3708mV now but I still cannot flash the firmware... still gives the error 13 low battery..
Anyway thanks for your replies
Well then you are almost there ! Let it go up between 3800 and 3900 then it's best to unlock the bootloader and flash philz touch recovery and charge the battery to 100% in there and then continue with upgrading the bootloader
bro, thanks for your advice unlocked bootloader and flashed that recovery. IT can FINALLY charge with the phone off So Now ima let it charge and then flash the new fw.
Thanks alot bro
EDIT: will the LED turn on if you plug in the charger in recovery? cause It's not red..
Yeah that's a small glitch, if you want the led on just keep it on the charger and "reboot recovery" then it will turn on
thanks bro I see that the % are goin up wich is awesome^^ have a nice day!!
EDIT: I see that you're dutch as well heel erg bedankt, zal mn maatje me weer dankbaar voor zijn hehe
Haha good luck......any questions , PM me in dutch
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 ?
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.
Hi, I'll keep this short and simple. The phone is locked, with S-ON and everything is stock, it's running Lollipop 5.0 with stock sense. I've had my M8 since Oct 2014, served me well until Dec 2017 when I switched to the HTC 10. At any rate, I've migrated the majority of my content to the new phone except for a few like telegram secret chat etc. Since I made the switch, I usually keep the M8 switched off and I used it like 4-5 times only since December. My last usage was around early March.
Anyway, come last week. I turned it on and it got stuck on the HTC logo (first time ever). So I booted into recovery which is when I noticed that the software status is now modified vs Official despite never tampering with it. I cleared the cache and attempted a reboot and it got stuck on the "HTC One" logo but that' about it. The only way out of this state is power button + vol up which reboots it again and on and on this goes. It just refuses to go past that stage. Occassionally "android is optimising apps" appears for like 2 sec before the htc One logo shows up again and remains there indefinitely.
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
(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) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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
So just an update, it seems that right now, my device goes straight into fastboot regardless if I choose power down (powering it on again boots it back into fastboot) or restart it (again goes into fastboot).
hemingway60 said:
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
Click to expand...
Click to collapse
Probably unlikely to get the phone working and keep your data.
It appears your OS has become corrupted or damaged in some way (it happens). This would explain why it goes straight to bootloader instead of booting to OS. It may also explain why it says software "modified" when you haven't done any mods. Although I haven't seen that happen specifically (showing "modified" due to OS damage on an otherwise stock device); but it does seem logical it would say this (it is possibly reading the damage as some unknown "modification").
Your best bet is to restore factory image using RUU, following the instructions on the following post: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe all data on the phone. But in the current condition (as mentioned), I don't think you have much choice anyway.
The RUU should restore the OS, in addition to updating it to Marshmallow (the last version HTC released for this device).
Hey, appreciate the reply. That's disappointing, considering the phone was literally just sitting inside a desk. Anyway, I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Thanks.
hemingway60 said:
I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Click to expand...
Click to collapse
Both are build number 6.12.401.4.
So I doubt there is any actual difference. If there was any change, it would have a different build number (6.12.401.5 or whatever).