Related
I really don't know what's just happened...I think maybe my TP2 just decided to die on me.
I was using NRGZ Leo ROM from 22nd Feb. All was going well until my battery ran out today. At the time, my daughter was playing a game on it, not from WM, but from the Android port (Haret). While she was playing, I heard the familiar short vibrate of a soft reset. I know my battery was low and I suspect the battery wasn't charging, although it was plugged in (not sure if Android supports charging yet in the later builds)
Anyway, for some reason, it wouldn't go past the vibrate/Touch Pro2 screen. It just kept resetting and looping back. I attempted to do a hardware reset (power button, talk/send, end buttons) but accidently chose the wrong combo (power button, volume down) and entered bootloader. No problem yet, just reset and try again, right? Only I didn't get the chance, as it reset itself and looped through bootloader.
Now I am stuck in this loop. I can't flash from SD as it wont stay on long enough before self-resetting to find the RHODIMG.nbh on the card. I can't connect to my PC as it wont stay in bootloader long enough before self-resetting for my PC to install the "Windows Mobile Device" drivers, and even if it did, when it self-resets, it would disconnect anyway. I can't connect to MTTY for the same reason. I can't connect to ActiveSync or WMDC as I can't boot to WM to get ActiveSync running on the device.
When plugged in to AC power or through USB, it fires itself up automatically and into this loop, and it wont turn off manually, reset or accept any other button combos to enter RUU (from SD method) or to do hard reset. When it is not plugged in to any power source it won't even switch on.
I suspect it is resetting as it is not charging. I'm guessing that when in bootloader, charging is disabled, and I think this because I was originally getting 3 seconds of bootloader, now I am getting around 8 seconds, but it doesn't get any better than that, and I don't know of a rom upgrade method that can be done in 8 seconds! There are a few seconds of charging time before bootloader kicks in and the orange LED goes out and presumably stops charging. Am I right in thinking there is no charging in bootloader and in the Android port (I am using the latest version from 27/2, rhod100).
Basically, to summarise, I am stuck in bootloader-reset-bootloader loop, I cannot connect to pc in any way, flash from SD, Hard Reset, I have very little or no battery and it won't charge because it keeps going into bootloader where there is no charging taking place and it wont turn off to charge that way either.
Any help will be greatly appreciated. I don't hold out much hope though. At the moment, it doesn't seem that I am able to interact with it at all to make it do anything different or to manipulate what it is trying to do. Hopefully someone will see something familiar and maybe have some suggestions.
Oh, and by the way, it's nothing to do with a bad flash. I've been doing this for long enough to know what I'm doing, and I wasn't even doing a rom upgrade at the time. My last rom upgrade was 2 days ago and all went well, and I have been using it without problems since, until now. I haven't flashed my Radio or SPL since HSPL was released, so I know it has nothing to do with that either.
Thanks in advance for anyone who can give any advice at all, or even just take pitty on me! Apologies for all the text. I know it looks boring and may put some people off reading, but I needed to get all the info in.
Are you able to charge when it completely turned off?
can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...
shadixs said:
Are you able to charge when it completely turned off?
Click to expand...
Click to collapse
I can't get it to turn off, power button has no effect.
clauswl said:
can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...
Click to expand...
Click to collapse
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.
matmaneyre said:
I can't get it to turn off, power button has no effect.
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.
Click to expand...
Click to collapse
I had exactly that problem after a bad romflash. I bought a decktop cradle for the tp 2 that has 2nd. battery charger. Charged the battery and reflash, everything was ok again.
So, juice up the battery and do a hard reset or reflash..
SOMETHING LIKE THIS
I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.
Cheers guys. I thought it might be the rom. Not sure how though as like I said, my last rom flash was a couple of days ago and it was fine. Guess these things just happen sometimes. I'll try and get the battery charged somehow. Trouble is, I don't know another single person who has a TP2, so it looks like the cradle option I think. It did cross my mind to be honest when I was trying to think of alternative charging methods.
As for the warranty idea, if it can be avoided, I'd rather not take that route if I can help it, but thanks for the suggestion. Lets just say that will remain an option as my last resort if all else fails.
Still open to suggestions if anyone knows of any miracles....any Hogwarts graduates kicking about these forums with a few magic words to spare?
Hey man, I had the same issue when my phone wouldn't for some unknown reason charge.
1) Take our your battery
2) Plug in your DESKTOP CHARGER (not USB from PC!!) to microUSB slot
3) Put your battery back
4) Wait few moments (5 minutes)
5) and you are ready to boot, now you can even charge from USB. No idea why, but looks like booting takes more than 500mA :O
If it wont help, swap those 2 and 3 points
Hey guys! Please give this thread a better title. More related to the problem. Sounds like it could be useful in the future for hopefully very few people.
OK, I will change the thread title. I searched for quite a while but couldn't find any similar cases. But it seems it is more common than I thought since I raised the issue, so a new, more specific title might be more beneficial to other users experiencing similar problems.
For the record, I haven't solved it yet. Waiting on a standalone battery charger I bought from eBay. Didn't really want the cradle. THIS is the one I have bought. I will update on my progress when it arrives.
Thanks for your help to all who have contributed so far.
Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.
I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
spark001uk said:
I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.
Click to expand...
Click to collapse
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.
fone_fanatic said:
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.
Click to expand...
Click to collapse
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
This might sound a little stupid, but I actually know somebody that said it worked for his iPhone (waste of 3-4 mins if not). Plug in the USB charger from PC. Reboot the PC without disconnecting the phone. Wait 3-4 minutes...
Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
from what i remember, it won't boot without the battery.
fone_fanatic said:
I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
Click to expand...
Click to collapse
I left it looping for hours....no joy I'm afraid. Just gonna have to wait for this charger to arrive I think
Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
fone_fanatic said:
from what i remember, it won't boot without the battery.
Click to expand...
Click to collapse
Definitely doesn't power up plugged in without a battery. Battery needs to be present. Still waiting on this charger though. I'm hoping it's not one of those where it says the item location is Cardiff (UK) when actually it's in Hong Kong and takes 14 years to arrive
soocerclaude said:
Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.
Click to expand...
Click to collapse
I really don't think it's the mini usb port as it charges and tries to connect to pc before bootloader kicks in & it all stops.
Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.
soocerclaude said:
Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.
Click to expand...
Click to collapse
Well when I unplug the ac adapter, mine doesn't last on bootloader for more than a couple of seconds before dying. Doesn't even get to the RHODIMG.nbh update screen that way - not enough charge (I'm still hoping). Tried charging overnight while looping but still wouldn't charge enough. The trouble is that obviously the bootloader is killing the battery as it's not charging very much.
Got my charger finally....but they sent the wrong one. Waiting on a response from the seller. The "dock" on the charger wasn't big enough, so while the connectors were in the right place to charge the battery, the battery didn't sit flush, so they wouldn't reach the points on the battery itself. Hope they have a TP2 one & it's not just them thinking it's compatible, as it's the only one on the whole of ebay UK that has them in stock in the UK. Don't want to have to wait up to 2 weeks for one from HK.
I will keep you posted anyway.
Hi I brought mine 2 get fix because my warrenty got void due 2 water damage. I think it is the usb port that is causing this, saw in other forums the same thing. Will get back the phone on monday & I will update u on the situation.
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
robuser007 said:
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
Click to expand...
Click to collapse
if your phone truly isn't charging the battery you can always hotwire it to the positive and negative wires from a clipped usb cord.
holding the wire to the terminals of the battery for a few minutes can get you running again.
however...
I have found that often if you just unplug the phone,remove the battery from the phone and then discharge the phone (pressing power button) then reinstall battery, you can then plug in the phone to get a charge...
let it charge for 15-20 minutes and then turn it on without the powercord.
resume charging once running.
I'd advise against the hotwiring method, since unless you have a lot of experience in wiring you run a risk of damaging something due to shorting wires, put it this way, I am experienced in electronics assembly, and wouldn't try this unless there was no other way.
However my method is similar to the one mnjm suggests, I have run out of battery once or twice on android, and I pull the battery, replace it, plug in the charger, wait until the light goes out, disconnect charger, pull and reinsert battery again, power on the phone, wait until it starts the second stage of booting, ( bootanimation), then plug in the charger. Usually works fine.
Or try this:
Pull the battery, replace it, plug in the charger, don't wait wait until the light goes out, power on the phone while light is ON.
I have run out of battery many times while testing battery patch an this always worked for me.
My battery meter was acting up lately and I decided to let my phone die. Let it run out of power to correct the battery meter. It was either 100% charged or less then 1% charge.
Now it won't boot. I see the X animation and nothing happens. I just keep watching the animation. The animation keeps resetting. I hate to think that my Android installation corrupted just by letting the battery run dry?
Will it even charge if I plug it in? I wanna try reinstalling Android to get it working again.
**EDIT**
Yep, corrupt installation.
I have no idea why draining the battery would do that, but it did. I reinstalled Android and it booted again.
My phone lost charge overnight the other day and I found plugging in usb power and using the hard reset button made it boot and then it would charge up OK.
Steve
zenity said:
I'd advise against the hotwiring method, .
Click to expand...
Click to collapse
yeah...I was regretting typing that.
obviously if you are not confident in your understanding of what you are doing then AVOID playing with bare wires.
you don't have to fear electricity...
but you do need to respect it.
I know you are confident, just making sure people knew that there were potential dangers, it's not that a cut down usb lead is dangerous as far as shock hazards go, more the remote possibility that a shorted lead could perhaps cause major battery problems, since hotwiring them, while it does charge the battery, provides no short-circuit protection, it is remotely possible, (but unlikely), that this could cause fire hazards.
If I was really desperate I might do this with a zener diode rather than just bare wires.
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Dukenukemx said:
**EDIT**
Yep, corrupt installation.
Click to expand...
Click to collapse
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
robuser007 said:
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
Click to expand...
Click to collapse
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
zenity said:
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Click to expand...
Click to collapse
I know what you mean. When I use my hammer to smash aerosol cans, I'm always careful enough to cover my face with my hand. Can't be too careful.
I kid, I kid.
Dukenukemx said:
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
Click to expand...
Click to collapse
I've seen that the milestone is still locked, no hardspl etc.
robuser007 said:
I've seen that the milestone is still locked, no hardspl etc.
Click to expand...
Click to collapse
Seriously? By the time they unlock it, there will be a new phone to buy.
Meh, besides, I never lose my old phones. They turn into "hand me downs". My sister has my old HTC Wizard right now. If things get really bad, I still have my old Nokia NGage. Yes, I own one of those.
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Stickman89 said:
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Click to expand...
Click to collapse
Sorted it now, note to self and anyone else who has done this.
Usually what occurs is when the phone powers off when the battery has not been calibrated properly it requires you to do a hard reset using the stylus.
Anyway's I did that in the dark and accidentally pushed the stylus into the charger port on the phone and pushed a pin into another so It was short circuiting. Luckily I didn't damage the pins or the phone and was able to straighten it so it wasn't making contact with the other pins.
I'm happy again, its only really a test phone tbh, I have had a HTC Hero for some time now...
Best Regards,
ST1Cl<^^aN
Like most problems, it's due to the kernel. Even if the bugs get sorted out, there's still plenty of room for improvement.
Lets say the following is working 100%.
phone
GPS
3D
power management
wifi
bluetooth
USB
camera
etc
There's always a need for something. Like upgrading 3D to OpenGL ES 2.0, or getting support for ext3/ext4. That's a long way to go and very few people are willing to do it on their spare time.
In the most severe cases, people had to pool together a reward for someone to include support for something.
Considering how similar the Kaiser/Polaris/Vogue is, you could combine this group of people to get something done. There's a lot of talent, but it's spread far apart.
Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
LizardProtection said:
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
Click to expand...
Click to collapse
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
de4life said:
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
Click to expand...
Click to collapse
That seems to be exactly my problem! Thanks!
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!