Related
As i said on the title,suddenly i couldn't recharge my Universal anymore,yes i've tried with a brend new official battery as well but everything was in vain.As soon as i plug my charge to my Universal it appear a Red Led and after 3 min or so the led turn off and so the battery.
How can i fix this problem?!
Is there any chance?!
Is it really dead like that?!
Please HHHHHHHEEEEEEEEELLLLLLLPPPPPPPPPPPPPPPPPPP!!!!!!!!!!!!!!!!
If the battery is really brand new, then I guess the connectors might be damaged or the internal power buses might be broken somewhere. Have you dropped your device recently? Or did anything that might explain broken connectors or internal buses?
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
tetsuokaneda said:
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
Click to expand...
Click to collapse
It can be a software error. Have you tried hard resetting or installing another ROM?
tnyynt said:
It can be a software error. Have you tried hard resetting or installing another ROM?
Click to expand...
Click to collapse
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
tetsuokaneda said:
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
Click to expand...
Click to collapse
Your battery is fine, unfortunately your device broke
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
mzalan said:
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
Click to expand...
Click to collapse
I wanna die!!!I'm completely Fu.. up!!!
What a terrible news!I can't believe it!!!!
If i'll bring my phone to the assistant i'm gonna pay alot of money,at least 200.00 euro!!!!
similar problem
i had the exact same thing happen to my EXEC when i got 2 new batteries for it. One was a standard sized, pretty much the same as the stock one that came with the phone and one was a much larger capacity one that needs an extra cover for the back.
Id been using the device for ages on this huge battery and the charge said 100% constantly. then the device turned itself off and it wouldnt come back on. upon connecting the charger the LED was red, so i thought the battery was dead. I left it on charge over night and when i tried again the next morning it was fine.
this happens everytime with this battery, it just needs a much longer charge than the standard one, and doesnt register properly on the default OS, i havent tried it on my recent upgrade to one of the midget roms.
so try leaving it on charge over night or for a very long time. if all else fails just get a new battery.
That might reset the battery back to life, but I wouldn't exactly count on that. A battery with a broken monitor circuitry is pretty hard to reset.
My last hope,i'm gonna leave charging my phone for a day and then see what happend....I'm desperate
Permanent red light...
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
wtpelzer said:
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
Click to expand...
Click to collapse
Could u post it please?!
Took a while but here it is...
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Same Problem, Led Indicator Always red
Hi,
We have the same situation, my jasjar just died in my hands, im reading a txt messages then al of the sudden it hangs, so what i did is reset it but it didnt power on, i removed the battery then after 10mins i put it back but then no power,then i charged it but it didnt power on too and the led indicator is always red, they say that if the indicator is red it means that there is no battery or the battery is missing but i check it thoroughly,the battery is perfectly place on the back of jasjer, i even tried to enter to bootloader but it cant. If anyone knows how can i revive my jasjar pls pls let us know....Thank you so much.
So sad till now there's no single solution.....
wtpelzer said:
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Click to expand...
Click to collapse
Exactly if my Jasjar is completely dead how can i connect via usb and then use mtty?!
I'm losing my hope to bring it back to live!
have same problem - can do nothing, still waiting
but there is one thing - led flashes once, when i put the charger into the device - but it does nor light, nor flashes - exactly nothing happens
If your device is dead...
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
wtpelzer said:
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
Click to expand...
Click to collapse
The point is that the device is dead and that is why the constant red light. I have a device that is stuck on the splash screen (no solution in sight) and another that fell down and broke. The one that fell down does not power on. If you put a charged battery ang plug in the charger nothing happens, no light comes on, but if you put a discharged battery the red light comes on. I have a third Uni that I accidentally flashed with a BA rom. It is behaving exactly like the broken uni, it does not turn on, does not go into bootloader and the red light comes on when I plug in the charger with a discharged battery in it.
For some things, there's just no cure...
Okay I understand where you're coming from but essentially what you need to do, under normal circumstances, is connect it to your PC, which if the device is working at all the PC will detect it but not connect... In the case of two of your Uni's I don't think this will help - the dropped one and the BA ROM failure. The one with the Red LED, which has stopped working could be a component failure on the board or it could be a Corrupt DOC table. Now to get back to how you'd go about fixing it if it is a corrupt DOC table, when you connect it to the PC and the PC detects it you disable ActiveSync and start MTTY it should give you the option of connecting to the USB port, when it does this if you get a prompt the problem should be fixable because MTTY can "talk" to the device... As for the other's try this method and if it doesn't work sell them for parts or canabalise the one for parts for the other...
Earlier today my ATT Tilt was having trouble synching to my office system; it would charge, but it would not be recognized by Active Sync. I had been planning to flash the new HardSPL tonight anyway, so I thought I'd check different cables on the home system while I looked to update the SPL.
When I got it home, none of the cables or other systems would change the basic problem: the unit would charge, but the device would not be recognized. I tried soft resetting it, but that did not help. I thought I'd try taking the battery out, then try a hard reset.
After taking the battery out, the system went straight to the tricolor boot loader, with "serial" underneath. The micro SD card it had in it wasn't formatted for FAT32 and didn't have an image on it, so it just stuck there.
I removed the microSD card.
I then tried plugging in the USB cable (which does change the screen from serial to USB), but attempting to flash a ROM still fails, as the USB connection still seems to be dead for that. Hard reset does not change this; it goes straight to tricolor.
It didn't seem to be charging on the usb or on the charger (no yellow light), so I also I removed the battery so as not to waste any remaining charge.
My current theory is to get another SD card in the morning, format it with FAT32 and see if it will flash a rom. Any other, better ideas?
Since I had the (v1) HardSPL on it with one of Dutty's ROMs, I am a
bit afraid to send it in for warranty replacement repair, at least until
I can restore it. But if I can't get anything to it, it's going to be a bear
to get through the diagnostic update to restore the original rom.
If I am missing anything obvious to try here, I'll glad take the noob points, but I'm stuck for better ideas.
Thanks for any thoughts.
Mtty doesn't work
Meant to mention that mtty.exe doesn't work through USB.
No Joy with sd card, hmm
So, I re-formatted the SD card, put an image on it, and it was recognized. It loaded the radio and OS, gave a success message and stayed on the white screen. I did a soft-reset, according to the "Flashing with SD cards" instructions, and it returned me to the boot loader and offered to re-run the install. I did that (why not, I guess?), and it did the same thing.
This had been Hard SPL'ed, but I'm trying a return to the stock ATT rom now. Any other thoughts much appreciated.
<edited>Same thing happens with the stock ATT rom. If I load it via SD card, it reports success, but a reset returns to the tri-color screen if the SD card is taken out and to the "loading" screen if it is not.
Hey there,
It seems I have a similar problem as you. A few days ago, I wanted to install this rom:
http://forum.xda-developers.com/showthread.php?t=392245
There was a hardSPL with it. Copied it to my device, ran it (went into tricolor mode, so that's good). From there, I wanted it to flash it, but my laptop didn't recognize my Kaiser anymore. Soft-resetted the thing, went back into windows mobile.. good. Bu from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
moos said:
Hey there,
But from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
Click to expand...
Click to collapse
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
I have had some issues with getting usb to recognize in the tricolor screen. In my latest spl flash, it took about five trys to get it to work, you have to be persistent some times.
Anyways the steps to get it recognized are as follows:
1. I plugged the phone in, (with the os booted, you can't do this obviously) and waited for activesync.
2. Went into bootloader mode, in the tricolor screen it said I had USB, but I was never able to flash.
3. Disconnect the usb while in tricolor, and wait about 15 sec and plug it back in.
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Speaking_On said:
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
Click to expand...
Click to collapse
At this point, the tricolor screen is showin the following:
KAIS130
SPL-1.JUMPSPL
CPLD-8
I already got my laptop to recognize my phone, just gave it a reset. I'll update as soon as my phone is over 50% of charge.
i had the same problem with my usb port...
I have just been flashing roms from microSD but I am stuck with radio from hell with no way to change it without usb connection
i also wanted to flash a new spl but have read that it is not recommended to do so from sd card.
not sure if its a hardware or software problem, in either case, it is a problem with the phone, i have tried it on many different computers with many different cables and i also tested my brothers tilt which is detected by each computer immediately.
rcm_rx7 said:
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Click to expand...
Click to collapse
Thanks for your message. The phone is showing olipro (I had flashed it with HardSPL before all this started; I was getting ready to update it to the new HardSPL for WM6.1 ROMs). I've tried a couple of different cables and the usb seems truly gone. I have had problems with it being a bit sensitive in the past, so I think the pins have just shorted at this point.
All else has failed...
GSLEON3 said:
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Click to expand...
Click to collapse
Thanks for the message. There aren't two activesync sessions running on the XP system, and there are none on the phone (as it is stuck in bootloader, there is no way to get to its task manager).
After calling in to ATT and finding a fairly knowledgable tech (Ben, no last name given), it sounds like the original problem was that the mini usb slots has bent pins which caused a short. Somehow, when I removed and re-installed the battery, that short went from preventing a synch to toasting the OS. My first Tilt had a red-light of death on first charge, so I pretty much believe that something in the electronics connecting the usb/charger and battery is delicate on Kaisers.
They're going to send out a warranty replacement tomorrow, and the RMA packaging for returning this unit. I guess I'll just cross my fingers that they don't boot it and notice that it isn't a stock SPL. Given that it's being written up as a hardware issue (as it is), hopefully they won't.
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
I think I got it..
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Theoretically, yes
rcm_rx7 said:
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
Click to expand...
Click to collapse
I did try flashing the SPL from the microSD, several times and using the stock ATT SPL was one of the choices. It reverted back to tri-color boot mode.
Theoretically, yes, they could demand payment. I've heard of them doing that if a customer said that a unit hadn't been wet, but they found that it had when they did diagnostics. Down from that, they could terminate the warranty or shut off service. Now that T-mobile is getting higher speed, that's not the threat it once was, but still.
The battery is now also empty (since it had no way of charging), so I am hoping they won't even bother.
Glad to hear it!
moos said:
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Click to expand...
Click to collapse
Glad to hear it worked for you! I couldn't get my system even close to that functional to get there, but it's good to know that you were able to get through.
kaiser usb dead
I have the same prblem as your USB is gone cannot move from tricolor screen. Cannot even flash from sd card. Check my signature for the link of my thread it explains everything that happened to it.
hello,
i'm interssested to buy it. can you send me your mail at [email protected]
Hello ppl,
since 2 days I've got a big problem with my Polas (at all XDA Orbit 2)
Ok first the bad story. My device did take a little shower and had water in it, which seems to be dried out now.
First, you all should think there is nothing to rescue here anymore.
BUT after the first problems (i will tell you some lines below), later on my device got working again. It worked for nearly a whole day.
And then the same problems as before came back again and now I'm stuck on it.
Here is the scenario:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
- With Power Plug: I turn on the device. Showing the o2 Splash Screen. And that's it. Not even the ROM Version Numbers are showing up. When I take out the Plug after a while, XDA just turns off. Oh and the orange LED is lightened.
I can also plug it in while the XDA is off and it shows the orange LED, so you should think it's getting power.
But it doesn't when I try it afterwards without the Plug.
When I boot up without the plug, and plug it in after the Splash Screen, it's the same behaviour as on the scenario "Without Power Plug", it doesn't recognize that the plug is in or is not getting power I don't know.
So why was it working for one day? I don't get it!
You think that maybe only the battery is damaged? But why was it working?
I hope this text is not too confusing and maybe somebody is able to help.
I'm dying without my lovely device.
Oh and yes, i did try a hard reset.
I think the biggest problem for me is, that the device doesn't boot when the plug is in. That is totally weird from my perspective.
Thanks in advance!
gmc
Weird! I am able to flash the ROM. But still the same ;( What the hell?
While flashing the ROM there was no sign of a not working battery.
I'm confused!
Update: Re-Flashed O2 Rom and also tried udK Diamond. Flash is always successful but behaviour doesn't change or get fixed ;(( This can't be true.
Well one question... when the version numbers show up on the Splash Screen what is the "G"-Number? It looks a bit weird, "25.69.30.05H"
Maybe that part of the ROM is down?
gmc said:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
Click to expand...
Click to collapse
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.
satfly said:
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.
Click to expand...
Click to collapse
Thanks for the link. Will check it out. As there is no more sign of water damage on my device, i hope i can use the warranty too.
Hello,
i have a brand new o2 XDA Touch pro. After trying (unsuccessfully) to remove the CID to flash the original HTC Firmware (the O2 Firmware was lame), the XDA went off and is completly dead now. The last thing I was able to see was a strange display behaing (some strange look and fading off).
The phone does not react on pressing the Power-On Button! No reaction!
Can anyone help me or has anyone a hint how to hard-reset the device?!
So far I remember there was a trick by removing the battery for about 24 hours (this worked for my older xda mini s phone). May this work for this phone, too?
Please help me!!!
Best regards
Gabriel
Did you try the old tric to remove the battery and then put it back in? When you do the Hard-SPL it would remove the CID lock. It would seem to go dead and unresponsive as happened with mine. I just removed the battery and put it back in and it powered up fine. Checked the tri-colour boot screen to make sure it was done. It is in the thread for flashing your first ROM.
Hello wildcard,
thanks for your reply.
I already tried removing the battery. Yesterday I tried for about an our and completly off power (no USB Power or PC connected). Still no reaction after trying to power on with battery plugged.
I'll give it another try in about a few hours after leaving the phone powered off about 12 hours. So far the phone seems completly dead! I would be glad even to see any light / display going on with try-color mode, but anything keeps powered off after battery connected and giving the power-on button a try.
Best regards
Gabriel
UPDATE:
Phone still completly dead / no-power on possible after 12 hours power-off / no battery!
Tried several key-combinations for soft+/hard reset with battery and/or USB-Power even with plugging in while pressing the keys including power-on. NO Reaction
How can this be??? May it only be possible to send it in to O2?
I was unable to complete any CID unlock / HTC Firmware update on the O2 device. They stuck always on 0% or failed before this step and until that time the phone always rebooted into WM6 after battery removal. So I don't think O2 could blame me for doing anything wrong... and I don't understand why there is not even Power for Bootloader mode possible. I don't think that any software could harm the hardware in such a way that not even power-on is possible??!
Any ideas of developers to reanimate the phone? I will try keep power of for a few days now until I go to O2 with the phone...last try. For a XDA Mini S i owned once (that phone has been unlocked too), this worked once it had a similar failure... maybe I have luck in 2-3 days with my TouchPro phone.
Best regards
Gabriel
I am thinking that you may really need to send it in to O2. Might be your best bet, let's hope some one more ducarted than I am chimes in.
I think I bricked my one X im not sure how or why but out of the blue it just said the 10 second power off message and no longer turns on at first i was able to turn it on a few more times but now i cant.
It is not taking charge both from my computer or ac :/
when i plug it into my computer it says HID compliant device found. and the three led buttons light up every about 5-10 seconds but the top led notification doesnt turn on
If it matters
Hboot 1.14
on jokerfg jb rom
also this is a week and a half old device. if i have to replace it i will but I am more concerned with formatting it or getting it to stock before hand incase i send it in and they get it running
Uff. I have not encountered this issue. Sorry brother. Update if you find a fix.
Sent from my HTC One X+ using xda app-developers app
How did it get to that state?
What are the 5 contact looking things at the back of the phone for?
Sounds like you need to give the thing some charge, i'm sure one of those street corner shops can pop it open, macgyver some volts in, and reflash something that will boot for $30ish?
I'm not really sure, my power buttton is stuck but it retracts like a button should, but it has died and refuses to power up now. I just wanna turn it on to reformat it. or is it possible htc wont be able to turn it on themselves and when they receive it just trash the device?
gururug said:
How did it get to that state?
What are the 5 contact looking things at the back of the phone for?
Sounds like you need to give the thing some charge, i'm sure one of those street corner shops can pop it open, macgyver some volts in, and reflash something that will boot for $30ish?
Click to expand...
Click to collapse
so the battery is dead and it wont charge? if it will charge youll have to relock the boatloader and ruu to stock if u cant get in to recovery
Leave the phone on the wall charger (not USB) for several hours (overnight) and see if you can boot. You might also try to power on, or hold the power button, or try to enter hboot while the phone is plugged to the charger (after letting it charge for several hours). As at least one guy that I thought was hard bricked got his phone to boot this way.
What appears like spontaneous power off has happened to some people. So it may be nothing that you did. Hopefully, letting it charge for a few hours will fix it up.
I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?
mr.5106411 said:
I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?
Click to expand...
Click to collapse
I had this happen. I left it on charge (from powerpoint not USB to PC) over night and then connected back to PC. It didnt start but the pc was telling me USB device connected and disconnected when long pressing power button.
after running RUU and changing bootloader I finally got it to work. I would try the latest RUU from US / ATT as it has newest everything and see how that goes.
vangoogle said:
I had this happen. I left it on charge (from powerpoint not USB to PC) over night and then connected back to PC. It didnt start but the pc was telling me USB device connected and disconnected when long pressing power button.
after running RUU and changing bootloader I finally got it to work. I would try the latest RUU from US / ATT as it has newest everything and see how that goes.
Click to expand...
Click to collapse
Thanks for the reply but how did you RUU if the phone connects then disconnects quickly?
mr.5106411 said:
Thanks for the reply but how did you RUU if the phone connects then disconnects quickly?
Click to expand...
Click to collapse
It stays connected. I meant u can hear the Win 7 sound of connect USB when u press power and then disconnect USB if u long press power.
Sorry I cant be of more help.
i would try ruu or another usb cable
vangoogle said:
It stays connected. I meant u can hear the Win 7 sound of connect USB when u press power and then disconnect USB if u long press power.
Sorry I cant be of more help.
Click to expand...
Click to collapse
Thank you for your help so far. Ill try this tonight.
mr.5106411 said:
I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?
Click to expand...
Click to collapse
I'm one of the folks who tried to help you in the other thread. Saying that you think people are unwilling to help sounds ungrateful and a bit whiny. Remember that the community here provides help for free, and that we also have lives and can't be on here to help you all the time.
Since you've tried charging (wall charger) for several hours, and tried (unsuccessfully) to get into bootloader, there isn't much else you can do. The idea of trying to run the RUU is a good one. But if you can't connect and can't run the RUU, the phone might be done. In particular, the blinking red light is not a good sign. I think there have been some other folks that have gotten this recently, and were not able to recover from it.
But keep trying to charge, and keep trying the bootloader button combo. The fact that your condition happened right after trying to restore a nandroid, leads me to believe its something that can be recovered from, and not a random hardware failure. But that is just a gut feeling, and maybe a bit too optimistic.
when my battery dies and i plug it up to charger led blinks red until it has enough juice to be powered on. you shouldn't try to power on your phone when it is blinking red, i assume that might end up killing the battery for good if you do.