Hey guys, I had a Ls-980, and I loved it. Rooted with Slimkat roms, and TWRP. The screen cracked though, and I took it in to sprint to get it fixed. They fixed the screen, but afterwords the phone no longer boots entirely. I cant get into recovery. The phone boots, but quickly turns off. I am now on a Note 2, until they order the replacement. Do you guys think there is a fix for this, that might not be too hard, with a minimal bricking risk? Should I just let the G2 go and get a replacement and try not to ruin that one when rooting? any thoughts?
Have you tried getting into download mode after fully charging
Sent from my LG-LS980 using Tapatalk
I don't have the phone with me, but it recovery and download mode seemed to not boot into it. It seemed like I only had the option to boot into the rom, but that shut down right away.
Related
I think I might be in need of some warranty work, however before I ship my phone off I want to see if anyone else here is experiencing the same issue as me in the past and perhaps they found a fix thus avoiding the having to go back to stock n ship away for Samsung to say nothing is wrong with the phone or have them tell me the warranty is voided due to them somehow finding out ive modded the phone in the past.
Anyhow my issue is, my phone seems to have 'issues' with coming out of lock mode. I sometime have to hit the lock button up to 5 times to get the screen to come on, as with each press prior the screen will just flash (the old crt power down look) for a second and then go black, I thought it was my case, but nope even without the case it still has the issue. I am currently running on the stock rooted rom with Synergy v0.10 kernel, I have also gone to the stock rooted kernel with the same issues. Now this is a random occurrence, sometimes after the phone sits for a while locked it will act up, and then sometimes it will do it shortly after being locked. Its rather annoying and the issue has really only shown up over this past week.
Anyone else experience this? I hope my explanation makes sense!
Nope. Not experiencing any hang whatsoever with my lockscreen.
Hmm wonder if odining back to stock and starting allllll over again would help.... could be to many cwm flashes on this sucker haha, I remember my old sgs started to act up and do weird random things, then I odined it and it started to run normal again
yeah just odin it.. i shipped my phone last week to samsung anf called them just to confirm..and they said we will replace your motherboard and motherboards are not in stock currently so we will wait for 2 more days otherwise we will send you new phone .. byda way my phone was bricked.. i accidently disconnected my phone when flashing through odin
Sent from my Nexus S using XDA
Use no lock
Sent from my SGH-T989 using xda premium
No lock didnt work on my phone in the past, plus its not really the 'lock' feature, its more the powering screen off and powering the screen back on is where the issue is, I will try a Odin and start over from scratch and see how it goes. the annying part is the damn thing isnt consistent with doing it, knowing my luck id take it into telus and the stupid thing wouldnt act up.
Yeah ive had this issue doesn't happen with stock roms
Sent from my SGH-T989D using XDA
Think my phone is going back to telus, as I did the Odin flash that was posted up by Przekret, and now my phone is stuck in a boot cycle :S so perhaps I had posibly hardware failure that was just amplified with the odin stock flash :S boo!
Edit... Well it was stuck in a boot loop, now it wont even turn on, nor will it detect when being plugged into my laptop... Not good
I decided to ROOT my phone, which seemed to be sucessful, and then I attempted to install a Custom ROM (where the problem began). This ROM used the AROMA installer and all seemed to be going fine. I rebooted at the end. I wasn't watching my phone at this point because I'm used to reboots following ROM installs taking a while so I just ignored it a bit. When I looked back finally, the screen was off. I figured that it had just gone to sleep but I couldn't wake it up.
What's worse is that I cant get it to turn back on at all! I've tried pulling the batter, hard reset (Power + volume up and power + volume up + home key). Nothing. Is there any advice anyone can give me? What did I do wrong and is there a way to recover the device?
How much battery left you had before flashing?
Sent from my SGH-T999
lazarat said:
How much battery left you had before flashing?
Sent from my SGH-T999
Click to expand...
Click to collapse
I'm not 100% sure actually. was low when I started the root process but I did have the device plugged in the whole time though. Do you think that's the problem? I actually swapped my battery with my GF's battery (which was nearly fully charged) so I don't think its a "dead battery" issue. Any ideas on how I can get it back on? Doesn't even show the charging icon.
Plug it into Odin and see if anything comes up.
Sent from my SGH-T999 using xda premium
Yes your battery died in the process of flashing which sucks bwcause i do not know what are the consequences of it but seems bad since you cannot even get into download mode. Never flash with battery below 50%. Good thing is though that if the phone does not turn on at all then jist go to tmobilw store say left it overnight to charge when woke up was all black screen. Idk whats wrong with it. Get a replacement.
Sent from my SGH-T999
Pull the battery out for like 2-3 mins then let it charge for like 15 and try to get in download mode... If it does pop odin open and flash stock image. You can find it under the stickies in dev section.
Sent from my SGH-T999
I wasn't able to resolve the issue but I was able to take it back to the TMO store and just swap it for another one. The guy didn't ask too many questions. Crisis averted but it's made me hesitant to flash on this again so soon. I've rooted and flashed dozens of Android devices for myself and others over the years but this is the first time something like this has happened to me. Being careless I suppose. When I get my nerves back up, I'll be back.
Thanks for all the help you guys offered. I appreciate it.
Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??
oscarito619 said:
Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??
Click to expand...
Click to collapse
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.
gallaxxeess said:
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.
Click to expand...
Click to collapse
Yeah well people here are advised to send their bricked device to Samsung all the time because Samsung won't know the difference... I don't see how that is any different from what this guy is proposing...
Sent from my SGH-T989 using xda premium
It sounds like you have a stuck or broken power button. Try doing what the guy above said to do and after you return it to stock, send it to Samsung for a replacement.
If you have insurance on your phone just tell them you lost it, but you would have to pay the copay
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Think I just borked by AT&T Galaxy S3, and yes it is completely my fault. This is probably a dead end, buy I figured I'd ask as a last resort.
I've got a lot of experience rooting and flashing ROMS and flashing custom recoveries and was rushing a proceedure when the problem occurred. I was trying to flash the CWM touch recovery using the instructions here: http://forum.xda-developers.com/showthread.php?t=1739426
I tried to do all this through my phone using Terminal Emulator and typed in the portion "mmcblk0p18" one letter off from what I should have (I think I typed in "mmcblk0p08" ... sick sinking feeling my stomach right now). The code went through as I started to power down the phone as I was looking at the code I wrote. Noticed the mispelled line of code right as the screen was powering off. Now my phone is completely unresponsive, after I rebooted. The phone does not power on, cannot boot into recovery mode, and worst of all seemingly will not boot into download mode. I've had boot loops before and am familiar with how to traditionally boot into Download mode via POWER + Vol Down + Home Button and used Odin to flash a fix.
Are there any other options, short of taking it to a repair shop, that I can try? I'm guessing it's completely bricked, but I just wanted to see if there were any options I was missing that are worth trying.
About to start calling repair shops to see if they can take a look at it as well.
Warranty replacement. Just say you don't know why it won't turn on. I did this after dropping my rooted phone and they asked no questions.
On the phone now, I'll let you know if they're able to assist with troubleshooting or otherwise.
I did the same thing.... I had insurance through att reported the phone lost... I repeat lost not stolen.. Got a replacement in 2 days brand new white and used that to pull the stock rom and flash it to my old phone. The then turned around and sold the replacement phone
Sent from my SGH-I747M using xda premium
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Mphill46 said:
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I agree that it doesn't make sense. It's behaving almost as if the battery is just flat out dead. I have a spare battery, but when I tried that one it made no difference. I plugged the phone into a couple of different chargers while the AT&T rep was helping me troubleshoot and the charging light wouldn't turn on. The phone was not responding to anything at all, no matter what we tried.
They declared it hardware failure and are sending a replacement, as part of the original warranty. It did not have any physical damage, scratches, no water damage, etc.
Let this be a lesson to others: Be very very VERY careful with ADB and read your commands carefully. Those warnings about bricking your phone are real and shouldn't be taken lightly. I've rooted 6 devices and flashed what I'd estimate as over 60 ROMs over all my Android devices. I let my guard down and rushed things, and really my carelessness is all to blame at this point.
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app