Related
Hi, my SGS is working fine all the while. But sometimes after i unplug the power adapter upon fully charge, the screen keeps blinking in the way like loading home(loading icons)->black screen->loading honme-> black screen->.....
it repeats for very a long time, even if i manually screen off then unlock the screen, the blinking problem still repeating. Until i reboot the device, it works fine again... Happened once in the middle of playing game, it suddenly 'jump' to home screen and the blinking problem begin
Wonder if this related to system crash and cause home screen keeps loading on and off or hardware problem... did anyone experience this?
I've never heard of this before. To diagnose whether it's a hardware problem, your only bet would probably be to flash a clean firmware. Maybe someone will have heard of this though.
upichie said:
I've never heard of this before. To diagnose whether it's a hardware problem, your only bet would probably be to flash a clean firmware. Maybe someone will have heard of this though.
Click to expand...
Click to collapse
thx mate for suggestion seems like its only me having this problem, so far has been flashed 2 custom roms, and problem persists, i think need to flash it back to old GB stock rom to compare it.. sadly warranty period has expired, hope its not related anything with hardware issue..
davidncs11 said:
thx mate for suggestion seems like its only me having this problem, so far has been flashed 2 custom roms, and problem persists, i think need to flash it back to old GB stock rom to compare it.. sadly warranty period has expired, hope its not related anything with hardware issue..
Click to expand...
Click to collapse
Try a stock firmware, that should tell you whether or not it's a hardware issue. If it isn't, it's probably kernel related. Hopefully you can figure it out!
i have got the same problem too.. =(( how to fixed it.. the screen keep blinking...
Flash stock firmware . Then if its fixed pls report here.
BHuvan goyal said:
Flash stock firmware . Then if its fixed pls report here.
Click to expand...
Click to collapse
I've flashed from 2.1 to 2.3.6 and still it's blinking
Does anyone know how to fix it?
same issue
hi,
i have the same issue as well with 2.3.6, BaseBand version I9000XXJVU.
It is not a stock rom and it started appearing just a few days ago. It happens when i plug to charge it and after unplugging it. I have not noticed when it stops.
A friend of mine has the same issue, but with 2.3.4 stock firmware, so i think it is not firmware related.
Any new info on this? what could i provide for further troubleshooting
Main issue is of course that it drains the battery quite much and also allows you to mistakenly unlock the phone when the screen is on, so i was forced to put patter or PIN lock.
Cheers...
avatarz_bg said:
hi,
i have the same issue as well with 2.3.6, BaseBand version I9000XXJVU.
It is not a stock rom and it started appearing just a few days ago. It happens when i plug to charge it and after unplugging it. I have not noticed when it stops.
A friend of mine has the same issue, but with 2.3.4 stock firmware, so i think it is not firmware related.
Any new info on this? what could i provide for further troubleshooting
Main issue is of course that it drains the battery quite much and also allows you to mistakenly unlock the phone when the screen is on, so i was forced to put patter or PIN lock.
Cheers...
Click to expand...
Click to collapse
If you have ChatOn app try to uninstall it. Did work for me. (I my case the issue appeared when the internet was accessed via any browser. Same blinking pattern though)
having a strange problem. was having a normal day with my phone, then at some point in the day I tried turning it on and nothing. No matter what I have done the screen just doesn't come on. Here are a ist of things I tried doing.
- Take batterry out for over a minute then try and turn it on. FAILED
- take battery out the plug phone into computer and turn it on. FAILED
- Tried to enter both recovery mode and download mode. FAILED
The phone simply does not respond to any button inputs. Have had the phone for almost a year and ZERO issues. Use the phone lightly and its in top condition.
Any help will be appreciated.
Try a different battery. You have rooted the phone? Give us more info about the phone like custom ROM and what do u suspect to be the probem.
Lorddeff have you heard of sds?
http://www.ifixit.com/Answers/View/128792/Sudden+Death+Syndrome+how+to+fix
《¤★N€€bz★¤》
Varad297 said:
Try a different battery. You have rooted the phone? Give us more info about the phone like custom ROM and what do u suspect to be the probem.
Click to expand...
Click to collapse
Yh, rooted and all that. Ben rooted from the first day I got it. Using philz safe kernel with the ultimate TW ROM. Never did any funky stuff on the phone. I'm pretty sure that its not from a battery cause I have two of those and I am sure its not from a bad flash or something. My last flash was over a month ago and the phone was working perfectly until it literally just stopped working like 5 mins after the last time I used it.
neebi007 said:
Lorddeff have you heard of sds?
http://www.ifixit.com/Answers/View/128792/Sudden+Death+Syndrome+how+to+fix
《¤★N€€bz★¤》
Click to expand...
Click to collapse
I have now... and thanks for that link. Looks promising. Though it means I would have to ship my phone out, which I guess is a lot better than doing nothing.
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
dlnas said:
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
Click to expand...
Click to collapse
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
iElvis said:
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
Click to expand...
Click to collapse
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
dlnas said:
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
Click to expand...
Click to collapse
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
iElvis said:
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
Click to expand...
Click to collapse
Before it died. I unlocked the phone and the only thing I could do was pull the notification drawer down. It would not let me open any app or even the app drawer.
dude this sounds frightening
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
postfatal said:
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
Click to expand...
Click to collapse
That fix is only for a couple of specific issues:
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
tousary shall
iElvis said:
That fix is only for a couple of specific issues:
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
Click to expand...
Click to collapse
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Had the same problem after flashing the wrong recovery..
THis means it is hardbricked and unrecoverable..
You could ask here: http://forum.xda-developers.com/showthread.php?p=43750389#post43750389
Else send it in for repairs
dlnas said:
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Click to expand...
Click to collapse
It's a hardware fault, from everything I've seen, and HTC or AT&T should replace it. AT&T tends to be very easy about this. If the phone won't power on at all, they shouldn't give you a hard time.
So My phone is most certainly bricked this morning. I saw a few posts on the topic, as well as one that was locked. Seems that there a re more than 5 of us, can a mod by chance merge the posts, so we can start troubleshooting the issue, and keep it from happening in the future. I will describe what I have done, and maybe it will help someone come up with an idea of what binds us all to our bricks.
Once upon a time in a galaxy far far away I was a flashoholic:
So I get my black one in the mail, and start playing in the forums, seeing what's what, and I go about trying to moonshine, firmware doesn't match so it doesn't work, get her rooted, s-off with revone, and flash a few sense based roms. No problems. Try the cm rom listed in the first post of the 10.1 link, no gps, weak signal, back to sense. Finally get a few of the threads completely read, and find rc2 of 10.1 flash(using twrp 2.6.1.0, and I do all the wipes and format data, and factory reset before sideloading my roms) get it up and running, gps works, find the build.prop line to edit to get it to stick to sprint to work, and away we go, rom is good, problems are small, phone working exactly llike it's supposed to. I did play with trickster mod here and there, but didn't much care for the program. So was playing in original development, and saw that the twrp forum had new input, so I go into it, and see a new twrp available (2.6.3.0) dl, flash the .img, reboot recovery, wipe everything, sideload 10.1 rc2 again and gapps. Almost immediately noticed the temp on the phone was very warm, almost hot, and that was without being on the charger. It was bedtime, so plugged phone in, go to bed, get up look at phone, and its at 50 percent on the dot, and no red light. Houston we have a problem. So I start researching how to ruu back to stock, and just to see if it was the recovery, I flashed cwm, didn't like it, and then reflashed the older twrp, problem persists, well I really didn't want my phone to reach 0 percent battery, so the race was on, set phone on ac vent and charge it, take it off charger, it would drop 20 to 30 percent in five to ten minutes. Get ruu downloaded, can't get it to run, troubleshooting that, my battery plugged in is down to 6 percent and the speakers are hissing at me, when I see the problem, plug it in to the laptop, run ruu, watching phone, watching progress, complete!!! yes reboot phone, log in to gmail, get message about phone using more power than it's receiving (plugged in to wall again) and boom shutdown. So now I'm thinking to myself hrmm good or bad, red light says charging, go smoke a few cigs comeback in phone boots, and is charging, no errors, everything is running like it is supposed to, everything works. It's still very warm though for not running much of nothing, leave it in the cold air, and she charges up to 100% (albeit slowly took most of the day) unplug her, go to sleep, and about 3 hours later I heard the low battery warning, and woke up to my nice black brick. No red light, no pressing buttons for x amount of time, she is most certainly dead.
Hopefully this can help us figure out what is causing the bricks.
And only 3 more hours to the sprint store opens :victory: that's bound to be fun
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
phatmanxxl said:
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
Click to expand...
Click to collapse
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
I don't know, I love Slim ROMs but if it happens again Sprint will start asking questions and might investigate the phone, plus I got the last red phone in stock
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
How many brick threads have you seen in here on Sense roms?
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
Including folks that flashed gsm roms? Zero
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
i wont even flash an aosp rom on this phone i have seen a few people brick while on aosp.. and the dude i got my one from he bricked his first one running an aosp rom.. he said he rooted it flash an aosp rom.. was fine for a week or so the while listing to music on the phone it died brick.. im not saying its deff aosp roms but i have seen and heard enough where im not going to try it... lol im good with my sense:good:
I wonder what's the difference between GE ones and Sense ones.
raptoro07 said:
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
I guess you could summarize it like that, but I thought that I stated I knew it was going to die, shortly after I upgraded my recovery. All flashing after that was an attempt to troubleshoot/save the beast if at all possible.
Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 2.6.1.0) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
Ty,
I'll be here all night
You sure do keep a really good attitude through it all though. We've all been there but you are purposely putting yourself and wallet through it over and over to find the culprit. I for one appreciate it.
D
Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,
Alsager said:
Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,
Click to expand...
Click to collapse
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
If the battery has waranity? how you find out is slow
wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
drulo222 said:
If the battery has waranity? how you find out is slow
Click to expand...
Click to collapse
I did a factory reset ( I was on JB then) and didn't solve the issue. when the phone is connected to the charger it can go beyond the Samsung logo and the splash screen for a while but will turn off quickly. without a charger it will only show the Samsung logo and then turn OFF.
Can you go into recovery, plug the cable, and then power off the phone? leave it like that for few minutes.
I can go into the download mode but not recovery.... what does that mean???? Tried your other suggestion, but no luck...!!
Is your battery swollen if looking at the side and you say it will go past splash screen if plugged into charger so does that mean it will boot into the Rom if plugged in or does it just stay splash screen and also if not able to get into recovery could mean something happened with the kernel so flashing a fresh jb Rom with Odin maybe what you need. The problem with that is if your battery is bad it could cause more problems trying to flash anything with dead battery as in bricking the device. So you should start with new battery and let charge a few hours then see if your phone boots up if not then you could flash with pc Odin and go from there.
Sent from my GT-N7000 using XDA Premium 4 mobile app
He should try kernel option you gave him, if everything else failed. I read around there were like 3 people with same situation. Maybe they used the same thing?
Search philz kernel, download one or two, and flash those in odin. Its a safe kernel, and powerful cwm.
He probably fixed by now. Hope so, for his own good.
Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....
Alsager said:
Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....
Click to expand...
Click to collapse
by any chance, do you know what were the old battery voltages under measurements?