Related
Hi
I am attaching a screenshot of what is happening to my phone screen .. it has happened about a dozen times today ...
There is a strange overlapping thing with the screen .. and happens randomly.
More often than not, it happens while unlocking the screen.
help!
Might want to try a factory reset. If its not solved you should return the device and swap it.
Return the piece for warranty.....did you flash any custom rom?
hi
I have returned the handset now .. and am waiting for a replacement .. feeling sceptical after all the screen issues being reported
My handset did not experience any flicker .. but it was unusable anyways ..
I am not using any custom ROM as of now ..
This looks like the same issue that my wife's HTC One X has been having. It crashes several times a day, becoming unresponsive. It's then very hard to coax it to reset/reboot. Sometimes the screen corrupts before it crashes, in just the way the photograph shows.
We're returning it to HTC under warranty. It's still in warranty, and untouched: although I've modded my share of phones I'm a big scaredy and never touch my (or my wife's) flagship devices until they're at the end of the warranty. And this is one of the reasons why... :/
So anyway, all the software is stock. It's an unbranded, unlocked One X. The only software updates done to it have been the OTA updates from HTC. Hasn't been one in a while, AFAIK, and this issue has started spontaneously a few days ago.
It's an odd fault. It's almost like the phone is trying to render the display at an inappropriately low resolution. If I had to guess, I'd say the ROM is partially corrupted, perhaps because of a fault with the flash chips.
Several factory resets have made no difference, and it problem occurs with or without a SIM card in place.
Fingers crossed HTC will service it with care, it *was* faultless until this happened.
I actually got a video of the corruption, which I will try to post later on.
EDIT: Here is the video.
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.
gicarey said:
Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.
Click to expand...
Click to collapse
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.
wowrlz123 said:
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.
Click to expand...
Click to collapse
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).
gicarey said:
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).
Click to expand...
Click to collapse
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.
wowrlz123 said:
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.
Click to expand...
Click to collapse
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM, though wasn't running a rooted phone since. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?
gicarey said:
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?
Click to expand...
Click to collapse
No you must have working phone and reset it with triangle away.
wowrlz123 said:
No you must have working phone and reset it with triangle away.
Click to expand...
Click to collapse
Sure I did that way back when.
dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old one
Sent from my GT-N7100 using xda premium
Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Sent from my GT-N7100 using Tapatalk 2
As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Sent from my SPH-L900 using xda premium
aka_sirok said:
dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old onem
Click to expand...
Click to collapse
adytum said:
Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Click to expand...
Click to collapse
Thanks chaps, this helps settle a few nerves.
billard412 said:
As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Click to expand...
Click to collapse
Sadly, no go, due to lack of a PIT according to Odin.
Called Samsung, mail in with 2 week turn around, or walk in and should have it back in 2 days? Sound about right.
There's a Service Centre 10 mins from my office, so I shall walk it in there, but (rather annoyingly), am on a training course until Friday so I won't get along till then. Excellent timing! Still, walk in ought still be quicker than sending it away.
In the mean time, I have hauled out an old SE Arc S running ICS for the time being. Feels painfully slow & restricted (low memory) compared to the Note2!
Thanks for all your help guys.
So...
Walked the phone into the service centre (CRC - http://www.crclondon.co.uk/repairs/samsungrepairs) on Monday, who told me they'd need to send it up to their Level 3 centre, which would likely be a 7-10 day turn around.
Took a call from them today, claiming that as the phone had been rooted, they couldn't do it under warranty, and it would cost £120 to repair. I rather firmly mentioned the aforementioned EU regulation which, I understood, meant that nevertheless, the repair, unless caused by the root, ought still be covered under warranty. The chap was completely intractable, refused to pass me to a supervisor of any sort for further discussion, so I've told him to have it returned to their office and I would collect ASAP and deal with Samsung directly where I hoped to have a more satisfactory discussion.
Seems like it's likely to be back with them on Friday - I will probably collect on Monday and get it dispatched same day.
Wish I hadn't bothered waiting for the walk in centre now. The Sony Arc S I'm currently using is frustratingly slow by comparison with what I've become used to!
I think you were being too honest.
I got my note2 motherboard replaced last month. and since they coundnt tell whether i had rooted or not and samsung havent officially made any announcement about sds, i told them what i found on the net that the system status shown customs because the nand memory was corrupt and it couldnt read the product name nor system partition thereore it defaulted the system status to be custom.
As a further update, Samsung central help group pretty awful to deal with, and not resulting in a satisfactory resolution.
Was eventually promised a call back, finally got an email 4 days later basically telling me 'whatever our 3rd party service centre told you we will stand by, if you collect & send to us, we'll lookup their response and use that in communication with you..' 'If you want to challenge their assertion, you'll need to source a report from an independent assessor.'
So, from all this - Ultimately, I need the phone back in a reasonable timeframe, so I've asked the 3rd party service centre to effect the repair, and I'll pay their £120 bill. I have also told them that I want whatever components they replace (I'm told likely motherboard), and copies of their full engineers report containing details of the fault found, diagnosis of cause, and resolution steps - returned to me along with the device so that I retain any evidence I require for further discussions (getting them to agree to this was an awful task, as they initially quoted various recycling regulations).
Once it's back in hand, I'll then revert to Samsung again, and work my way up through the escalation queue.
Next phone, I suspect, won't be a Samsung device. Maybe Nexus.
Fun fun fun...
G.
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Top5a said:
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Click to expand...
Click to collapse
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
thorur said:
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
Click to expand...
Click to collapse
Did it die closely after the unlocking/flashing? Or a long time after? Or was the unlocking/flashing an attempt to save the phone? Ever get it fixed? I'm so anxious!
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
Well, thanks for the input! Makes me feel a better hopefully the emmc isn't completely fried. I just really want my files, and am continually irritated at myself for having been so stupid to not make backups.. although I have phones from 10+ years ago that have never completely died in such an unexpected manner. It's quite the agonizing wait for a JTAG programmer to come in the mail. If I can manage to get it to boot from SD, which I haven't been able to do so far, do you think it's logical for me to simply reflash the bootloader/CWM, then attempt boot? It shouldn't erase files, right?
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I've also searched everywhere for a debrick image for 4.1.1 AT&T... anyone know where I can get one? All I can find are ones for 4.1.3 =\
EXACT same problem here, let me know if you find anything
(Btw, my phone also had the "power button stuck down" issue, but your phone will vibrate when you put the battery in if this is the issue.)
If I'm not mistaken you will be able to Odin to 4.1.1 while using the 4.3 SD card debrick (again this is just guessing)
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I've tried the SD card debricks for 4.3, and still nothing happens. Yea, I also don't get vibrate. As a long shot, I actually installed the qualcomm drivers and ran the qdload.sh script to attempt to send a signal which kicks the phone out of that mode (works on some... I want to say, HTC, phones), but, yea, I think the emmc just failed somehow. I'm hoping that the failure is just in the bootloader segment, and that by jtag reflashing the bootloader area, I should be able to boot. Either that, or even if one of the memory sectors died, hopefully it's not the one with my data partition. I still can't believe this ! Out of all the electronics I've ever used, aside from a hard drive or two, I've never had something like a phone just kick the bucket with no warning. gha !
Also, thanks for all the tips and stuff, guys and gals. Tell me if you figure out anything, and I'll let you know if I get it fixed with jtag.
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ZOMG SO RUDE > haha, j/k ;P Yea, no problem, dude/dudette! I know how it feels reading threads with no followup... I'm actually surprised that people have come out of the proverbial woodwork mentioning having similar problems to me ! It really sucks spending inordinate amounts of time reading threads and not arriving at a definitive conclusion... so, yea, I especially want to let people know if there is a fix, and/or how I did it.
So, with regard to what you said about the snapdragons not failing... yea. This is rekking my mind, tbh, because I've just never had a device insta-fail on me like this (aside from some old computer hard drives that were server backed up, but yea that's essentially par for the course on that medium [yay for S.M.A.R.T.]). Especially a device that I'd only had for less than 2 years, and though my GS3 has heavy usage, I treat it very well (no drops, water, etc.)... so, yea.
Also, a minority of people with whom I have spoken via the æther have also experienced similar emmc failures on i747s, as well ! Which I was not expecting. It's still insane, though, to believe that, out of such a small percentage of phones that could potentially experience SDS, and then which ones actually do experience it... and then to not even have an i9000 and /still/ experience it on an i747... I feel as though I've won the lotto. Except ****ty.
I'm waiting on parts to come in, then surgery will commence.
Did you try going into download mode? If you can so that then the phone is fine. Another thing is try reflashing stock Odin which will erase msgs and stuff but not music or pics unless u tick "repartition".
Sent from my SGH-I747M using Tapatalk
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung I747 V1.0.5095.46594]
Connecting to the dead body...OK
Detected dead body ID: 0xhexhereisOK[redacted] - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x000400000000 Bytes = 16.00 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)
No Resurrection Data is available for the eMMC Chip with Capacity = 16.00GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x0003AB3FBE00
Had to reduce the speed to that 2MHz/1MHz to get communication to work. So, 0x51 is a DCC power failure problem... but it is able to detect the initialized chips. So.. not really sure how to proceed at this point. I haven't checked the signal quality on my NRST line, which apparently can cause problems. Some people have increased the voltage from 1.8 to say 1.9, but doing something like that requires me to actually make my own resurrection file, which I haven't had the time to do yet.
Anyone seen a problem with something like this before?
The 000000 is somewhat unsettling, as the chip is apparently supposed to report some ID#? Although, the failures that I'm getting don't seem to be the typical ones that happen when the emmc becomes completely toasted.
Oh, yea... I can't seem to figure out wth is up with --> WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Like..... ??? I think I'm using the most up to date resurrector?!
EDIT: Dumping out the entire contents of the emmc (haven't had errors so far, but it will take a while at 1 MHz), into a bin file (this avoids the bad sectors in the bootloader).
Does anyone know what to do with the resultant *.bin file? I think that if I got another surrogate GS3, I'd be able to write that onto the phone, essentially cloning my dead phone. I'd like to avoid having to do that, though -- does anyone know how to write one of DCC bin jtag file dumps into a readable file system?
So after using the NOTE4 for 6 months and the latest lollipop updates just completely ruining my Smartphone experience, I started searching for my next phone. Fastest I've started looking for another phone on any smartphone I've owned.
Not wanting to dish out another $600 immediately, I took my NOTE4 to ATT repair center and after two trips, had my device replaced.
and I must say.. the new NOTE4 seems faster, has ZERO gps issues (locks in under 2 seconds). Car tracks smooth under Google Maps instead of jumping and getting stuck. And placed that I use to get really bad download speeds are now much better.
If you have issues with update and been having problem with GPS.. go get your phone swapped.
Several on this site have swapped our device multiple times over GPS issues and had just as bad a problem with the new one.
i'm thinking to do the same thing. Were they aware of this issue or they were surprised to hear that? What tests did they run to confirm you had malfunctioning device? Did you get temporary replacement for time your phone was in shop?
Guess this happens randomly, cause i have my Note 4 since it first came out and upgraded to Lollipop ? and have 0 issues.
Running On New Deadly Venom Note 4 v3.0
First time i went in they said they'll "FACTORY FLASH" the device to the latest Lollipop update. said sometimes the update over the air gets all messed up. so I let them.. tried it for 2 weeks only to see that it was behaving the exact same.
I use GPS all the time for work and the problem I had was when I would stop at the light, the GPS position would be stuck for 30sec to a min after I left that intersection. Made the GPS useless.
So I just went in.. same complaint.. they had log of what they did before.. and just said "we'll give you a replacement device."
I had them flash it to latest lollipop firmware and I haven't had issue since. Granted.. It's not as good as 4.4.4 GPS.. but it's workable.
and I'm only out of $8 bucks for the glass screen protector.
I may ODIN it back to 4.4.4 to test the temp root, but at least i know that my phone is good with 5.1.
Venom.. I got the NOTE4 on week of of release.. possible that mine was a earlier hardware with issues? can't be sure.. but I'm happy again with my NOTE4.
Waze GPS lost when static
Hello all,
My problem is that my GPS signal gets lost when I am stopped at a traffic light...
Has anyone else got this problem?
I have a release day Note 4 as well. My GPS sometimes loses signal when nothing is blocking it such as trees, tunnels, etc.