Related
Hi all,
Hopefully you can help me, i have just installed the latest radio and Modaco ROM (this isn't the first time i've did this).
After installation i got what looked like an image of a drive and an arrow, i assume this meant it couldnt find the boot image. I then tried a couple of times to reboot holding the home key but now i cant even switch it back on... even on charge the light isn't coming on
Any help would be gratefully appreciated
Thanks
GF
When the arrow and drive comes up, you're meant to leave your phone well alone, it means it's flashing something (usually something important!)
If your phone doesn't turn on, sounds like you've made a full hard brick, nothing you can do but see if you can get it repaired.
Gutted, cheers
Can you pull the battery and get into fastboot?
Breakthecycle2 said:
Can you pull the battery and get into fastboot?
Click to expand...
Click to collapse
Not sure what that is? I've tried the various power+key sequences
Thanks
GaelForce said:
Not sure what that is? I've tried the various power+key sequences
Thanks
Click to expand...
Click to collapse
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
docsamsom said:
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
Click to expand...
Click to collapse
Worked a treat, got a doorstep exchange today
Thanks
I bought a phone as a brick, it was stuck in bootloader mode with a err:etc....
So I had it plugged into my computer used RSD which did recognize it and flashed the 2.23.32 recovery only file and that said successful. but still was stuck in boatloader I was gonna try to flash something else to it and while it was still plugged into my computer and on the bootloader screen it just went blank but the green charge light stayed on, now I have nothing, it wont come up, pc wont recognize it, but it will have the green charge light lit when plugged in.
I'm guessing screwed, anyone know something I don't lol?
kiddkill said:
I bought a phone as a brick, it was stuck in bootloader mode with a err:etc....
So I had it plugged into my computer used RSD which did recognize it and flashed the 2.23.32 recovery only file and that said successful. but still was stuck in boatloader I was gonna try to flash something else to it and while it was still plugged into my computer and on the bootloader screen it just went blank but the green charge light stayed on, now I have nothing, it wont come up, pc wont recognize it, but it will have the green charge light lit when plugged in.
I'm guessing screwed, anyone know something I don't lol?
Click to expand...
Click to collapse
What file did you flash exactly? Im not familiar with what you referenced. Also, what do you mean by RSD? Did you mean RUU? So right now you have an led light when its plugged in, bit nothing else.? What happens when you pull the battery, then.out it back and hold power and volume down. Does it get to the bootloader or no?
Sent from my PC36100 using XDA App
I used a program called rsdlite_4.8 and flashed a file called SHADO_X6_2.3.32_RECOVERY-ONLY.sbf
but it still wasnt until later when the phone screen just went blank.
I pulled the battery, and the key combo did nothing. I was getting a really faint quick blue light from the led when I tried to power it on while not plugged in, but now not even that.
Well it just finally woke back up but says battery low cannnot program on the bootloader screen, so I'm pretty sure the battery is dead now. So once I get the battery issue sorted, I'm back to trying to figure out how to fix it lol
kiddkill said:
I used a program called rsdlite_4.8 and flashed a file called SHADO_X6_2.3.32_RECOVERY-ONLY.sbf
but it still wasnt until later when the phone screen just went blank.
I pulled the battery, and the key combo did nothing. I was getting a really faint quick blue light from the led when I tried to power it on while not plugged in, but now not even that.
Click to expand...
Click to collapse
I have never heard of that program, or file. Nor have I ever noticed it being mentioned on here. Are you sure those were for the Evo? Do you happen to have a link to that file and program you used, so I can look at it? Im going to go out on a limb here, and guess.that you accidentally flashed a file that wasn't for the Evo, unless I've just never heard of that file before, then I apologize.
Are you sure the battery is good?
Sent from my PC36100 using XDA App
So I just did some Googling...about the program you used, and file that you flashed.....and now I just wanted to make sure that the phone you're working on is indeed an Evo, right? Reason I ask, is because every single bit of info I found on that program and that file, indicated that it was for the Droid X or Droid 2. Nothing anywhere mentions anything at all about using that on an Evo. I don't even think and .sbf file can be used on the evo, as far as I know. At least I've never heard of it before, in regard to an Evo.
If my research is correct, then I'm going to take a guess and say that there is a very strong possibility that you might've borked your phone.
I am retarded lol, This is a droid x, for some reason I've been calling it an evo all day. Probably cause i usually mess with evos.
Well sorry for the confusion and thanks for still trying to follow my nonsense.
I'm pretty sure the battery is cooked though so I'm gonna try to get a new one and then take another stab at it, if i still cant figure it out, then off to the DROID X forum I go lol.
kiddkill said:
I am retarded lol, This is a droid x, for some reason I've been calling it an evo all day. Probably cause i usually mess with evos.
Well sorry for the confusion and thanks for still trying to follow my nonsense.
I'm pretty sure the battery is cooked though so I'm gonna try to get a new one and then take another stab at it, if i still cant figure it out, then off to the DROID X forum I go lol.
Click to expand...
Click to collapse
HAHA, that's a riot man. I was getting mighty confused for a minute, and couldn't figure out how a program and file for the Droid X would even possibly successfully flash on to an Evo, as you said it flashed successfully. LOL. I was mighty perplexed. Anyways, good luck, and I'm sure you'll get some more assistance from the DX forums, haha. Take it easy.
Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?
charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.
Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!
I still have the phone, I'm gonna try this now. Will update with results.
aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.
Well, I tried both suggestions to no avail. Anyone else have any ideas?
aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.
no cigar with the hold for ten seconds method on the power button.
aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App
aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
That sucks. Good that they are replacing it. What was the last thing you were doing before it happened?
VoiD_Dweller said:
That sucks. Good that they are replacing it. What was the last thing you were doing before it happened?
Click to expand...
Click to collapse
Yeah I have PHP protection with them so I always have warrenty and insurance together. Its alot easier trying to get an exchange when your phone wont turn on because they dont make you do 1000 different things lol, was off the phone within 5 mins. Tried being slick and saying " Well you know if their arent any S2 in stock, you can always send me the s3 if you like ".. Didnt work =[ They had s2 lol
Anyway, nothing really. Was just typing, put the phone down, then the screen went off like it always does, then when I tried to turn it back on to unlock it, it happened.
This happened a few weeks ago but the vibrating lasted for a couple of mins ten ended up turning itself back on. Now its just not turning itself back on at all. Just stuck with the vibrate.
Am I losing everything on it now or will it automatically back up on my gmail account?
I knew I shouldnt have saved all those pix on the phone and not the sd card lol
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
Is this a thing with this phone? Got the same problem two days ago. Cant send to tmobile, any idea anybody?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
ITALIANNYC said:
Am I losing everything on it now or will it automatically back up on my gmail account?
I knew I shouldnt have saved all those pix on the phone and not the sd card lol
Click to expand...
Click to collapse
Sorry, unless you had some kind of auto upload set up ( I set mine up through Dropbox and Google + ), those pictures are likely lost.
Google doesn't automatically sync pics unless you have Picasa, I think?
Russian smashed across the interwebz from my T-Mobile Galaxy S2.
Sounds like the power button might be stuck.
I gotta say, I HATE UPS. I dont know why T-mobile uses them. You get overnight delivery and of course they ring the wrong bell and do not come back. I live on ground floor and they up and ring top bell. Fed EX of course would always come back. Thank fully the overnight delivery was basically be free, but that sucks. I also wish they would just leave the phone sometimes but they never do, even though it is not sig required. ( Drivers Discruction )
Gotta wait till Monday now.
sux brohim
had the same thing happen to me. this was back when i was dong the stock ICS update through (hang myself) Kies. Thankfully T-mobile sent me a new one at no charge and i didn't pay for the shipping either. either battery fried or something in the phone. seems to have been a fairly rare but known prob with the t989.
i always seem to to get the units that are within the .05% of defective units, no matter what company i buy from.
Here's to hoping you get better luck with the next unit! :raise a beer:
Quick question
I have used GB for my gs2 from the beginning and never upgraded to ICS.
I am worried that the replacement they send will have ICS in it. Simply put, will it be easy for me to put GB on the phone when I get it.
You can root and flash a gb Rom
Sent from my SGH-T999 using xda premium
You can go through odin and follow the tutorial on galaxys2root.com to unroot and ffash to stock GB. Link provided. The power button may have been stuck on yours but congratulations on getting it replaced. Just follow that tutorial and it will get you to stock 2.3.6 GB with no root or anything done, completely stock.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
Was messing around with the power button today pushing it 100 times and it finally turned on. Figures it would turn on when I'm getting a new one on Monday. Least I now backed up all my pix and contacts. Now point in keeping this one though, probably gunna happen again. Keeping the new one.
Wow another S2 down with a defective power button. I just had to send my out to get fixed for the same problem. This is become more common
So I received the phone today. Came stock with 4.0.4.
I plug it into my computer and kies gives me this
" Your device does not support software upgrading via Kies "
What the hell is that all about.
Oh and when I made my first call, I heard the people on the other end, but they did not hear me. I had to battery pull. It sucks because that was an issue with my phone on GB, figured it might have been fixed with ICS. Guess not. It really makes me sick that this happens. Sometimes I call someone and I hear nothing at all. Its happened with both GB and ICS. When the hell are they going to issue a fix for this crap.
First thing that I noticed and do not like is that when I use the keyboard, the phone vibrate heptic or w.e is not as strong as it was with GB. Also the voice on the other end sounds more muffled and more can like than GB. Not sure if thats the phone though
I keep reading that ICS stock verison UVLH1 ICS 4.0.4 is the Official tmobile and best ICS rom for stock
The phone they sent me is Baseband Version UVLI1.
I cant find anything on this version. What is it?
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
Time for upgrade maybe you can convince them to send you S3
I had to just replace my S2 with a new one from t-mo because I had tons of problems with my original phone once it upgraded to ICS. "Hanging" goodbye (didn't want to shut off unless you took out the battery, even after the buzz - which tells me that I may possibly had a stuck on/off switch too), lost the phone's internal driver so that the phone can be plugged into my PC, internet and processes became S-L-O-W-E-R than molasses, and more.
I'm assuming that, since all the S2's now have ICS on them shipping out, Samsung may have added a little additional processor power or something in order for it to run efficiently on ICS. All I know is that it runs a little faster than my original S2 did. And no problems - SO FAR.
P.S. UPS really does suck - they tried to deliver twice to my house, didn't leave one of those sticky things that said they were there, and I finally wound up going to a UPS service facility where I had to wait over one hour to get my new phone.
sparkie6point0 said:
I had to just replace my S2 with a new one from t-mo because I had tons of problems with my original phone once it upgraded to ICS. "Hanging" goodbye (didn't want to shut off unless you took out the battery, even after the buzz - which tells me that I may possibly had a stuck on/off switch too), lost the phone's internal driver so that the phone can be plugged into my PC, internet and processes became S-L-O-W-E-R than molasses, and more.
I'm assuming that, since all the S2's now have ICS on them shipping out, Samsung may have added a little additional processor power or something in order for it to run efficiently on ICS. All I know is that it runs a little faster than my original S2 did. And no problems - SO FAR.
P.S. UPS really does suck - they tried to deliver twice to my house, didn't leave one of those sticky things that said they were there, and I finally wound up going to a UPS service facility where I had to wait over one hour to get my new phone.
Click to expand...
Click to collapse
I am not really happy with it. Seems slower to me. Not as smooth. Still sometimes the person on the other line cant hear me, and vice versa with the battery pull, but I had that with my old phone and GB also. If I am going to have it either way though, id rather just stay smoother with GB.
What did your new one come with? Mine is UVLI1. Kernel 3.0.8