Hello. I have a very big problem. My Pocket PC, a Fujitsu Siemens Pocket Loox N520 has been bricked. It occured this way:
I purchased a new battery (quality one, for FS). I started it, it went fine, I connected it to my PC and borh linux and windows had seen it as device. Then, after a few hours I wanted to hard reset it. Tried 10 times, no succes and now, when I try to start it it get's stuck at the image with the climbing people, no booting, no usb recharging. I really don't know what to do and I need your help/advice.
I tried the following. Hard reset, soft reset, battery replace/removal, linux won\t see it with lsusb command, tried to reburn rom but it's not found as device.
Thank You!
pockloox2009 said:
Hello. I have a very big problem. My Pocket PC, a Fujitsu Siemens Pocket Loox N520 has been bricked. It occured this way:
I purchased a new battery (quality one, for FS). I started it, it went fine, I connected it to my PC and borh linux and windows had seen it as device. Then, after a few hours I wanted to hard reset it. Tried 10 times, no succes and now, when I try to start it it get's stuck at the image with the climbing people, no booting, no usb recharging. I really don't know what to do and I need your help/advice.
I tried the following. Hard reset, soft reset, battery replace/removal, linux won\t see it with lsusb command, tried to reburn rom but it's not found as device.
Thank You!
Click to expand...
Click to collapse
These Looxes (I have N560 with extended battery) sometimes get stuck if the battery voltage is too low, i.e they are nearly out of juice. If you have the original battery, have you tried running it from that? Whichever battery you use, make sure it is fully charged. It could be that the new battery had not had a full first charge? It may even appear to be charging but has not fully held its charge and has been running down. I have had bad experiences with Cameron-Sino batteries, which appear to be working but in fact are not holding their charge.
I am clutching at straws but it is worth a try? These are pretty rugged devices. I would not give up hope yet.
Exactly Sir! The battery was not fully charged when the problem occured. I will try what you said and post the feedback. I also hope is not dead, yet.
Thank you and if you have other suggestions I would be glad to hear them.
pockloox2009 said:
Exactly Sir! The battery was not fully charged when the problem occured. I will try what you said and post the feedback. I also hope is not dead, yet.
Thank you and if you have other suggestions I would be glad to hear them.
Click to expand...
Click to collapse
No other suggestions. You should charge it on the cradle though and not be tempted to try to turn it on at all until it has had a few hours of juice/charging. It should not make any difference but to be sure use the cradle and not a USB socket in the lead. The mains charger has a greater output capacity than USB supplies and it is likely to give a better charge rate. Be warned, the N520 may not show any signs of life at all while you are doing this long charge. I would leave it over night and try again to hard reset it, or indeed even use it, next morning. Most new batteries, even LiIon ones, need a longer fist charge and it is not recommended that you use them until they have received their first over-long charge.
I tried a full recharge on my pda, over night but no success. Still, when I power it on, it doesn-t boot. I don.t know what else to do.
I think i should rewrite the ROM. Can anyone help me with that?
Please...
Ummmm it does sound like you may have a hardware problem?
The following site has in the download section the Fujitsu Seimens ROM burning program.
http://translate.google.co.uk/trans...snum=1&ct=result&prev=/search?q=newplow&hl=en
Someone could point you to the ROM image for your N520? Newplow's site has software which can switch devices in the FSC range but I cannot remember if the 520 is catered for?
I wonder if it is stuck on the climbers boot screen whether the burning progrram will work either, as you have to use a PC which can communicate via USB with the device, even if only as a "guest"?
Have you also tried ensuring the device is completely powered down by removing the fully charged battery for say an hour then re-inserting and trying again to start? Are you sure the battery is fully charged - have you measured the voltages on the battery pins with a voltmeter?
Ok. I can't even burn the ROM, the device is not recognized on both linux or windows. Nothing. Anyone knows if its possible to repair it or it is forever briked and I can throw it away? Or maybe keep the parts? GPS receiver ?
Please respond. Thanks!
Just had the same problem today. I was flashing my N500 from WM6 to WM5 and the god damn setup crashed. Now I can only see the climbers and thats it. No hard reset or boot screen combinations work
Something spooky going on here!????? Two crashed Looxes...
I repeat, if all hard and soft resets have failed, the only remaining test is to completely remove the battery and any power source for a long period of time, just in case some residual charge lingers in the electronics/chips. I would suggest several hours, perhaps overnight. Then care fully re-insert the battery and try again. If this fails, I am afraid your device is well and truly bricked.
The only other little trick is to look for the proper operation of the little switch which resets the device when you slide the cover back on. On the Looxes this is operating by a small pip on the back cover. You should try the device with the battery firmly pushed in and the cover off. Then try delicately (it is very tiny and delicate) to operate the switch. Look at the screen while you operate it? It is a simple spring loaded micro switch. It should have a similar effect as a soft reset, taking you back to the climbers screen. Worth a try. I have had problems with it putting the device into a odd "stuck" state from which there seemed to be no way out with normal soft or hard resets.
There must be an engineer somewhere who might attempt a repair????? I was an electronics engineer some years ago, but have long since hung up my soldering iron, otherwise I would offer!
Related
Help, I have a 620 that up until recently has worked great with Win6.1 upgrade, the problem is that it shows fully charged 100% all of the time. I thought that maybe the battery had just shorted out some how, but when I tried the new battery it does the same thing. It will sync properly and function right, just all of a sudden will go dead without any warning. Any ideas?? Please.
I would just try to restart it if not charge it up all the way and than reflash your phone.
I have tried restarting the phone and no change. The orange light (Charging) will come on for about 10 seconds and go to green (Charged) even with the phone off.
Anybody?? Any ideas??
One last try,
I don't want to brick this thing. Anybody have any ideas??
no real good ideas, since you have already tried a new battery. That would have been my guess.
Are you only using a charge cord, or do you have a real charger as well? USB ports are around 500mah, and I thought the charger was closer to 750, could even be 1a. Also, check the contacts to the battery, use an eraser or if you have a hobby store around use a model railroad track cleaning eraser (slightly abrasive). Thats about all I can think of, I have had issues charging before but they were all due to the battery.
Take out the memory card, then charge the phone.. run the battery dead then recharge it and try inserting the memory card. Many times what looks like a battery issue is really the memory card and removing it 'solves' the problem. If that does not work do a hard reset and cross your fingers that it is just a bad battery profile.
I'll try the memory card. Will let you know what happens.
OK, tried the memory card. Didn't change anything. Tried hardreset, still no luck. Reflashed rom, still same problem. Am going to just get a desktop charger for the extra battery and keep one charged that way.
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.
I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
I've read through the forums and I saw a few similar problems like this but it seems like it those they were stuck at the bootloader, and that's not the case for me.
Basically the battery was down to 14% and I turned off the phone last night intending to charge it this morning. Somehow the battery dropped to 1% by the time I went to turn it on this morning, and it shutdown (really just lost power) right after I started it. So I go to plug it into the wall charger and then:
charge light comes on
after a few seconds charge light goes off
the phone tries to boot (does little vibrate, shows splash)
after the splash screen, phone loses power
charge light comes back on
then tries to boot after a few seconds.
repeat
If left unplugged the phone just sits there dead, but upon plugging it in, it tries to boot.
I've seen it where the phone doesn't have enough power to boot and just needs to be charged for a while, but I can't seem to do that here.
Anyone have any idea how to prevent it from trying to boot after the AC adapter is plugged in?
Thanks
arimp said:
I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
Thanks
Click to expand...
Click to collapse
If you're desperate...you might try doing a hard-reset.
Why would that help? I don't know...except sometimes when really stuck it helps to just change the situation...try something completely different.
Of course, a hard-reset deletes all data and applications that you've put on the phone, which is why I suggested it as a recourse if desperate.
Probably keep the phone plugged in while doing hard-reset.
Same problem, solved by itself
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu
nradu said:
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu
Click to expand...
Click to collapse
Yes, it goes without saying -- though it's good you did -- that if you have access to another battery that's an obvious thing to try first.
The hard reset is worth trying, in general, for otherwise-unresolvable phone issues.
It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.
devis said:
It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.
Click to expand...
Click to collapse
So it was indeed a dead battery. Oddly I found someone who had a CMDA TP2 from Verizon (mine is GSM TMO), and was able to pop my battery into their phone for a minute or two and charge it to about 5%, then put it back in my phone and all was well. With their phone, plugging in the charger did not cause the phone to start up and then power cycle.
That's really weird "glitch" if you want to call it that. So mental note, don't let the battery run down too far.
Hey guys, I got a real big problem.
I've got a Rhodium100, but it won't charge nor it'll boot.
When connected to original charger or pc the phone starts. Then I can see the HTC logo and it dies again. The battery seems to be totally dead
What I've triend so far:
1. Pulled out the battery
2. Multiple cabels for the charger
3. Soft reset
4. Hard reset (won't complete because the battery is dead)
5. Checked the on/off button (on top)
What else can I do to fix this problem? I'd like to try anything before sending the phone to HTC (did that 2 times before, but with other problems).
This is what happens: MOVIE
Thanks in advance
trilbert said:
Hey guys, I got a real big problem.
I've got a Rhodium100, but it won't charge nor it'll boot.
When connected to original charger or pc the phone starts. Then I can see the HTC logo and it dies again. The battery seems to be totally dead
What I've triend so far:
1. Pulled out the battery
2. Multiple cabels for the charger
3. Soft reset
4. Hard reset (won't complete because the battery is dead)
5. Checked the on/off button (on top)
What else can I do to fix this problem? I'd like to try anything before sending the phone to HTC (did that 2 times before, but with other problems).
This is what happens: MOVIE
Thanks in advance
Click to expand...
Click to collapse
Buy a new battery and see if that helps. There are some cheap ones on ebay.
I just found another cable and it seems to be he's charging again. But after 5 hours of charging it's still on 40%.
When the battery-level is around 45% it goes downwards to around 38% and then to 45 again..
This is circulating..
How can this be?
You shouldn't let the battery completely die in the first place. A deep discharge of any Lithium Ion battery is not recommended because of this. If you've tried to do a hard reset and it did not complete, you may have destroyed the ROM image. If it doesn't turn back on, flash a stock ROM.
Always try to charge the device before it gets to 5% remaining battery. 10% is recommended, but 5% is the lowest the battery should ever be. Having a second battery is always a good idea. I have two of them and an external battery charger. This way, I can always have a battery able to charge without needing the device just in case something goes awry.
Make sure you do not turn the device on. Leave the battery in the device overnight on the charger without turning it on. If it still does not function after this, you might try purchasing another battery and charger.
If you have time left on your warranty, this is covered by it. Simply call your carrier or HTC and they will fix it for you. It's generally faster to go through your carrier if you have the option to do so.
Thanks for the tips. I followed them and it seems to be my phone is fully working again!
Nothing helps with TP2 reanimation
trilbert said:
Thanks for the tips. I followed them and it seems to be my phone is fully working again!
Click to expand...
Click to collapse
I have the same problem since august 2010. I've do the same as you flashing some ROM's also restoring original one(T-Mobile), buying new akku ang external charger- but nothing helps When I place battery in phone it switches on by self(seems like power button abridget but I've checked it with testing device), starting showing T-Mobile logo "Stick together" then shows windows logo then backlight fading then device restarts, so it happen infinite till battery fully goes empty. Now on phone is installed original ROM and I can't install any other- in bootloader I can install only SPL's, but other ROM's not installs (flashing process freezes on 0%). I haven't any ideas, somebody can help me? Thank you all.
mrRadja said:
I have the same problem since august 2010. I've do the same as you flashing some ROM's also restoring original one(T-Mobile), buying new akku ang external charger- but nothing helps When I place battery in phone it switches on by self(seems like power button abridget but I've checked it with testing device), starting showing T-Mobile logo "Stick together" then shows windows logo then backlight fading then device restarts, so it happen infinite till battery fully goes empty. Now on phone is installed original ROM and I can't install any other- in bootloader I can install only SPL's, but other ROM's not installs (flashing process freezes on 0%). I haven't any ideas, somebody can help me? Thank you all.
Click to expand...
Click to collapse
It's a dead battery. If it powers on by itself, then you'll either want to get a new battery or an external battery charger. Make sure you're charging from the wall, and not a USB port.
cajunflavoredbob said:
It's a dead battery. If it powers on by itself, then you'll either want to get a new battery or an external battery charger. Make sure you're charging from the wall, and not a USB port.
Click to expand...
Click to collapse
Yes, I do as you suggest - bought new battery and wall charger, but no result. I doubt that new battery or charger is destroyed, but anything is possible... What actually kind of problem if phone couldn't do hard reset, not upgding ROM, also switches on when battery is placed into? 100% fault (discharged) battery?
mrRadja said:
Yes, I do as you suggest - bought new battery and wall charger, but no result. I doubt that new battery or charger is destroyed, but anything is possible... What actually kind of problem if phone couldn't do hard reset, not upgding ROM, also switches on when battery is placed into? 100% fault (discharged) battery?
Click to expand...
Click to collapse
I mentioned that you may need to charge the battery externally if it is powering on when you insert the battery. You'll either need a friend's phone to charge it, or buy an external charger. With the external charger, let it sit on the charger overnight, pop it in the phone, and then try again. If using an external charger does not work, then you may want to send the device in for repairs/replacement.