Related
So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!
Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.
It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%
It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)
HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
Let us find out how mush SDS has affected to the Galaxy Note 2 by voting.
Keep posting in the thread so that the thread is keep bumping and people can vote.
AFAIK most of the SDS occurs within first six month, so the Poll options are according to it.
Please download this application and check your FwRev of chip and then vote
If you look in the sds thrwad you'll find far more opinions.
Sent from my GT-N7100
Your poll doesn't cater for me.
Had my N7100 with 0xf1 for a bit less than six months, not SDS yet, but showing symptoms (freezes/resets).
gadgetuk437 said:
Your poll doesn't cater for me.
Had my N7100 with 0xf1 for a bit less than six months, not SDS yet, but showing symptoms (freezes/resets).
Click to expand...
Click to collapse
I think it's ironic how it's called Sudden Death Syndrome and yet people think theyre actually experiencing it's symptoms on the phone. Maybe it was labeled wrong but maybe someone can correct me?
Sent from my GT-N7100 using Tapatalk 2
bushako said:
I think it's ironic how it's called Sudden Death Syndrome and yet people think their actually experiencing it's symptoms on the phone. Maybe it was labeled wrong but maybe someone can correct me?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Couldn't agree more.
Sent from my GT-N7100 using xda app-developers app
I am confused should i get note 2 or not (because of SDS) i started this poll. but looks like many people have not used 0xf1 chip for six months
i dont know what to do.. should wait more for newer version of chip?
i dont know why but whenever i compare mobiles with note 2 i like only note2 but sds does not let me go ahead please suggest me what to do
nicholes said:
I am confused should i get note 2 or not (because of SDS) i started this poll. but looks like many people have not used 0xf1 chip for six months
i dont know what to do.. should wait more for newer version of chip?
i dont know why but whenever i compare mobiles with note 2 i like only note2 but sds does not let me go ahead please suggest me what to do
Click to expand...
Click to collapse
I think u can go for it as 4.1.2 fixes sds or custom kernel+custom recovery fixes that on 4.1.1, and I think newer stock of note 2 should have newer chips so at the end its ur call
has anyone of you face or seen any 32 GB note 2 is getting SDS?
nicholes said:
has anyone of you face or seen any 32 GB note 2 is getting SDS?
Click to expand...
Click to collapse
Lol I clicked thanks by accident but I wanted to say that it's only the 16gigs that's affected by sds.
Sent from my GT-N7100 using xda premium
gaurav2009 said:
I think u can go for it as 4.1.2 fixes sds or custom kernel+custom recovery fixes that on 4.1.1, and I think newer stock of note 2 should have newer chips so at the end its ur call
Click to expand...
Click to collapse
Are you sure 4.1.2 is SDS safe? Why?
I'm trying to find any information about this problem as my phone died 2 days ago and I want to avoid this situation in the future.
Samsung doesn't recognize this bug officially (or at least I didn't find this information) and there is no official claims 4.1.2 fixes this.
colibri2 said:
Are you sure 4.1.2 is SDS safe? Why?
I'm trying to find any information about this problem as my phone died 2 days ago and I want to avoid this situation in the future.
Samsung doesn't recognize this bug officially (or at least I didn't find this information) and there is no official claims 4.1.2 fixes this.
Click to expand...
Click to collapse
Sammy would never acknowledge the existence of sds officially nor they seem to know what is going to be the perfect solution to the problem.
nicholes said:
has anyone of you face or seen any 32 GB note 2 is getting SDS?
Click to expand...
Click to collapse
It only happens to the 16gig versions of the note 2 which has that chip revision afaik.
Sammath said:
It only happens to the 16gig versions of the note 2 which has that chip revision afaik.
Click to expand...
Click to collapse
How does a newbie know if thier Note 2 is this revision?
Sent from my GT-i9500 using XDA Premium HD app
mstickland said:
How does a newbie know if thier Note 2 is this revision?
Sent from my GT-i9500 using XDA Premium HD app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2093599
I have had this phone since October 23rd and have had no problems. If it did die, I would warranty it through T-Mobile. They've been good to me in the past where I sent back my old HTC Sensation three times, each time they got a new refurb to me within 3 days. :good:
No problems here with sds, no lags, freezes. Works fine, thinking about rooting but not yet, still fears about sds
Sent from my GT-N7100 using xda premium
I seen some of the method given that used to detect the faulty chip but i just curious as the result on my phone somehow shown contradict result. May i know which source are reliable to ensure that the phone chip is faulty.
1st check with IMEI, i get 3537 (understand that anything 3550 should be no problem)
2nd check with dial *#12580*369#, i get HW rev 1.300 as understand HW rev If 1.301 then it is good chip, 1.300 is bad chip
3rd check with eMMC check, i notice the result given are different as it shows positive result with no SDS reported and sane chip....
d33pbluez said:
I seen some of the method given that used to detect the faulty chip but i just curious as the result on my phone somehow shown contradict result. May i know which source are reliable to ensure that the phone chip is faulty.
1st check with IMEI, i get 3537 (understand that anything 3550 should be no problem)
2nd check with dial *#12580*369#, i get HW rev 1.300 as understand HW rev If 1.301 then it is good chip, 1.300 is bad chip
3rd check with eMMC check, i notice the result given are different as it shows positive result with no SDS reported and sane chip....
Click to expand...
Click to collapse
Got all the things you posted here. But few month ago, My phone is still in good mood. (at least i think that).
Type: VTU00M
FWrev: 0xF1
Only Type: VTU00M
FWrev: 0xF7
is safe as per XDA SDS thread. They also mentioned that JB 4.1.2 has safe stock kernel.
t seems my phone is broken now also duo the SDS-problem. I knew that I had a SGN2 with a Insane-chip. I've updated to version 4.1.2 (late version DLK7) kinda fast. Afterwards I decided to root my phone and flash the Perseus kernel with a built-in software SDS-fix. I've runned the eMMC program multiple times without a crash or problem. So I thought that my phone was not affected / corrupted yet. A couple of weeks ago the symptoms started. I had a phone-reboot when I clicked to update a application in Google Play. A couple days later another crash. I've did run the eMMC program again and it showed : Passed. Then it seemed suddenly the problem was not happening for roughly two weeks.
Last week my phone started to acting weird after a program update (LED LIGHT MANAGER). My first thought was that this was because of a bad LED LIGHT MANAGER update. So I've cleared the data and removed the application. But the problem occured afterwards.
I did a eMMC program test and my phone did reboot (did not pass the test). Then freezes and reboots started to happen frequently and the time between those were becoming shorter and shorter. Maybe it was caused by a program or something. So I've started in Safe-mode and see what happened. But even that made my phone freeze.Sometimes scrolling in mails, facebook or even deleting a picture is causing the freeze.
Now the phone is even freezing after like 2 minutes without dooing anything. And one time it didn't wanted to power on. A battery-remove and add was needed. Also on a restart I noticed that some datasetting of application where missing. I had to do the settings of Swiftkey-board again and from Whatsapp+ :S:S
Luckily got most of my datastored in the cloud with a good back-up of Titanium Back-up. I have a insurrence also on my phone. Upcoming wednesday gonna visit the Samsung Repair Store and ask them to replace my motherboard with a good chip. Phone is roughly : 7/8 months old now.
It seems that the software-fix (kernel and rom) are not the solution. Sooner or later everyone with that specific kind of broken Batch: VTU00M 16GB internal memory chips with revision 0xF1 will be a victim of this SDS problem. A software patch is definitely not the solution for this problem.
We keep in touch.
Regards,
IriseyouFall / Jurgen
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Yes its the chipset in the phone that has a bug which can kill the phone. Alot of the note2 phones have it including mine. There is an app on market that can tell you if you got the chip in your phone but by now you already know that. Try a phone repair shop or if you want surf around the net and see if you can find a motherboard for a decent price then you could change it your self.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
The newer roms have a software fix for the hardware bug. Dont remember if that fix is in the rom it self or in the kernel but if you had the latest custom rom on your phone then it might not have died.
Sent from my GT-N7100 using XDA Premium 4 mobile app
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
ksc6000 said:
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
Click to expand...
Click to collapse
My N7105 died also, simply would not boot, not even into download/recovery mode at all, no red led. Tried switching batteries, charging, pressing buttons for 30secs, etc; no response.
It was running 4.1.2 and on Perseus kernel alpha33, which was what everyone said it needed to avoid the SDS issue. My phone was even tested safe/sane via the eMMC test app.
Not 100% certain if it was SDS, but either way it was unresponsive/dead.
ksc6000 said:
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Click to expand...
Click to collapse
Ohh,Sorry for that & Thanks share this IMP Info,Have u ever Test eMMC Bug app? U have Sane Chip?U bought new phone?
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
ksc6000 said:
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
Click to expand...
Click to collapse
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
jdomadia said:
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
Click to expand...
Click to collapse
No red light. I can't get into download mode at all.
a piece of my knowledge acquired by reading the whole thread. First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Sent from my GT-N7100 using xda premium
aka_sirok said:
First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
Click to expand...
Click to collapse
Hmm ok, just curious, my dead phone was running 'HashCheck Hybrid v2.2 ZHDMB1.t0lte' with Perseus kernel. Should it have been safe or no?
aka_sirok said:
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Click to expand...
Click to collapse
I see, so Hard SDS it was then.
Perseus kernel has the patch for sds added.
GT N7105 with XDA Premium......that is all......
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Sent from my GT-N7100 using xda premium
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
maluus said:
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
Click to expand...
Click to collapse
it is a hardware problem. check the version of the chip with EMMC checker, 2 months old it's quite a good notice because it means newer chip probably.
Sent from my GT-N7100 using xda premium
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
aka_sirok said:
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Click to expand...
Click to collapse
That was my understanding too, I had Philz CWM Touch (cant remember which version, but I d/led and installed it last month) installed as well.
This was the version I was running:
N7100XXDMC3 N7100OLBDMD1 - Malaysia
maluus said:
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
Click to expand...
Click to collapse
Checked it and my wife's is a "sane" chip.
Hi
Had the sds bug kill my n7100 and Samsung wouldn't fix under warranty saying the phone is scratched and therefore no warranty, amazing how easy it is to turn a fan into a hater but that's unrelated to this post.
After a private lab replaced my emmc they warned me not to flash a new rom but when I asked why they couldn't give me a proper explanation hence my post.
Can anyone elaborate more about this and explain what the risks are and what the reproductions are in flashing a new rom like omega for example? I'm fairly technical and have good knowledge about flashing roms restoring efs etc. So a technical explanation will be extremely appreciated.
Thanks
Sent from my GT-N7100 using Tapatalk
eMMC erase bug is related to Samsung's fault. The firmware versions >4.1.2 are belived to be safe. Check the threads about SDS here, there are more than just one.
In fact, the bug fix been done by a patch that gets loaded by each boot. One for the OS, one for the recovery mode. Most of the custom kernels or ROMs made for N7100 feature the SDS fix patch.
Actually, you should definitelly flash another ROM. Try to avoid using recovery mode before you have flashed safe rom or kernel. Any action done in the recovery mode with insane chip and android ver. earlier than 4.1.2 may cause sudden death of the device.
It is simply unacceptable insolence of Samsung to try to hide from customers the fact that SDS is a big, embarrassing faoult of themselves. Yes, they are searching for even a smallest scratch and try to convince people that THAT is a reason for sudden death. LOL! Just insist that the www is overfilled with information about that. Also i9300 has it, N7000 has a hard brick bug.
Saying that, I just have bought a new n7100 as it is amazing device with one of the lowest SAR values among all ever made cell phones. Strong reason to own it, especially now when the price has dropped after Note 3 is released.
Thanks for your answer, the lab actually replaced the emmc to the a sane chip now, shouldn't be hitting sds anymore.
They said that because this is not the original emmc it could cause problems when flashing roms, I was wondering why they would say that.
Sent from my GT-N7100 using Tapatalk
petelking said:
Thanks for your answer, the lab actually replaced the emmc to the a sane chip now, shouldn't be hitting sds anymore.
They said that because this is not the original emmc it could cause problems when flashing roms, I was wondering why they would say that.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Where did you get it fixed at? Thanks
Sent from my iPhone using Tapatalk 2
Local shop here in Israel
Is Israel there is common KASTAH policy for every fixed device.
Do nothing or have your own KASTAH ready. Not our business...
Sent from my GT-N7100 using Tapatalk
So you are saying this is just kisuy tachat?