Related
after i attemped to upgrade my jf 1.41 rc 30 to jf 1.41 rc 33 my phone freeze and then i took out the battery, try to turn it on and it wont turn back on is there any way or any buttons i need to push to get this back on again? i'm desperate and dont want to wait for a g1 replacement which is coming next week please give me some advice on how to make my phone work again.
both CAMERA/POWER and HOME/POWER are not working?
yup both i tried nothing works
ariex said:
my phone freeze and then i took out the battery, try to turn it on and it wont turn back on.
Click to expand...
Click to collapse
Did you put the battery back in?
what do you think?
I upgraded from JF 1.41 RC30 with no problem, Radio and all, good luck!
ariex said:
what do you think?
Click to expand...
Click to collapse
So far you are the only person with this problem so we are running through the basics.
Did you get any errors or messages during the update? Did the phone run out of battery mid update? Did anything odd or unusual happen?
quick question in while in the topic, had he done a FULL nandroid backup and was able to atleast get to boot screen would he be able to restore his phone? just a quick questions because to this day i have no idea how the nandroid thing works i cant do it on my x64 vista either and dont see how it comes in handy lol. Sorry just trying to fig it out.
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
@zgjbeta Yes. If you can get to the blinkin android screen, your not really bricked. Nandroid would fix it right up.
If it wont even turn on, like your case. I dono what to tell you.
For starters, try to connect it to a wall outlet to make sure its not the battery.
Also tell us exactly what happened during the update process.
EDIT: I read your most recent post. That's strange because everyone gets the chip thing, you shouldve tried home + back or menu + green + red.
One of those wouldve most likely worked.
Good luck.
Also maybe try to take it out again and put it back in.
I had the chip and arrow after the radio update, I didn't take the battery out, started pressing random keys, lol... and then it went away and booted back to a JF recovery style screen. Pressed home + back and it rebooted to a stuck flashing android. Then did call+menu+end to reboot and it has worked fine ever since.
There is definitely something whacky going on...
yes i tried to do the home key plus end and camera plus end options while in that chip state but didnt do anything so i resolve to take out the battery and it wont turn on again. i also tried all the button reset combo nothing happens
If it wont even turn then there is really nothing that can be done. Another thing I would try is if you know someone else with a G1 try their battery.
ariex said:
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
Click to expand...
Click to collapse
Also try cleaning the battery contacts in the phone and on the battery. This happened to one of my dumbphones once - cleaned out the battery contacts and it worked again. Bizzare situation, simple solutions first.
You might've turned it off while it was writing a vital file. Thus your phone might be bricked.
Here's an idea - sent it back to T-Mobile/HTC - and I don't think they will notice you violated your warranty until it's too late (they have to fix your phone to find out) so you could just refuse to pay and have them send it back to you.
I too saw the chip with the arrow thing, so that makes 3 people in this thread. It happened when I did the radio update. Anyway, in my case, I held down the recovery mode keys for a while and it went to the menu. Then I just rebooted and everything was great. Glad I didn't take out the battery (I considered it).
I had the chip and just waited and it took care of itself. Just be patient people.
plug in the wall charger, wait 10 seconds, then hold the red power button for 3-5 seconds then release, it should turn on
i tried that didnt work anymore advice?
also is there any way to run diagnostics of this phone to pc to make it work?
If the phone won't turn on, go back to the T-Mobile store and ***** em out. Not much else to say if we can't even get power to it.
background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*
Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk
Did you try booting into recovery mode instead of odin?
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
if u can boot into cwm flash darkside
OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?
Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...
I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe
Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727
The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m
Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...
He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.
Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...
As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.
Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.
Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
---Edit---
I should note that I can have all the radios on when it is plugged in, I just can not have them on when unplugged right now.
mikeoconnor said:
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not?
If you're rooted/on a custom ROM, I would make a backup of all non-system apps and settings and try to start over. The fact that you dont get that when in recovery is the biggest indicator.
First, back up all NON-SYSTEM apps/settings with Titanium backup (or something similar).
Then follow my fix >>>HERE<<< and see if that helps
I am currently on CM-10-20130728-NIGHTLY, I should also note one thing I did try was to update the ROM yesterday AFTER the problem started (problem started at 4pm I updated the ROM at 7pm), it use to be CM-10-20130526-NIGHTLY. I will look at your link and see if that works.
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I hope you are wrong, but I fear you are right. But I am going to do the steps cited above and see if that helps, right now I am doing a second back up (first was Titanium backup, now is the CWRM backup) and I am going to do the flashing stuff who knows. Don't have much to loss, and I am still open to other ideas, if any one else has them.
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's a distinct possibility, but not the only cause for what he's experiencing. Jumping the gun and buying new hardware usually results in money spent on hardware that wasn't needed a good portion of the time.
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
mikeoconnor said:
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
Click to expand...
Click to collapse
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
jparnell8839 said:
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
Click to expand...
Click to collapse
It is white (indicating no water damage) also the other indicators on the phone are white. I hope you are right on that that would be sweet, I will stop by the tmo store before I head home tonight. And thanks for all the help (I now have to go back and "Thank" all the posts by you two, it is appreciated)
Funny part is I took the battery out to double check the sticker (even though I was sure it was still white) and the phone died even though it was still plugged in (so I guess I need both the battery and power plug for now)
mikeoconnor said:
It is white (indicating no water damage) also the other indicators on the phone are white.
Click to expand...
Click to collapse
you might get lucky and get a free one out of it. cant hurt to ask
Thanks all I picked up a new battery today and I looks like it is working. Sadly T-Mobile did not replace it for free but the phone is working again.
Sent from my Thrive using Tapatalk 2
Hi. I'm somewhat new to the forum. I've read a lot of info on this website that helped me root my G1 when I had it and my Doubleshot. I was running CM 9.1 I believe and it was working fine. But then my girlfriend wet her phone (Sony Xperia) so I let her use mine while we waited to get her phone a new phone. While she was using my phone she somehow killed it. It won't turn on at all. I can get into bootloader from ADB but when I try to power it on from there, it goes to the splash screen then 1-2 seconds later it shuts off. At first I thought it was a battery issue so I ordered a new battery from ebay, popped it in but was still having the same issue. I had it overclocked to 1.7 Ghz I think and it would run hot sometimes when I would play a game. I'm wondering it got so hot that it actually fried something. Anybody have any idea what could be wrong with it?
chillywilly638 said:
Hi. I'm somewhat new to the forum. I've read a lot of info on this website that helped me root my G1 when I had it and my Doubleshot. I was running CM 9.1 I believe and it was working fine. But then my girlfriend wet her phone (Sony Xperia) so I let her use mine while we waited to get her phone a new phone. While she was using my phone she somehow killed it. It won't turn on at all. I can get into bootloader from ADB but when I try to power it on from there, it goes to the splash screen then 1-2 seconds later it shuts off. At first I thought it was a battery issue so I ordered a new battery from ebay, popped it in but was still having the same issue. I had it overclocked to 1.7 Ghz I think and it would run hot sometimes when I would play a game. I'm wondering it got so hot that it actually fried something. Anybody have any idea what could be wrong with it?
Click to expand...
Click to collapse
It could be that the high-intensity load is causing panic, shutting the device down. It could be that it doesn't like the overclock anymore.
Let's rule out a couple things.
Go into recovery (CWM / TWRP) and wipe data and cache (factory reset). Reflash Gapps while you're at it.
If recovery causes the same problem, reflash recovery in fastboot mode. If recovery still doesn't work right (shutdowns), you can try a different version, but it may really mean something got fried on your MT4GS.
If you were able to get recovery to do your bidding, reboot. Does the system still shut down on boot? If so, this time reflash CM 9.1 and GApps with the data/cache wipe, reboot. If still problems, try a different ROM, like Miktouch. If it fails there, then you may really be having hardware problems.