Related
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
I have been running the new cm9 ics ROM for about 2 days now, and had just got all my data and apps sorted and fully working. I sat down, watched some TV, and after 30 mins i checked my phone. Black screen ( i assume its locked) i tap the power button, nothing, again nothing. I now think i must have turned my phone off. I now hold the power button, nothing, again, nothing. I grab my charger, put my phone on charge and notice no orange or green light. I have repeatedly tried to revive my phone but nothing works. I don't know if its the software, battery, charger, Im so confused. Please if anyone has had the same problem, or has any suggestions, i would appreciate it very much. Thanks.
some extra details: i charged my phone over night the day before, so it shouldn't have died ( i know you shouldnt charge overnight, but i do :/)
i wasn't trying to flash anything or messing around with files, it was in my pocket.
i didn't drop it
Gaff3rs said:
I have been running the new cm9 ics ROM for about 2 days now, and had just got all my data and apps sorted and fully working. I sat down, watched some TV, and after 30 mins i checked my phone. Black screen ( i assume its locked) i tap the power button, nothing, again nothing. I now think i must have turned my phone off. I now hold the power button, nothing, again, nothing. I grab my charger, put my phone on charge and notice no orange or green light. I have repeatedly tried to revive my phone but nothing works. I don't know if its the software, battery, charger, Im so confused. Please if anyone has had the same problem, or has any suggestions, i would appreciate it very much. Thanks.
some extra details: i charged my phone over night the day before, so it shouldn't have died ( i know you shouldnt charge overnight, but i do :/)
i wasn't trying to flash anything or messing around with files, it was in my pocket.
i didn't drop it
Click to expand...
Click to collapse
Don't panic. Stay calm. The most of our ics roms suffer from reboots or freezes at this stage of development. Your phone simply froze, this can happen with screen on or turned off. If the three button combo (power and volume + -) does not work, You need to wait until the battery drains out.
if you pull the battery there is a chance to freeze your emmc chip and really brick your phone. If you connect the phone to PC before pulling the Batt there's a little lower risk. But I still don't recommend to do so. After your phone is running again, you should overvolt by 25 to hopefully prevent your phone from freezing again.
Ps.
Really, please stay calm, this happened to me about 20 times on ics roms and I'm not the only one.
Sent by my fingers to your head.
thanks, i will just wait then, is it normal that adb won't recognise the device? and also two things, how long roughly will it take to drain completely? and when it is completely drained, what do i do? charge as normal?
thanks a lot
Gaff3rs said:
thanks, i will just wait then, is it normal that adb won't recognise the device? and also two things, how long roughly will it take to drain completely? and when it is completely drained, what do i do? charge as normal?
thanks a lot
Click to expand...
Click to collapse
1. Yes, if it's frozen adb does not recognize the device
2. Depends on how much loaded your battery was. Could be between 1-12 hours
For me very often it didn't need that long, phone restarted by itself after some time.. (30 mins?) But sometimes I also had to wait long..
3.yes, charge normal
Edit: since your screen is off it could take even more than 12 hours
post your results
Sent by my fingers to your head.
Nothing yet i think i will have to wait to tomorrow
EDIT: 11:00 am GMT still nothing, it's been almost 24 hours; should I just keep waiting?
And is there any way to tell wether it's frozen, or the Emmc chip is broken? Thanks
Hey, I've been looking around the forums, and it seems to me that my phone's emmc chip is fine. I admit I did, in a panic, pull out the battery and re-insert it, but on other forums people with a 'fried' emmc chip can at least boot their phone, mine is just completely un-responsive, with a black screen and nothing, when you put it on charge. Am I right or could you shed some light on the problem?
Thanks
Gaff3rs said:
Hey, I've been looking around the forums, and it seems to me that my phone's emmc chip is fine. I admit I did, in a panic, pull out the battery and re-insert it, but on other forums people with a 'fried' emmc chip can at least boot their phone, mine is just completely un-responsive, with a black screen and nothing, when you put it on charge. Am I right or could you shed some light on the problem?
Thanks
Click to expand...
Click to collapse
Seems to me exactly like the freeze I and a bunch of others are suffering from. If you think you can take the risk, you could try pulling the battery.
1. Connect to PC first.
2. Pull battery.
3. Pull USB cable
4. Insert battery after few minutes
5. Try to reboot recovery with adb
As I said there is a chance of freezing your emmc. You might succeed, but you might totally brick your phone too. I'm not responsible, I told you the risk..
Sent by my fingers to your head.
I had a spare battery lying around, did what you said above, instead putting the other battery in and not going on adb, but nothing happened. I think I am going to have to try what you said above ^^^
Oh and once I have put the battery back in do I turn the phone on? It might sound stupid but I don't want to get it wrong :/
Alright a few details:
My phone connected to the computer with a battery in (I don't have a clue how full it is) is not recognised as a 'device with removable storage'
It won't charge (or the orange light won't come on)
Yes, to see if it's booting, I would suggest to turn it on
As I said, try to reboot via adb.
And I would recommend to reboot into recovery and flash another ROM or backup, you don't want to freeze your phone again today, do you?
Sent by my fingers to your head.
I've taken my bay out and am just waiting a few minutes :/
Alright it seemsbe booting, could be a boot loop though
Edit : it's working I'm on the home screen of cm9
You don't know how much I love you right now thanks so much for all the help (I didn't even need adb, it just booted normally 0.o)
Keep your fingers crossed
Edit: glad you already solved it.
You're welcome mate
Sent by my fingers to your head.
As I said, overvolt by 25 to hopefully prevent the phone from freezing again.
Or simply do flash a stable ROM. I would prefer this as I don't like to freeze my phone and brutally pull the batt
Sent by my fingers to your head.
I'm trawling through pages and pages of ROMs I think I will stick to stable ones now
If you want sense, try endymion, by far the best.
No sense - reaper, fastest ever.
Just my personal opinion.
Sent by my fingers to your head.
I may have not the thread in its entirety..
But did you try VolumeUp + VolumeDown + Power button combination.
Which can often reboot a hung/stuck phone?
Ok, stop me if you've heard this one before (I've searched and searched to find a solution to this issue, so I appreciate any help I can get)
I recently rooted my TF101 and have been flashing different ROM's to see which one I like the best. I'm not a complete NOOB, but I've never done flashing on a tablet before. I flashed Megatron 1.6.1 and when I went to reboot I couldn't get out of recovery and it kept looping back to recovery despite my doing a complete re-wipe/flash. When I finally powered down I wasn't able to power back on.
Now the unit will not turn on, either regularly or in recovery. It's completely dead. I've been letting it sit plugged in for a while to see if that helped and still nothing. I've held the power button down in every conceivable way and for different lengths of time and still nothing.
I'm at my wits end... any help would be AMAZING!!! Thank you in advance.
Can you get into APX mode? You may want to nvflash back to stock and try again.
Sometimes the tf not really shutdown, it just freeze in black screen when we thought it already shutdown. Undock it and plug in charger to see if it charging as it might be given up totally battery drained.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Rogueharvest said:
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Click to expand...
Click to collapse
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
redninja007 said:
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
Click to expand...
Click to collapse
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
new damages
farsight73 said:
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
Click to expand...
Click to collapse
i already tried nvflashing back to stock it went back to stock but the screen still wont turn on...i charged it for 12 hours still nothing.but it plays music still ...after getting pissed off,,,my wife hits the tf101 screen and then it turns on finally but the screen was orange and red... then she hit it again then i think she damaged it once more hahhaha....im pissed off too but when thinkin bout her face while hitting the tf101 EPIC hahahha...any help wanted i wanna buy new screen... attatched is the picture she sent me hahaha
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
---------- Post added at 11:47 PM ---------- Previous post was at 11:38 PM ----------
Chichoman said:
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
Click to expand...
Click to collapse
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Chichoman said:
<snip>
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Click to expand...
Click to collapse
This won't do anything for the OP's inability to boot. That's why I said that likely his best bet is to see if he can boot into AP Fastboot, so that he may be able to FXZ back to stock...
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Apex_Strider said:
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
fire_fist_ace said:
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
Click to expand...
Click to collapse
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Apex_Strider said:
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Click to expand...
Click to collapse
The battery reset actually worked! I had to charge it for quite a while on the usb charger since it wouldnt charge on the mains charger. Once it was on i made a backup then cleared the battery stats, and now it detects the mains charger.
Cheers for your help guys i still dont get why it wouldnt charge on the mains charger when the battery was low, even though before it would charge before when the battery wasnt...
Hello,
I am an owner of HTC Sensation, rooted with Android Revolution 7.3.
My phone has ~1,5 years, since its first days i was using Android Revolution ROM, never had any problem.
Today, my phone first lost signal. Itcould not connect to any mobile network so I tried to restart it, when i got back to it after 5 minutes, the phone was stuck on beats audio logo and when i touched it, it felt very hot, it was never that hot even I used it for hours playing some games or browsing internet. (I think it was processor, down side of the phone, below battery, but because of that battery got a bit hotter too) I had to pull off the battery, I've waited till it got cold and tried to run again but rom was not working so i reflashed it from my sd card, after the next restart (phone did not get hot) when phone was checking installed apps, it simply turned itself off. Before battery showed around 80% charged, after reinstall 30% and it happened in max 10 minutes ,but after that shut down I could not turn it on. LED was not working, I tried pulling off battery, charging it, charging without abttery then connecting it, trying to reboot with abs but PC could not see the device.
The only thing I noticed, when i was trying tocharge it for the first time, processor was getting hotter but LED was not working, but then, it simply went cold.
I have no idea what I could do more here, it looks like hardware problem but te only thing i could not check was putting a new battery and try it then. Is there anything I can do more about it?
For any help, thank you.
PS: When the phone 'died' it was using faux123's 1,5 GHz kernel which came with the ROM. AsI said, before this event, everything was working perfectly, no sign of this incoming event. No restarts, freezes or crashes.
*If it matters, i was charging phone every 4-5 days, never let it go below 10%, bettery is from HTC EVO 1730mAh (original).
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
rzr86 said:
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
Click to expand...
Click to collapse
I can do nothing. No reaction.
MarcBliz said:
I can do nothing. No reaction.
Click to expand...
Click to collapse
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
rzr86 said:
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
Click to expand...
Click to collapse
Re-tried these methods, hoped I had done soemthing wrong before. I saw the artice before, was hoping there are different ways to revive the phone. Tried this, says device not found. Looks like the only method would be this JTAG box but it's a bit expensive or try to send it to repair.
Anyway thank you for your time, I appreciate it.
-And if I might ask, any idea why the phone heated up itself on nearly last startup as I mentioned in my thread? It would be allright if the phone just died before this event, now it just makes me think there might be bigger hardware problem which just caused the death and it's not worth repair.