Related
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
phone wont boot at all after install. wont even go into download mode.
phone worked perfectly when i was running beastmod 3.0 i believe. i stayed inactive ever since.. i made sure i could get into download right before i went ahead to the jedi mind trick update. like i said, everything worked perfectly. tested out all button combos for recovery and download mode (even did the pulling the battery and plugging the usb method) with success before i updated. yes phone was on 100% battery . it was on the charger the whole night.
i logged back on because i felt like updating and read about Jedi Mind Trick. installed TWRP recovery as well a few days ago. i wiped everything of course, flashed, repaired , reboot. I got a black screen for awhile and let it sit for 30min. no response, so i pulled the battery and tried to turn on. phone wouldnt turn on so i tried to get into download mode and failed. phone is completely unresponsive.
what to do? i'm just stumped now. i was inactive, but by no means am i new to this.
Are you sure your battery has a good charge?
brian_v3ntura said:
phone wont boot at all after install. wont even go into download mode.
phone worked perfectly when i was running beastmod 3.0 i believe. i stayed inactive ever since.. i made sure i could get into download right before i went ahead to the jedi mind trick update. like i said, everything worked perfectly. tested out all button combos for recovery and download mode (even did the pulling the battery and plugging the usb method) with success before i updated. yes phone was on 100% battery . it was on the charger the whole night.
i logged back on because i felt like updating and read about Jedi Mind Trick. installed TWRP recovery as well a few days ago. i wiped everything of course, flashed, repaired , reboot. I got a black screen for awhile and let it sit for 30min. no response, so i pulled the battery and tried to turn on. phone wouldnt turn on so i tried to get into download mode and failed. phone is completely unresponsive.
what to do? i'm just stumped now. i was inactive, but by no means am i new to this.
Click to expand...
Click to collapse
I see by no means are you a rookie but I will ask have you tried to plug your phone in to your pc and see if it makes a noise and recognizes it. Honestly I would assume prior to posting you probably tried everything so it may be unfortunate but you may have to send to JTAG or go through insurance.
Cant see a rom doing that to your phone? Unless you had some hardware failure
Have you tried using a usb jig to force it into download mode?
davwman said:
Are you sure your battery has a good charge?
Click to expand...
Click to collapse
yep. battery was just fine. never had had a problem. even popped in my spare and dad's battery to make sure it wasnt a battery related issue.
CMDann said:
Have you tried using a usb jig to force it into download mode?
Click to expand...
Click to collapse
yes. i made my own actually. it was the first thing i used to make sure i could get into download mode,with success, before the flashing process.
playya said:
I see by no means are you a rookie but I will ask have you tried to plug your phone in to your pc and see if it makes a noise and recognizes it. Honestly I would assume prior to posting you probably tried everything so it may be unfortunate but you may have to send to JTAG or go through insurance.
Cant see a rom doing that to your phone? Unless you had some hardware failure
Click to expand...
Click to collapse
after flashing:
1) i did plug into 2 laptops(windows 7) and a 2 desktop(vista and xp). "tries" to install the drivers and then makes the fail noise.
2) tried to use the SGS2 toolkit as well.
prior to flashing:
1) phone mounted successfully to 1 laptop and 1 desktop. thats all i tried it on. i used my laptop to transfer the flash zips and my desktop to back up my internal memory since i havent done it in awhile.
2) everything just worked. my only gripe was that my phone was still on gingerbread and decided to update to to ICS
i'm just puzzled myself. i did try everything that i could think of to at least get the phone to turn on somehow. i even went back to sleep and put the phone on the charger hoping the phone would just magically turn on itself >_<
i know i've been super inactive for awhile, but it only took me a few of days to get myself back up to speed and catch up on the new information.
Also would like to add that i used 3 samsung micro usb cords(2x sgs2 and vibrant),jig,2htc cords(hd3 and mytouch 4g) and even my old nokia micro usb. No success but at last the laptop is detecting the phone when trying to install drivers and then fail.
I know i did not download thw wrong rom either its not like i go off to other phone sub-forums to look for stuff.
Chalk this up to bad luck and move on. Its not the ROM. Period. Like pmtr3 said, 20,000 downloads plus, and your the first one to say this happened. Sorry to hear about your phone.
Sent from JMT Goodness
Have you tried pulling the phones battery out sim and micro sdcard... then hold the two volume buttons then olug in the usb and then place the battery while still holding the volume buttons? (Open up odin before trying)
Sent from my SGH-T989 using xda app-developers app
LoopDoGG79 said:
Chalk this up to bad luck and move on. Its not the ROM. Period. Like pmtr3 said, 20,000 downloads plus, and your the first one to say this happened. Sorry to hear about your phone.
Sent from JMT Goodness
Click to expand...
Click to collapse
i have no clue what happened. maybe some kind of freak hardware failure. i used to be so into flashing,but decided to use my phone as a phone instead of always flashing.
i did call TMo for a warranty replacement, but the SGS2 is supposedly on back order -____- they recommended an alternative device,but not details yet until they get back to me.
this isnt my first SGS2. i got mine during TMo's firesale on Nov. 19th. 3 days later, i exchanged under the 14day grace period it due to horrible data drops and robotic voice. The phone was stock at the time. Data drops made it impossible to download-on-the-go for whatever the professors assigned . 2nd one worked like a charm.
phreshjoker said:
Have you tried pulling the phones battery out sim and micro sdcard... then hold the two volume buttons then olug in the usb and then place the battery while still holding the volume buttons? (Open up odin before trying)
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
yes....i'm cutting my loses and doing a warranty exchange. Hopefully an SGS3 due to having 2 SGS2's. Usually,they will upgrade to the next device if your current device is not available and you had 2 replacements.
i'm trying to find my Good ol' G1 that never really failed me. i used to like using it from time to time whenever i had my vibrant just for nostalgia purposes.
Got a new rom yesterday. Was working fine, phone was charging fine. Today After using the phone for about 10 hours it just died. I didn't do anything new such as download any new apks or flash any thing. But it just died. When I hold power it can go to the samsung screen and just die, when I hold power vol down and home it goes to the download screen for like 5 sec and dies, when I go to cwm it dies in a short time as well.
Now I have it wall charging and I'm getting no LED light, so I'm worried!!!
Any recommendations?
ihugyou said:
Got a new rom yesterday. Was working fine, phone was charging fine. Today After using the phone for about 10 hours it just died. I didn't do anything new such as download any new apks or flash any thing. But it just died. When I hold power it can go to the samsung screen and just die, when I hold power vol down and home it goes to the download screen for like 5 sec and dies, when I go to cwm it dies in a short time as well.
Now I have it wall charging and I'm getting no LED light, so I'm worried!!!
Any recommendations?
Click to expand...
Click to collapse
Depending on what rom. Some don't play well with the led. Also you have to make sure it's checked in the settings.
Have you tried turning it on while it's charging?
Sent from a planet far far away.
Speedin07si said:
Depending on what rom. Some don't play well with the led. Also you have to make sure it's checked in the settings.
Have you tried turning it on while it's charging?
Sent from a planet far far away.
Click to expand...
Click to collapse
Some times it turns on while charging, but will just turn back off.
I'm using This Rom
Edit* the led normally turns on while charging...im not that much of a newb, i'm just thinking I might have bricked my phone.. It's strange that it happened a whole day after I flashed the rom though..
ihugyou said:
Some times it turns on while charging, but will just turn back off.
I'm using This Rom
Edit* the led normally turns on while charging...im not that much of a newb, i'm just thinking I might have bricked my phone.. It's strange that it happened a whole day after I flashed the rom though..
Click to expand...
Click to collapse
If it's turning on its not bricked at all. It's a charging issue, take the back cover off make sure the battery is making good contact with its connection points. Close it back up and plug it in and let it charge for 30 tp 40 minutes check if it comes on. Sometimes when the battery dies completely it takes some time to get some charge into it. The booting up process uses a ton of power, once on make sure you leave it plugged in and charge fully.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Ok because the one time it actually came on it said it was at 70%, which I'm assuming is totally incorrect. So I will now plug it into the wall and let it charge for quite a while, I jsut think it's weird that the light never comes on (which it normally does).....
thanks for the tips dudes!
I had the same issue as you, the phone will turn on and then most of the time it will turn off during the boot process. If I turn it on in Download or Recovery mode it'll stay on for a couple seconds and then turn off. At best, it'll turn on, get to the home screen and then after a couple seconds of usage it'll turn right back off. Also, did you notice that before the phone turned off it would lock itself and unlock itself possibly showing the power menu to like reboot or turn off and such? That made me think it might've been the power button but I'm not positive.
I could not get a fix for this at all, I attempted everything I could think of. I ran the phone in safe mode, it still did it. I ran a different rom, still had the issue. Ran stock rooted, same problem. Ran stock non-rooted, problem still there. In fact, I talked to Samsung yesterday and I sent it in for the warranty as I didn't have carrier insurance. One thing happened was that while I was in stock rooted, I decided to underclock the phone to see if anything would occur and I noticed something interesting. The phone still had the problem but it would stay on for longer periods of time. This made me think maybe the phone was overheating or the CPU was shutting itself off for some reason. As far as I know from my testing I can say that the problem was hardware related. I should also note that this thing happened to me once a couple months ago but I flashed the stock tar through Odin and the problem disappeared for a short while but it came back and continually did so.
Oh, I also figured out how to get it on for a short period of time. To get it to work temporarily, first make sure the phone is charged a good amount. Plug it in for a couple hours. Next, take the battery out of the phone for a couple hours and remove the phone from the charger, the longer you keep the battery out the better. Now, put the battery back in, and attempt to turn on the phone, if it doesn't work try again a couple times. The phone should eventually turn on and stay on for a short period of time (anywhere between 1 or 2 min and 30 minutes). From here just back up anything you need to and if you are rooted and want to turn it in for warranty or whatnot you'll need to clear the evidence that the phone was rooted.
First off, if you are rooted you'll want to clear your flash counter. Download the Triangle Away apk and put it in the microSD so you can access it easily when the phone turns on. Follow the instructions on how to turn the phone on from above. After it turns on, quickly Run Triangle away and click on the option that says something along the lines of "reset flash counter". Once that is done, turn off the phone and take out the battery so that you can turn it on for the next step.
Next, you will need to download Odin (I believe it is Windows only, if you don't have Windows I'm not sure what you can do as I haven't had to unroot on anything other than my PC) and the stock tar file so that you can return the phone to complete stock. Once you have done this, run Odin and click on the PDA tab and browse for the stock tar. Let Odin do it's thing and once you see it's ready to flash the file, put the battery back in and turn the phone back on in download mode. Plug the phone in and let it sit there for a couple seconds to make sure it won't turn off during the flashing process. If it does turn off try again. When you can get it to stay on for over 30 seconds click on the Start in Odin and start the flash. If it stays on for a while but turns off while flashing, the boot will be corrupt and you will have to try again til you can get it to stay on long enough. Note that if the boot is corrupt you won't be able to turn the phone on to anything other than Download mode and possibly recovery. Once you complete the flashing process the phone should auto-boot and it SHOULD work. That means that the phone should turn on with no problems but it may or may not turn itself off. If it doesn't turn itself off go ahead and use it for a while, but if your situation is like mine the problem will come back eventually. But at least now you can turn it in to Samsung for warranty or whatnot.
And if worst comes to worst you can completely f up the phone while it's flashing in Odin, have a corrupt boot img and then call in saying it doesn't work.
Of course all of this is only if you're having a similar problem to me. Like I said, I sent it in yesterday so I'll post updates as I get them. Hopefully they'll fix it for me!
Nice write-up :good:
@OP If you can't get the unroot process to work (like the guy above me said) just flash a rom made for the international S3, thats a sure-fire way to brick you phone
Sent from my PG06100
CNexus said:
Nice write-up :good:
@OP If you can't get the unroot process to work (like the guy above me said) just flash a rom made for the international S3, thats a sure-fire way to brick you phone
Sent from my PG06100
Click to expand...
Click to collapse
It was quite a nice wall of text. And oh yes, bricking your phone is a great idea! Say it was an OTA or something haha
Ok so SG3 should have a warranty even though I don't have carrier insurance?
And did you try replacing the battery?
ihugyou said:
Ok so SG3 should have a warranty even though I don't have carrier insurance?
And did you try replacing the battery?
Click to expand...
Click to collapse
Correct, there is a 1 year warranty on the phone and 6 months on the battery and charger. And yes I switched with another OEM battery and the issue persisted. However, the S3 I switched the batteries with continued to work so I believe it is the phone itself and not the battery or charger. It might be the connector points but my phone did strange things before turning off. It may be a combination of many things as well.
porshce2 said:
Correct, there is a 1 year warranty on the phone and 6 months on the battery and charger. And yes I switched with another OEM battery and the issue persisted. However, the S3 I switched the batteries with continued to work so I believe it is the phone itself and not the battery or charger. It might be the connector points but my phone did strange things before turning off. It may be a combination of many things as well.
Click to expand...
Click to collapse
Where exactly did you take your phone to return it? The samsung people are giving me a hard time it seems.
ihugyou said:
Where exactly did you take your phone to return it? The samsung people are giving me a hard time it seems.
Click to expand...
Click to collapse
I requested a Repair Service. You can contact them at 1-888-987-4357 and request the service there. They'll send you a UPS label and give you an RMA number. I tried to do it through the site but it didn't work so your best bet is to call them there. It's very simple to do it if your phone is already registered. Otherwise you'll have to give them the HEX number I believe. It's under your battery so just have that ready.
porshce2 said:
I requested a Repair Service. You can contact them at 1-888-987-4357 and request the service there. They'll send you a UPS label and give you an RMA number. I tried to do it through the site but it didn't work so your best bet is to call them there. It's very simple to do it if your phone is already registered. Otherwise you'll have to give them the HEX number I believe. It's under your battery so just have that ready.
Click to expand...
Click to collapse
Ok currently i have my phone running amazingly, re rooted, and installed moar morphology, I'm gonna give this some time and see what happens.. if it dies again i'm bricking it for good and returning it.
I really appreciate your help!
ihugyou said:
Ok currently i have my phone running amazingly, re rooted, and installed moar morphology, I'm gonna give this some time and see what happens.. if it dies again i'm bricking it for good and returning it.
I really appreciate your help!
Click to expand...
Click to collapse
Well if it does happen again, don't brick it unless you can't get it to turn on for long enough to flash stock. Hopefully it'll still be under warranty if it does happen again. And no problem! Good luck!:good:
porshce2 said:
Well if it does happen again, don't brick it unless you can't get it to turn on for long enough to flash stock. Hopefully it'll still be under warranty if it does happen again. And no problem! Good luck!:good:
Click to expand...
Click to collapse
This phone is giving me some epic ****in stress, can't load a rom, can revert to stock, but how boring is that... i've tried flashing at least 3 roms so far, this is taking forever, it just sits at the samsung galaxy screen now or reboots to recovery lol wtf ****ing phone
ihugyou said:
This phone is giving me some epic ****in stress, can't load a rom, can revert to stock, but how boring is that... i've tried flashing at least 3 roms so far, this is taking forever, it just sits at the samsung galaxy screen now or reboots to recovery lol wtf ****ing phone
Click to expand...
Click to collapse
If think you need to take a deep breath and relax. Try doing some more reading, it sounds like your missing a step somewhere. There's something which may be insignificant but your missing it.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hey guys. Bit rusty on this phone as I have been on the M8 for a while but my wife uses it. Her phone is stock rooted (Digiblur's rom I think.) and today after having the phone charging over night she went to turn it on and it got stuck on the Samsung logo screen. I don't have the phone near me at the moment but can you guys refresh my memory and advise the best steps to take? Pretty sure the phone has TWRP recovery but I forgot how to manually access it (if that's even the right course of action.
Not a single person who knows what to do or cares enough to point me in the right direction
Damn man you posted 8 hrs ago. You expect someone to just jump out and fix your issue asap? Give people a chance and you might get help.
My first guess would be battery. Plug phone to wall and see if it boots fully. If it does unplug it and it will most likely shut down or crash. You should be able to boot into recovery without being plugged in since it requires much less power to run. This device has come to that point in its life span where the battery just gives up. I bet if you ask your wife she will probably have noticed that charges don't last as long either.
Sent from my SPH-L900 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?p=55712636
Check this out worked for me. I would deff check battery first but if that fails this could help you. I know when i wasnt rooted on stock rom the phone had an error in recovery saying efs folder couldnt mount. After rooting the stock rom with a custom recovery, the error didnt show up but was still present.