GloriaStacey
07-13-2014, 05:05
However, another serious problem suffered by users of the Galaxy S3 The device has a major fault that many began to call "sudden death", especially on devices sold during the period from May to July, which caused him to be completely unusable because from time to time just "died" and that it was impossible to turn it on.
Moreover, it was not possible to establish a pattern because sufferers were not root, root, devices with ROM shipped with ROMs cooked, etc and all felt the same: the Galaxy S3 working perfectly and at any moment "dead ". The number of affected increased daily and Samsung remained silent on this issue so that users themselves who began to investigate the problem. Some argued that the "sudden death" was due to defects in the motherboard of the Galaxy S3 sold from May to July, which caused "dies" after 5 or 6 months of use. Others argued that the problem was responsible for the NAND memory, which was corrupted and caused failure of the root samsung galaxy s3 (http://airpublisher.com/how-to-root-your-samsung-galaxy-s3-with-ease) device, resulting in a brick. Meanwhile, others believed that the problem was generated by the device loader.
Samsung remained silent on the matter, but was changing free terminals that have this problem (although they have to speak of many cases in which the victims had to pay for the service).
After many twists and turns, he looks to have some light on this topic.
Moreover, it was not possible to establish a pattern because sufferers were not root, root, devices with ROM shipped with ROMs cooked, etc and all felt the same: the Galaxy S3 working perfectly and at any moment "dead ". The number of affected increased daily and Samsung remained silent on this issue so that users themselves who began to investigate the problem. Some argued that the "sudden death" was due to defects in the motherboard of the Galaxy S3 sold from May to July, which caused "dies" after 5 or 6 months of use. Others argued that the problem was responsible for the NAND memory, which was corrupted and caused failure of the root samsung galaxy s3 (http://airpublisher.com/how-to-root-your-samsung-galaxy-s3-with-ease) device, resulting in a brick. Meanwhile, others believed that the problem was generated by the device loader.
Samsung remained silent on the matter, but was changing free terminals that have this problem (although they have to speak of many cases in which the victims had to pay for the service).
After many twists and turns, he looks to have some light on this topic.