Weird charging issues - Verizon HTC One (M9)

Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.

magesticschu said:
Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.
Click to expand...
Click to collapse
Sounds like a hardware issue not software. but not sure. just my 02. cents

If running the RUU for 1.33.605.15 doesn't solve your charging issue, my first thought would be hardware.
That said, HTC has definitely been having trouble with charging and battery issues, so we've gotta hope that the final release of 5.1 for us will resolve the problem. The currently leaked 2.6.605.10 is most likely not the version that will be released publicly.

After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)

magesticschu said:
After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)
Click to expand...
Click to collapse
Still doesn't explain off state not charging tho so idk I'll see after a few more days see if it happens again

O had a similar issue, where it would go from charging to not charging every couple of seconds. I have not had these issues with Fluent or Adrenaline. There's a post in the Adrenaline thread about how to calibrate your battery. Try that, also. FWIW, when I installed Viper after being on Fluent, and calibrated the battery, I haven't had any more issues.

I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.

Tom Huot said:
I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.
Click to expand...
Click to collapse
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.

Please tell me how to do this.
sdamark said:
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.
Click to expand...
Click to collapse
What is TWRP?

Tom Huot said:
What is TWRP?
Click to expand...
Click to collapse
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.

Root?
Do you have to root the phone?
sdamark said:
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.
Click to expand...
Click to collapse

Tom Huot said:
Do you have to root the phone?
Click to expand...
Click to collapse
You need to have s-off and bootloader unlocked. Currently the only way to do this on Verizon is with a clip or a java card. There is a post in general about java cards with plenty of information. Currently there is no way to root without TWRP and thus you need s-off and the bootloader unlocked.
Sent from my HTC6535LVW using Tapatalk

Related

[Q] [Problem] Reboots after disconnecting phone from charger/USB

Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!

[Q] Cant get S off

Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
ancora76 said:
Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
Click to expand...
Click to collapse
Sounds like what happend to incubus...
any idea what he did to possibly fix the issue?
ancora76 said:
any idea what he did to possibly fix the issue?
Click to expand...
Click to collapse
Think he is exchanging his phone on insurance policy.
there has to be a way to go back to s off either with an emulator or something i hope...
ancora76 said:
there has to be a way to go back to s off either with an emulator or something i hope...
Click to expand...
Click to collapse
Probably not. If you cant get your SD card to mount, then you probably screwed.
damn, same problem!!
Yeah, i couldnt get s off because sd wouldnt mount to be able to flash anything, nor would ir mount with the pc to able to flash ruu or anything.
Spending $90
Let me know if you figure it out.
Did you guys do/change anything RIGHT before it happened? Just wondering so maybe we can avoid it happening to anyone else.
I did nothing other then do a nan backup...
ancora76 said:
Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
Click to expand...
Click to collapse
I've had this happen twice now, two diff. phones. sucks... I don't know what causes it, but you need to call Verizon and get a refurb. Make sure to pull the rom.zip from the most recent RUU file (from nov.) and rename it to PB31IMG.zip and you will be un-rooted and back to stock w/o repercussions of losing warranty.
also when not connected to power, does it do the vibrate three times then blinking green notification light until battery pull?
ACD168 said:
I've had this happen twice now, two diff. phones. sucks... I don't know what causes it, but you need to call Verizon and get a refurb. Make sure to pull the rom.zip from the most recent RUU file (from nov.) and rename it to PB31IMG.zip and you will be un-rooted and back to stock w/o repercussions of losing warranty.
Click to expand...
Click to collapse
but bootloader isnt reading anthing from sd card so i wouldnt be able to flash that
Thats exactly what happened to me on Sunday. I had to get a new phone. If you notice the adb drivers aren't working, or mine weren't. I was thinking it was just a bad usb port but why would it go back to s-on. Mine did exactly same thing.
nfiniti9 said:
Thats exactly what happened to me on Sunday. I had to get a new phone. If you notice the adb drivers aren't working, or mine weren't. I was thinking it was just a bad usb port but why would it go back to s-on. Mine did exactly same thing.
Click to expand...
Click to collapse
what rom were you using?
Well I was using reengineered and switched to magnolia. I unplugged the usb cable right before hitting reboot after flashing. It never booted up. I went through everything, even flashed back to RUU. When I went in to flash RUU I noticed I was s-on. I hadn't done anything that should do that. I was about to give up (already called verizon) when I plugged in the data cable, I had tried the power cable (i have 1 usb plugged into ac adapter and 1 into computer) but it didnt change anything. Soon as I plugged it into the data cable and powered the phone on, it booted up fine. I did managed to get it to reboot unplugging the usb cable while it was on. Once it just rebooted, once it went to the 5 vibrates/led flash error thing. Once I got it working it would work fine (except for usb/sdcard) until I plugged in the usb cable again. Would charge fine on ac though. I didn't notice the sdcard thing until later when I couldn't set any options in handcent. Somehow I just don't feel its just a bad usb port.
I still have my old phone, going to send it back tomorrow if you want to know anything.
nfiniti9 said:
Well I was using reengineered and switched to magnolia. I unplugged the usb cable right before hitting reboot after flashing. It never booted up. I went through everything, even flashed back to RUU. When I went in to flash RUU I noticed I was s-on. I hadn't done anything that should do that. I was about to give up (already called verizon) when I plugged in the data cable, I had tried the power cable (i have 1 usb plugged into ac adapter and 1 into computer) but it didnt change anything. Soon as I plugged it into the data cable and powered the phone on, it booted up fine. I did managed to get it to reboot unplugging the usb cable while it was on. Once it just rebooted, once it went to the 5 vibrates/led flash error thing. Once I got it working it would work fine (except for usb/sdcard) until I plugged in the usb cable again. Would charge fine on ac though. I didn't notice the sdcard thing until later when I couldn't set any options in handcent. Somehow I just don't feel its just a bad usb port.
I still have my old phone, going to send it back tomorrow if you want to know anything.
Click to expand...
Click to collapse
it's very strange that you have 5 vibrates, I've read everywhere and I seem to be the only one who have had this happen on two diff phones, getting 3 vibrates... it boots to the splash screen then instead of boot animation it vibrates 3 times, blank screen and green flashing notification light only remedy to pull the battery. I found that it would boot up only with usb or wall power, and I was able to take the ROM.zip from the nov. update RUU and rename it to PB31IMG.zip since it's signed and got me back to stock splash, recovery ect. and since I was turned to S-ON ( dunno how). weird.
My situation is the same with the 5 vibrate and then blinking light until i remove the battery. I cant get the phone to start up at all i keep going to recovery.
ACD168 said:
it's very strange that you have 5 vibrates, I've read everywhere and I seem to be the only one who have had this happen on two diff phones, getting 3 vibrates... it boots to the splash screen then instead of boot animation it vibrates 3 times, blank screen and green flashing notification light only remedy to pull the battery. I found that it would boot up only with usb or wall power, and I was able to take the ROM.zip from the nov. update RUU and rename it to PB31IMG.zip since it's signed and got me back to stock splash, recovery ect. and since I was turned to S-ON ( dunno how). weird.
Click to expand...
Click to collapse
ok, i was finally able to get stock android back on. So im getting somewhere at least.
I had to reformat my sd, rename my rom.zip to PB31IMG.zip and put it back on there. And now im at least back to stock. Now i gotta see if i can re root it.
its crazy that after getting the rom and recovery etc... back to stock, it still wants to vibrate 5 times if i unplug usb.
incubus26jc said:
its crazy that after getting the rom and recovery etc... back to stock, it still wants to vibrate 5 times if i unplug usb.
Click to expand...
Click to collapse
Trust me bro I feel your pain I had two phones do this, a blown speaker, one had the green noti light go out, first brand new one had the camera lens pushed in. even with all the problems I love the phone. just get it back to stock like you have, call 1800-922-0204, push 0, push 0, enter your account password and tell the rep whats up. get new phone. if you bought with amoled, thats what youll get. I should know Ive gone through 4 in the past week. I've brought back 2 boxes last week and I have 3 more to bring back tmw, at one point I had three incredibles sitting in my room. I have two batteries to send back too. man I can't wait to upgrade to the Thunderbolt. Every one of these refurbs it's something else. the last one with the green light blown out, that trackpad was PERFECT it hurts to loose that, this one is a little pushed in, but what can you do, not too mention the back door wasn't creaky at ALL, and on this on its sooooo looose. I just can't win. so this one needs cardboard behind the battery and its still not as good a fit as the last refurb... not too mention who knows if the cardboard isn't good?

USB Issues

I was running Leedroid on my Desire and all was fine.
I seen these Sense 2.1+3.0 ROMS and decided to give one a go.
I tried to get into recovery before doing anything to take a NAND Backup, but it just refused to go into recovery. I finally got it in there and tried to apply to update.zip but it kept saying something could not be found, I forgot what, and failed after 10 tries.
I booted mu phone up and I'd lost all my data. It's like the phone had been wiped.
I tried reseating the SD Card and checking it was all ok, but then I got stuck in a bootloop. In the mean time, my Alienware Laptop decided to die, followed by my backup Dell laptop! lol
I messed around for ages trying to get various things to work, but couldn't do it. In the end, I downloaded the old root method and flashed Cyanomod 7 which seemed to work and I got it booted, but I couldn't mount the SD card and it would rarely pick up that the USB was connected.
I then flashed AceSMod007 which also seemed to go well minus 2 things.
The first, Text messages seem to show my contacts picture, but also it only shows their Number rather than the contact name. This is VERY annoying and I can't find a way to resolve it.
The second issue, and possibly the most worrying is that it won't pick up USB connection AT ALL. This includes when it's plugged into the Wall to charge.
I tried the USB Brick fix, but that didn't work at all.
I shutdown the phone, removed the battery, plugged in the charger, inserted the battery and booted up the phone and it started charging, but as soon as I unplugged the charger and put it in again, same problem.
I'm currently trying another ROM to see if that resolves the issue, but I suspect that it won't tbh.
Has anyone came across this before and/or knows how to fix it?
Other things I've tried:
Wiping all data, cache and Battery data.
Using different USB cables
Thanks
UPDATE:
Flashing a different ROM didn't seem to resolve it.
Quick update.
I flashed Insertcoin rom onto the phone and it's resolved my text message issue.
Also, when I plugged the phone into the PC, it didn't give me any options for mount SD or anything like that, but said it was charging. However, an hour later and the battery had only gone down.
Since charging by USB has always been slow for me, I plugged in into the wall socket for an hour but it wouldn't pick up that I'd plugged it in. I turned the phone off and I got the LED to say it's charging.
Left it, then booted it up and still has the same battery level.
I don't expect it's the battery otherwise it would pick up fine when plugging into the PC.
Could be an usb brick:
http://forum.xda-developers.com/showthread.php?t=691639
Cheers mate, but as I mentioned, I've tried the USB Brick fix a couple of times and still experiencing the same issues.
Can you switch on blue tooth? Does it stay on?
Sent from my HTC Desire using XDA Premium App
Actually, no. Its says Turning On... Then just goes back to off.
you DO have USB-Brick
you gotta fix it
if S-OFF do:
fastboot oem enable qxdm 0
fastboot oem eraseconfig
if S-ON there are a few threads on xda on how-to do it, if you still get no USB-connectivity you just didnt do it right
good luck
Ah, I did try it a few times. I'll just keep trying then.
Cheers
Are you S-Off or S-On and are you still ROOTED?
This thread for USB Brick
See for my post here
if you are S-off or tried to flash a RUU and lost ROOT!
This thread has a flasher with built in USB Brick fix
I'd already followed the USB Brick guide and it didn't help.
Now, is I were to have missed the step that says to run '/data/flash_image misc /data/mtd0.img', I'd be a bit of a tit.
So let's just say that I tried the guide again and now I have full USB functionality back
I was going to S-OFF my phone, but I'll hopefully get a Sensation soon and I don't want to fubar anything in the mean time.
Thanks for the help and pointers though guys. It's nice to be a member of some forums that aren't full of people who want to cry at you for not understanding everything 100%.
Cheers again
just use the thanks button
glad we (or at least I) could help.

[Q] Phone won't power on. Bricked?

Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!

[Q] Hard Bricked One X?

Right i know ive posted before but i have had a lot more since i posted last and now im in another different situation
About a week ago i was running Hboot 1.28 along with ARHD 12.1(i think)
Randomly during the day changed my gmail account to a different email that went fine
Next i ended up having some random SuperUser commands asking me to do random things that had never seen before so i denied them and my phone was running as normally
Few hours later all my apps started crashing starting with process.com.gapps.process i think? and then everything else crashed
So i thought ahh its just my rom messing about so i wiped and then re-flashed (yes i installed the boot, and wiped properly and didnt install any tweeks) and as it booted up everything crashed and it reboots and bootloops
So i tried a few different roms to see if it would work and i got the same problem on EVERY rom i tired including ARHD MAXIMUS
So i posted on here and was told to reflash hboot up to the latest which i did at the time it was 1.31 and i still had the same problem even when i flashed the recovery boot image and new roms ect
I messaged football on twitter to find out when the latest RUU would be released and waited a few days to flash the latest RUU WWE for JB which was for my CID which is HTC_001 so i flashed that and everything went completely fine so i let my phone boot up and then the same problem happened
I then unlocked it again and left phone charging in recovery over night like i normally do
and now my phone is hard bricked im pretty sure i cant even turn it on?
any ideas?
Ok, so you can't turn it on? That's seems somewhat more important than changing your email account.
So you last had it in recovery (which one? CWM 5.8.4.0?) and it was charging? Then, some time later it was dead, right?
So when you plug it into a usb charger (give it 5 minutes) does the charging light come on? And what about a USB port?
BenPope said:
Ok, so you can't turn it on? That's seems somewhat more important than changing your email account.
So you last had it in recovery (which one? CWM 5.8.4.0?) and it was charging? Then, some time later it was dead, right?
So when you plug it into a usb charger (give it 5 minutes) does the charging light come on? And what about a USB port?
Click to expand...
Click to collapse
Aha, i cant turn it on as of today i changed my email account about a week ago
i had the latest CWM yes 5.8.4.0 and yes it was, and last night it is now dead and wont even turn on
I have tried wall charger i get nothing havent tried USB when i get back home in a couple hours ill give it another go and use the USB
Seems like a hardware fault, you can't hard brick an s on device
Sent from my HTC One X using xda premium
Stuar said:
when i get back home in a couple hours ill give it another go and use the USB
Click to expand...
Click to collapse
Can you hear input sound in windows when you plug it in? Does anything show up in device manager?
TToivanen said:
Can you hear input sound in windows when you plug it in? Does anything show up in device manager?
Click to expand...
Click to collapse
Right ive finally plugged it into my laptop and now i got the red light charging, i can now get into fastboot
Stuar said:
Right ive finally plugged it into my laptop and now i got the red light charging, i can now get into fastboot
Click to expand...
Click to collapse
Since you are already unlocked, try to install some ROM.
There has to be something wrong since the problem persists on every ROM.
You sure you wiped everything you can? SD-card also?
TToivanen said:
Since you are already unlocked, try to install some ROM.
There has to be something wrong since the problem persists on every ROM.
You sure you wiped everything you can? SD-card also?
Click to expand...
Click to collapse
I haven't done the SD card, so ill give that a try, so wipe SD card first then put rom ect back on the sd card, then preform full wipe
also wipe using computer or recovery?
Flash the boot.img. enter recovery, perform a full wipe there, install the rom.zip

Categories

Resources