Related
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
My friend's S2 is having the following issues:
The phone will not turn on (Darkside 3.6 ROM with DarksideX Kernel). The phone will show the Samsung logo, the Darkside X kernel flash and then it would shut off. It will then have a constant vibration ever 2 seconds or so.
I tried going into recovery mode to try and wipe all the caches, but the phone will not let me go into recovery mode at all. It will give me the constant vibration mentioned above.
I'm guessing the issue is being caused by Kernel crash so I tried going into download mode so I could try and flash a new Kernel via Odin, but once I get into the warning screen and I press volume up to go to download mode, the phone go into download mode for a split second before shutting off and go into the constant vibration mode again.
Any idea what's going on? Or did anyone have had these problems in the past?
I flashed her phone a few months ago and it's been working flawlessly until last night. So I know it's not a bad flash. I'm getting frustrated here because I can't keep the phone turned on long enough to re-flash or to ODIN or to do anything.
Any help is appreciated!
Try letting it sit for a couple of minutes, the battery might have drained too much. This happened to me before I hope this helps, every once in a while when it turns off and on try to boot into recovery and just reboot back out to restart the phone to a normal boot.
Sent from my SGH-T989 using xda premium
Daddy_617 said:
Try letting it sit for a couple of minutes, the battery might have drained too much. This happened to me before I hope this helps, every once in a while when it turns off and on try to boot into recovery and just reboot back out to restart the phone to a normal boot.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried letting the phone sit for hours.
I've tried unplugging and then plugging back in and not touching it for hours.
I've tried charging the battery to 100% (with my phone) and then putting it in my friend's phone.
Nothing's working
Sounds like the power button may be stuck, or a hardware failure.
xcrazydx said:
Sounds like the power button may be stuck, or a hardware failure.
Click to expand...
Click to collapse
Power button is definitely not stuck.
I'm worried that it's hardware failure, but the phone is still under warranty and if that's the case, I'm trying to get this back to stock so I can claim the warranty.
belly1026 said:
Power button is definitely not stuck.
I'm worried that it's hardware failure, but the phone is still under warranty and if that's the case, I'm trying to get this back to stock so I can claim the warranty.
Click to expand...
Click to collapse
This happened to a couple people a while ago. One had some lint or corrosion on the battery contacts, they cleaned it, and that fixed it.
skrambled said:
BOOM!!!! I fixed it!!!!!!!!!!!!!!!!!!!!!!!!!
I knew it was a battery or battery connection issue. I removed the back plating and noticed that there was some lint on the inside that was bridging the battery connections (I don't know the tech terms, sorry).
Used some air duster and blew it out. Reassembled and it is working like a charm now.
(If Joosty is reading this, I did a factory data reset--including USB storage--immediately so no worries about any personal data you may have had on there.)
EDIT: For anyone trying this fix just thought I'd mention that I used a 1/16 screwdriver to get the screws out and that getting the cover off was a little tricky--I thought I was going to break the plastic when trying to pop it off. Also, the volume rocker button falls right out so make sure to watch for that...
Click to expand...
Click to collapse
From this thread
http://forum.xda-developers.com/showthread.php?t=1546174
xcrazydx said:
This happened to a couple people a while ago. One had some lint or corrosion on the battery contacts, they cleaned it, and that fixed it.
From this thread
http://forum.xda-developers.com/showthread.php?t=1546174
Click to expand...
Click to collapse
Tried doing that just now, didn't work
Thanks for the link though. I'm wondering if that jtag service could repair this. Nobody on that thread seemed to actually tried that method.
belly1026 said:
Tried doing that just now, didn't work
Thanks for the link though. I'm wondering if that jtag service could repair this. Nobody on that thread seemed to actually tried that method.
Click to expand...
Click to collapse
I would bet he can fix it, whether it be a hardware or software issue. Mobiletechvideos does good work from what I hear.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
dongle
bought 3.00 usb dongle on Ebay, that forced mine brick into download mode. Reflashed through Odin
Try to just put the battery in and hold the volume up and down button while it keeps booting up and down with the vibration thingy going on. It usually just boots into recovery might take a few tries just be patient and hold down the volume up and down buttons
Sent from my SGH-T989 using xda premium
Happened to me when I put a née battery in while the phone rebooted into recovery. I ref lashed recovery and let the battery recharge bam it worked.
Sent from my SGH-T989 using xda premium
Daddy_617 said:
Try to just put the battery in and hold the volume up and down button while it keeps booting up and down with the vibration thingy going on. It usually just boots into recovery might take a few tries just be patient and hold down the volume up and down buttons
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but I've tried this and didn't work. I was pressing the vol up and down button so long for so many times, my fingers started to hurt lol.
Madblaster6 said:
Happened to me when I put a née battery in while the phone rebooted into recovery. I ref lashed recovery and let the battery recharge bam it worked.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Battery is 100% charged and the phone will not boot into recovery
Damn... I guess you should try a jig, that's the only thing I have in mind. Sometimes you need to take everything out such as the sim card, Sdcard etc... let sit for 5 minutes then try to put the battery in to go into download mode. Last time I was getting so frustrated and noticed the USB cable was still in and that was the reason I couldn't get into recovery I was so heated! Haha anyways I hope this helps.
Sent from my SGH-T989 using xda premium
Daddy_617 said:
Damn... I guess you should try a jig, that's the only thing I have in mind. Sometimes you need to take everything out such as the sim card, Sdcard etc... let sit for 5 minutes then try to put the battery in to go into download mode. Last time I was getting so frustrated and noticed the USB cable was still in and that was the reason I couldn't get into recovery I was so heated! Haha anyways I hope this helps.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, I'm ordering a jig and hoping that it would force my phone to download mode and keep it on long enough for me to flash new kernel or stock rom.
But I did try letting the phone sit overnight before attempting anything to it with no results. If the jig doesn't work, I'm just going to send it in for the JTAG service. I e-mailed them and they said they would be able to fix it.
What??
belly1026 said:
Yeah, I'm ordering a jig and hoping that it would force my phone to download mode and keep it on long enough for me to flash new kernel or stock rom.
But I did try letting the phone sit overnight before attempting anything to it with no results. If the jig doesn't work, I'm just going to send it in for the JTAG service. I e-mailed them and they said they would be able to fix it.
Click to expand...
Click to collapse
This does not make sense. First, were you able to go into download mode using Vol up+down and USB cable plugged in to computer? If you can, then press vol up to continue and start ODIN on your desktop, flash the stock ROM (download from the Galaxy S2 Android Dev threads) and see if that works.
To me this does not sound like a hardware but more like a corrupt software issue.
I hope you just don't waste your money for nothing here.
belly1026 said:
once I get into the warning screen and I press volume up to go to download mode, the phone go into download mode for a split second before shutting off and go into the constant vibration mode again.
Click to expand...
Click to collapse
razormight said:
This does not make sense. First, were you able to go into download mode using Vol up+down and USB cable plugged in to computer? If you can, then press vol up to continue and start ODIN on your desktop, flash the stock ROM (download from the Galaxy S2 Android Dev threads) and see if that works.
To me this does not sound like a hardware but more like a corrupt software issue.
I hope you just don't waste your money for nothing here.
Click to expand...
Click to collapse
As I'd mentioned in my first post, I'm able to go into download mode, but I'm unable to keep the phone turned on for me to do anything with ODIN.
I'm hoping that by using the JIG, it will somehow force my phone to stay in download mode long enough for me to flash.
That happened when my phone's Seidio battery had some liquid spilled on it. It did the same exact thing but I used my stock battery to boot it, let the phone run from the charger and replaced the battery. That fixed it for me. Try using another battery.
aranurea said:
That happened when my phone's Seidio battery had some liquid spilled on it. It did the same exact thing but I used my stock battery to boot it, let the phone run from the charger and replaced the battery. That fixed it for me. Try using another battery.
Click to expand...
Click to collapse
I've used three different batteries. No go.
Thanks for the suggestion though.
No problem. If your gonna return it, either brick it or stock it
Sent from my Ice Cream Sandwiched Darkside T989.
did you manage to fix it?
I have the same problem! please help
I've searched & searched thru XDA without any luck or finding someone with a similar situation.
My GNEX is unlocked, rooted & running AOKP 36.
I hung up the phone after a call...locked it...put it in my pocket...took it out a few minutes later and the phone would not turn on. My battery was over 50%, so i thought i pocket-powered the phone down.
The phone does not boot into any mode. I've tried them all. It is not recognized by my Mac or PC. Here are the things i've done so far: Battery pull. Charge overnight. Removed battery overnight. I bought a new battery & i'm still having the same problem.
Any ideas before i call Verizon and take the loss? I would really like to recover my pictures & videos.
Thanks in advance.
So you have tried to boot into recovery by holding down power and the volume buttons?
If not try this to get to recovery to do a restore.
http://www.youtube.com/watch?v=1SDd1DZUs-M
If you tried this, then you might need to send it in.
Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.
falotm said:
Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.
Click to expand...
Click to collapse
Do you have another battery or friend with a gnex? My girls died completely while plugged in over night. I got another battery and it fired up.
Needless to say a clean install was the next step.
Sent from my GT-I9300 using Tapatalk 2
Also hold down power button for awhile. And also try.with a different battery.
...
I bought a new battery from Verizon and tried it, but its still unresponsive. I charged both batteries overnight and nothing happens.
I've held all buttons for several minutes with both batteries, but nothing happens. It wont boot and it won't boot into recovery/bootloader/hard reset menu, etc (android with stomach open LOL)
On a few occasions, when i connect to my PC, it says new hardware detected OMAP 4440 (or something like that) & asks to install drivers. I have the Gnex toolkit, but the program does NOT detect my phone.
Thanks for the replies.
This happened to my fiance's vzw gnex. She was on stock though. Just surfing the web and it turned off. Dead as can be. She took it back and they gave her a new one.
Sent from my Xoom using xda premium
Oh.. Man you lost the bootloader.... If you have warranty go ask for a replacement, it's a pain trying to get the phone back up..
They won't know the phone its unlocked since it won't turn on
Nexus Cm9 + Franco
http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
Try this?
Can't hurt...
My Nexus is from Verizon & the tutorial you linked is for the GSM version. Do you think it matters?
I will still give it a shot. Thanks!
Did you check the pin area where the battery connects? Are the pins in good condition or any small foreign object around them?
If you're careful you can *maybe* odin it back to stock (you've already lost the pics tho).
Look in the dev area for any odin threads.....links to files and stuff are in there.
Jubakuba said:
Try this?
Can't hurt...
Click to expand...
Click to collapse
Thanks for the link. I installed the drivers, phone was detected, ran thru the program, but it failed at the very end. I think its because my phone is i515 & not GSM version.
I've given up hope. Time to get a replacement. I hope it never boots and they don't find out its unlocked & rooted.
I appreciate everyone's input.
Thanks!
a friend mine has a similar problem..
phone died without reason
where i can download the drives that you made mention?
i'll suggest him to try that .bat file
Now before you say its not hard bricked, just use odin/download mode bla bla bla, know that I do know what I am talking about. I was odining WITH PARTION ON to go from mtd to bml and my computer power cut out. Now I can't turn my phone on OR get into download mode . I looked into th e unbrickable mod but apparently that's just more of an untested thing (at least for the epic). That pretty much means I can only get a new phone (probably get the note 2). However I was wondering for the time being if I turned this into sprint, assuming they don't know whats wrong with it and i play dumb, Will they just replace my phone cause I have tep? Or will i have to make an assurion claim? Or should i use an old crap phone for the next 3 weeks until i can get my gnote 2?
A month or so ago, I thought I had hard bricked from an odin disconnect. I searched & tried EVERYTHING and couldn't get it to DL mode. Somewhere in XDA I stumbled on a suggested unbrick method that amazingly worked. I wish I could find that post & hit Thanks.
- Close the keyboard
- Put the battery in
- Press the power button TWICE with short presses
- Plug in your USB cable
- Use 1+Power to fire up DL Mode
- Voila!!
I know it sounds overly simple, but it worked for me. I was shocked.
Al
Sent from my SPH-D700 using xda app-developers app
arschend said:
A month or so ago, I thought I had hard bricked from an odin disconnect. I searched & tried EVERYTHING and couldn't get it to DL mode. Somewhere in XDA I stumbled on a suggested unbrick method that amazingly worked. I wish I could find that post & hit Thanks.
- Close the keyboard
- Put the battery in
- Press the power button TWICE with short presses
- Plug in your USB cable
- Use 1+Power to fire up DL Mode
- Voila!!
I know it sounds overly simple, but it worked for me. I was shocked.
Al
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I don't know why, but they seemed to work...thank you!
Well, I guess my memory isn't so hot. I found the original post here. The instruction should have been to press the power button twice with the the battery OUT. I'm glad it worked for you anyway.:laugh:
Al
arschend said:
Well, I guess my memory isn't so hot. I found the original post here. The instruction should have been to press the power button twice with the the battery OUT. I'm glad it worked for you anyway.:laugh:
Al
Click to expand...
Click to collapse
My friend told me it had something to do with waiting for the static something or other to clear with the battery out...so it may not have been your method. Just the two hours i got frusturated and didn't do anything with it and the battery out.
samdsox said:
My friend told me it had something to do with waiting for the static something or other to clear with the battery out...so it may not have been your method. Just the two hours i got frusturated and didn't do anything with it and the battery out.
Click to expand...
Click to collapse
this drains the power out of the phone board, you could also unplug the battery and plug the phone into a WALL charger while holding power and 1, then after you get into download mode plug the battery in and take it to the usb for odin.
samdsox said:
Now before you say its not hard bricked, just use odin/download mode bla bla bla, know that I do know what I am talking about. I was odining WITH PARTION ON to go from mtd to bml and my computer power cut out. Now I can't turn my phone on OR get into download mode . I looked into th e unbrickable mod but apparently that's just more of an untested thing (at least for the epic). That pretty much means I can only get a new phone (probably get the note 2). However I was wondering for the time being if I turned this into sprint, assuming they don't know whats wrong with it and i play dumb, Will they just replace my phone cause I have tep? Or will i have to make an assurion claim? Or should i use an old crap phone for the next 3 weeks until i can get my gnote 2?
Click to expand...
Click to collapse
If its been 30 days you can go back to any sprint store and they have to give you a new one. I've done it. not for the s3 but for other phones. Thats considered a manufacturers defect.
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