So, I've downloaded Odin, the tar file, and anything else necessary to root, unroot, unbrick phone, etc.... I've read tons of forums and followed some I trusted very thoroughly. The problem began with my screen just suddenly going blank. This was almost two weeks ago now. Verizon has been of no help, AS USUAL.... the phone is only 3 months old, and Samsung offers no support either.
I've gotten the screen and phone to come on twice since, and that was the day of and right after it occurred. I thought I finally had it fixed after doing all of the steps in Odin last night, but the screen is still black. The other lights come on, and I can hear notifications, etc coming through but I can't see anything. I'm beyond stressed out.
If anyone can finally help me work through this, I would great appreciate it!!
Thanks so much in advance
Sorry, meant to delete this reply. I'd be happy if the mods did so x)
Related
Hello there,
I'm by no means an expert with mobile phones, but was recently given a C600 and having done some research on the net managed to unlock the phone myself.
However, although the phone was working fine with an O2 prepay sim card for the past few weeks, it has now decided to have what can only be described as a 'fit' every time i try to use it.
Half the time the three colured screen comes up when i turn it on, which says tornado, and a series of numbers, and then when i can get the phone switched on properly, half the time some of the buttons refuse to work, and the other half the phone will decide to flip between the earpiece volume setting screen, the camera, and the voice command thingy, when all i am trying to do is to text my mate to see if he wants to go for a beer!
Needless to say i haven't had a beer for the last two days, and am a little annoyed about being constantly outwitted by a mobile phone, so i decided to come to the experts for help.
Thanks to anyone who can help me resolve this issue!!
thanks guys, i clearly came to the right place here!
great.
what rom did you install on your tornado?
pabs1980 said:
thanks guys, i clearly came to the right place here!
great.
Click to expand...
Click to collapse
Wow you waited whole hour and a half before you gave up to wait for an answer, LOL.
PS
Your problem is cammera button - its half stuck so you need to clean it.
gr8 said:
what rom did you install on your tornado?
Click to expand...
Click to collapse
didn't change the rom at all as i heard that the new one was no good, its as it came out of the factory...
however, the toggle button is now not responding at all as with many other c600s from what i can tell on the net, so i may have to install the new rom anyway and hope that solves the problem.
i have a feeling that i will have to go through the entire process of unlocking the phone again when i have installed the new rom also, i'm starting to wonder if it is worth it....but i do really like the phone so it would be a shame to give up
thanks a lot for the help, if anyone else can help please post...
thanks
bllohin said:
Wow you waited whole hour and a half before you gave up to wait for an answer, LOL.
PS
Your problem is cammera button - its half stuck so you need to clean it.
Click to expand...
Click to collapse
25 and a half hours, but sorry for the impatience its just very frustrating to not be able to use a phone when i have no spare.
i'm pretty sure the problem runs a little deeper than the camera button but i'll give it a try.
thanks
Hello, everyone.
Ok I'll explain the situation, then explain how it might of happened.
My phone will not turn on. It is stuck at the white at&t screen.
How It Happened:
I went out camping with family. We decided to go boating, No I didn't dunk the phone in lake water. I was listening to music on the boat, I noticed that an error message kept coming up. It said something along the lines of "com.android.phone has stopped unexpectedly, please try again." I would get this message every other second. So I booted the phone into clockwork recovery, hoping to recover an old back up of my system. It didn't work, I got some other error message saying it couldn't recover. Being desperate, I was like, "I'll just flash a different ROM!" I tried flashing cognition. It said it installed correctly. I was stoked! I rebooted my phone. I noticed it still showed the cyanogenmod 7 boot animation, so of course it didn't flash the other ROM. I decided to reboot my phone again. This time instead of turning all the way on, it stopped at the cyanogenmod animation, then restarted. It looks as if, right before it would restart it looked like a "loading screen" in clockwork recovery. It rebooted continually for the next 10 minutes until I took the battery out. I then tried to recover the phone again. Then I rebooted my phone, but then it froze at the at&t white screen. I left it like that for around 20 minutes. As we were coming back to the dock, I decided that I had enough messing with it and turned it off.
Any ideas. Did I do what they call "Bricking" and if so, what can I do to fix it?
And if not what do you think I did?
Thanks for help. I am getting a new phone in 2 days.
Btw, I am running through AT&T, and I own a sumsung captivate.
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
DanBroChill said:
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
Click to expand...
Click to collapse
No, I got Odin3. Thanks, I got it back to stock. I got my new Cappy today. I'm sending my old one to AT&T and all that. Thanks anyways.
Hello, I have pretty solid belief after trying to fix my phone for 3 days now that its bricked badly. I was in the process of loading a new rom and in the process of doing so a breaker in our house went out and the power in my room turned off and so did my computer in the process of putting a new rom in.
So the first thing it did was show a phone--/!\--computer symbol, and I found a few ppl with similar problems and I tried to pull battery and go into download mode by holding down volume + and volume - and put the battery in after a few seconds and then usb. No luck
I then tried to go through the other solution of downloading unbrickable infuse mod and setting that up but once it started talking about soldering stuff I was lost and I scraped that idea. I tried some small other stuff like leaving the battery out of it well I went to work. come home still no luck. Finally I tried the "well its pretty much dead as it lets try this." and I tried to flash GTG's ultimate unbrick to my phone... and I first I thought it worked.. it found my phone, and everything went smooth then after that my phone stopped working completely. No power, no logo, no sound, not even seen by my computer.
Any help is appreciated i've been trying to find and rummage through as many threads as possible and use them to help, but I'm at a loss. Going to continue but any advice would be helpful.
I'm an avid follower of this site and forum, and have had this phone the day it released. Any help is appreciated thank you in advance ^_^
good morning bump... ^_^
=\ Really need help here, Ive been lurking xda for a long time, and just haven't posted but I really would appreciate help >.<
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Disable Ripple Effect
CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
Try disabling the ripple effect in your lockscreen settings. That is a known issue with any lockscreen other than the stock one.
Seriously a new version of MOAR? Dang it seems like every time I downloaded the new version they're putting up a new one. Which isn't a bad thing but still. Did they say this on the thread?
CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
What kernel are you using?
airmaxx23 said:
What kernel are you using?
Click to expand...
Click to collapse
Where can I find the kernel information?
So with a couple tests, I found that the phone tends to soft reset twice if I enter the wrong swipe password, not sure why it has to freak out like that but it's annoying. That's the only time it's been resetting now. The other issue, screen turning back on after I turn it off with the power button, is still persisting but isn't happening in any discernable pattern.
Okay so I found the kernel information, it says
"3.0.31-1152558
[email protected] #1"
People in the MOAR forum (Verizon S3) have had problems on the reboots with the Blackberry lockscreen, but I'm on Rotary so that doesn't help.
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Wickidmasshole said:
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Click to expand...
Click to collapse
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
hyelton said:
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
wait- did you mean select board DL?
Wickidmasshole said:
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
Click to expand...
Click to collapse
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
hyelton said:
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
Click to expand...
Click to collapse
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Wickidmasshole said:
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Click to expand...
Click to collapse
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
hyelton said:
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh well it was a great phone while it lasted. Thanks for the input.